Hi all,
Investigation of the error below is leading me to believe that it has
something to do with Apache Xalan and JDK 1.5. So... I have a few
questions about that.
- Does WOLips run under a separate JVM from Eclipse? I tried running
Eclipse under both 1.5 and 1.4.2 with the same symptoms, so if that
should have clarified it, I'll start looking elsewhere.
- Does WOLips bundle its own version of Xalan, utilize one from
Eclipse's plug-ins, or one on my class path?
Thanks,
Clark
On 31 Mar 07, at 12:39 PM, Clark Mueller wrote:
> This solution does not appear to have worked for me. I experienced
> this same problem a couple of weeks ago, and I posted some stack
> traces from the Console to the list at that time - didn't get any
> commentary on that one. My eventual solution was to roll back
> temporarily (see next paragraph). This problem started showing up
> in some recent build of WOLips, in my case. The JDK 1.5 comment
> below is interesting, because the switch to 1.5 would have been
> about the time I started experiencing the problem (the specific
> build I was using at the time is in my post, I think).
>
> I had been planning to restore my computer for unrelated reasons,
> so I did that yesterday, and I did a fresh install of Xcode 2.4.1,
> Eclipse 3.2.2, using WOLips 3898 (also without Win Goodies &
> Maven). I haven't had any of the other problems mentioned with
> 3.2.2's Find & Install myself. I installed WOLips via the I tried
> switching explicitly to 1.5.0 (but this is my system default
> anyway) and for memory I used:
>
> -Xms256m
> -Xmx512m
>
> So... I can confirm that this is not an isolated incident. :-)
> Perhaps someone who is familiar with the WOLips code could make
> something of the stack traces I was seeing? These were taken from
> console.log, I believe.
>
> Clark
>
>
>
>> From: cpmueller
>> Subject: API files
>> Date: March 1, 2007 4:14:23 PM MST (CA)
>> To: woproject-de..bjectstyle.org
>>
>> Hey all,
>>
>> I'm appears that at some point in the last couple of weeks (I just
>> updated to the latest WOLips nightly), API editing has gone kaput.
>> I've noticed the following two problems when creating a new
>> component today. It just consists of a WOHyperlink, a couple of
>> conditionals, and a couple of strings. When I have it open and
>> create and save an API file by clicking on the "Api" tab, I am
>> able to edit the API, but when I try to save, I get a message
>> "Save Failed:Failed to save .api file." Similarly, if I create the
>> file externally (say, by right clicking on the .wo and saying
>> Generate API file... or by building it manually), I get an
>> assertion failure when I try to then edit the component. Stack
>> trace for the error upon save is as follows:
>>
>>
>>> !ENTRY org.eclipse.ui 2 0 2007-03-01 16:09:36.137
>>> !MESSAGE Save Failed
>>> !STACK 0
>>> java.lang.RuntimeException: Failed to save .api file.
>>> at org.objectstyle.wolips.apieditor.editor.ApiEditor.doSave
>>> (ApiEditor.java:105)
>>> at org.objectstyle.wolips.componenteditor.part.ApiTab.doSave
>>> (ApiTab.java:87)
>>> at
>>> org.objectstyle.wolips.componenteditor.part.ComponentEditorPart.doSa
>>> ve(ComponentEditorPart.java:198)
>>> .....
>>> Caused by:
>>> org.objectstyle.wolips.core.resources.types.api.ApiModelException: F
>>> ailed to save API file /Users/clark/Code/MIX/Eclipse/MIX/
>>> Components/ShowInvoiceLink.api.
>>> at
>>> org.objectstyle.wolips.core.resources.types.api.ApiModel.saveChanges
>>> (ApiModel.java:221)
>>> at
>>> org.objectstyle.wolips.core.resources.types.api.ApiModel.saveChanges
>>> (ApiModel.java:193)
>>> at org.objectstyle.wolips.apieditor.editor.ApiEditor.doSave
>>> (ApiEditor.java:102)
>>> ... 60 more
>>> Caused by: java.lang.IllegalArgumentException: Not supported:
>>> indent-number
>>> at org.apache.xalan.processor.TransformerFactoryImpl.setAttribute
>>> (TransformerFactoryImpl.java:574)
>>> at
>>> org.objectstyle.wolips.core.resources.types.api.ApiModel.saveChanges
>>> (ApiModel.java:212)
>>> ... 62 more
>>>
>>
>> When opening the .wo, the error looks like this:
>>
>>
>>> org.eclipse.core.runtime.AssertionFailedException: assertion failed:
>>> at org.eclipse.core.runtime.Assert.isTrue(Assert.java:109)
>>> at org.eclipse.core.runtime.Assert.isTrue(Assert.java:95)
>>> at org.eclipse.ui.part.MultiPageEditorPart.setActivePage
>>> (MultiPageEditorPart.java:688)
>>> at org.eclipse.ui.forms.editor.FormEditor.setActivePage
>>> (FormEditor.java:601)
>>> at org.eclipse.ui.part.MultiPageEditorPart.createPartControl
>>> (MultiPageEditorPart.java:280)
>>> at
>>> org.objectstyle.wolips.componenteditor.part.ComponentEditorTab.creat
>>> eInnerPartControl(ComponentEditorTab.java:78)
>>> at org.objectstyle.wolips.componenteditor.part.ApiTab.createTab
>>> (ApiTab.java:78)
>>> at
>>> org.objectstyle.wolips.componenteditor.part.ComponentEditorPart.crea
>>> tePages(ComponentEditorPart.java:167)
>>>
>>
>> The only components that appear to have this problem are ones that
>> have bindings defined, whether the API file actually exists or
>> not. Known issue? Bug time? Problem with my component?
>>
>> Clark
>
This archive was generated by hypermail 2.0.0 : Tue Apr 03 2007 - 08:19:55 EDT