[ spindle-Bugs-1207876 ] Tapestry Spec Editor Unusable on Mac OS X

"SourceForge.net" <[email protected]> Sun, 11 Sep 2005 11:24:35 -0700
Newsgroups gmane.comp.ide.eclipse.spindle.devel
Message-ID <[email protected]>
Bugs item #1207876, was opened at 2005-05-24 11:06
Message generated for change (Comment added) made by glongman
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=459328&aid=1207876&group_id=50321

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Spindle
Group: 3.0 alphas
Status: Open
Resolution: None
Priority: 5
Submitted By: Galen Meurer (sitio)
Assigned to: Geoffrey Longman (glongman)
Summary: Tapestry Spec Editor Unusable on Mac OS X

Initial Comment:
On OS X, I am finding that the Tapestry Spec Editor spends most of 
it's time in the rainbow pinwheel (the Mac equivalent of the 
hourglass), or flashing the black and white pinwheel, quickly, 
purposelessly. When not stuck in the pinwheel, typing is so slow, I'm 
having flashbacks of my 2400 baud modem.

All of Spindle seems to work flawlessly except the Spec Editor, 
which does work, it is just painful. Every key press causes cursor 
spasms and a great delay. I have given Eclipse from 250Mb to 1 gig 
of memory and none of that makes a difference.

For now, I'm simply opening all my jwc and page specs in the text 
editor. They are decorated with the red x to mark errors and the 
problems view gets updated just fine, but I neither get syntax 
highlighting nor completions.

I am using Eclipse 3.0.1 and Spindle 3.1.24. I am currently on Tiger, 
but I had this same problem on Panther. I have had this problem 
since moving to a Mac. I have never seen this issue on Windows.

I am attaching some of my .log that looks potentially relevant.



----------------------------------------------------------------------

>Comment By: Geoffrey Longman (glongman)
Date: 2005-09-11 14:24

Message:
Logged In: YES 
user_id=387057

Looking at the original stack trace attached to this bug I
think that recent changes will have address at least some of
the problem.

I would implore that a Mac user try out Spindle 3.2.2 (about
to be released)  and see if the situation has improved at
all. If not, pls attach a new stack trace as the line
numbers in the old one don't match the current code.

Thanks!

----------------------------------------------------------------------

Comment By: Geoffrey Longman (glongman)
Date: 2005-08-26 10:33

Message:
Logged In: YES 
user_id=387057

The new stack trace is a Xerces conflict. A description of
the problem (in one particular case - RSA)  is found here:

http://jroller.com/page/glongman?entry=spindle_breaks_in_rsa_6

The question is where is Xerces getting into Java's root
classloader? Sun VMs ship with crimson so no problem unless
users preempt that using the endorsed jar method. IBM JRE's
appear to screw up Spindle because they ship with Xerces by
default. I don't own a Mac so I can't tell what the cause is
in this case.

----------------------------------------------------------------------

Comment By: Guillaume Lasnier (guette)
Date: 2005-08-26 08:35

Message:
Logged In: YES 
user_id=633150

I confirm this is still an issue. I am experimenting the same symptoms 
on Mac OS X.4 running Eclipse 3.1 and Spindle 3.2.0. Curiously, the log 
error messages no longer are those reported by Galen.
Here's mine :
!ENTRY org.eclipse.core.resources 4 2 2005-08-26 14:20:25.917
!MESSAGE Problems occurred when invoking code from plug-in: 
"org.eclipse.core.resources".
!STACK 0
java.lang.NullPointerException
        at com.iw.plugins.spindle.core.parser.Parser.domParse
(Parser.java:315)
        at com.iw.plugins.spindle.core.parser.Parser.parse(Parser.java:
252)
        at com.iw.plugins.spindle.core.parser.Parser.parse(Parser.java:
235)
        at com.iw.plugins.spindle.core.parser.Parser.parse(Parser.java:
216)
        at com.iw.plugins.spindle.core.builder.Build.parseToDocument
(Build.java:690)
        at com.iw.plugins.spindle.core.builder.Build.parseToDocument
(Build.java:669)
        at 
com.iw.plugins.spindle.core.builder.FullBuild.findDeclaredApplication
(FullBuild.java:181)
        at com.iw.plugins.spindle.core.builder.FullBuild.preBuild
(FullBuild.java:72)
        at com.iw.plugins.spindle.core.builder.Build.build(Build.java:171)
        at com.iw.plugins.spindle.core.builder.TapestryBuilder.buildAll
(TapestryBuilder.java:389)
        at com.iw.plugins.spindle.core.builder.TapestryBuilder.build
(TapestryBuilder.java:240)
        at org.eclipse.core.internal.events.BuildManager$2.run
(BuildManager.java:593)
        at org.eclipse.core.internal.runtime.InternalPlatform.run
(InternalPlatform.java:1044)
        at org.eclipse.core.runtime.Platform.run(Platform.java:783)
        at org.eclipse.core.internal.events.BuildManager.basicBuild
(BuildManager.java:168)
        at org.eclipse.core.internal.events.BuildManager.build
(BuildManager.java:324)
        at org.eclipse.core.internal.resources.Project.build(Project.java:82)
        at com.iw.plugins.spindle.core.builder.BuildJob.run(BuildJob.java:
86)
        at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)

!ENTRY com.iw.plugins.spindle.core 4 4 2005-08-26 14:20:25.919
!MESSAGE org.eclipse.core.internal.resources.ResourceException: 
Errors during build.
        at org.eclipse.core.internal.events.BuildManager.build
(BuildManager.java:326)
        at org.eclipse.core.internal.resources.Project.build(Project.java:82)
        at com.iw.plugins.spindle.core.builder.BuildJob.run(BuildJob.java:
86)
        at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)   

----------------------------------------------------------------------

Comment By: Geoffrey Longman (glongman)
Date: 2005-08-20 13:25

Message:
Logged In: YES 
user_id=387057

is this still an issue?

----------------------------------------------------------------------

Comment By: Geoffrey Longman (glongman)
Date: 2005-06-17 15:33

Message:
Logged In: YES 
user_id=387057

Although I can't reproduce this on a PC, I have examined the
errors and made some changes. If I were you I would try out
3.1.27 when it appears and report you experiences here.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=459328&aid=1207876&group_id=50321


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf