> This may be due to an IBM bug. I have found this thread online:
>
>
> http://www-128.ibm.com/developerworks/forums/dw_thread.jsp?message=1729665&cat=9&thread=31014&treeDisplayType=threadmode1&forum=275#1729665 
>
>
> Basically, a bunch of people complaining but no solution provided.
>
> I also found this:
>
>   http://www-1.ibm.com/support/docview.wss?uid=swg21221199
>
> Have you tried restarting the app server?
>
> -Erik
>
> Pavel Jbanov wrote:
>> Hi Erik,
>>
>> Here is what I get with the nightly build:
>>
>>
>>   Orbeon Forms Error
>>
>> Type     class java.lang.VerifyError
>> Message     class loading constraint violated (class:
>> org/orbeon/saxon/style/StyleElement method:
>> getNamespaceResolver()Lorg/orbeon/saxon/om/NamespaceResolver;) at pc: 0
>> Stack Trace    
>>
>> java.lang.VerifyError: class loading constraint violated (class:
>> org/orbeon/saxon/style/StyleElement method:
>> getNamespaceResolver()Lorg/orbeon/saxon/om/NamespaceResolver;) at pc: 0
>>     at java.lang.J9VMInternals.verifyImpl(Native Method)
>>     at java.lang.J9VMInternals.verify(J9VMInternals.java:59)
>>     at java.lang.J9VMInternals.verify(J9VMInternals.java:57)
>>     at java.lang.J9VMInternals.initialize(J9VMInternals.java:120)
>>     at
>> org.orbeon.saxon.style.StyleNodeFactory.makeXSLElement(StyleNodeFactory.java:340)
>>
>>     at
>> org.orbeon.saxon.style.StyleNodeFactory.makeElementNode(StyleNodeFactory.java:82)
>>
>>     at
>> org.orbeon.saxon.tree.TreeBuilder.startContent(TreeBuilder.java:179)
>>     at
>> org.orbeon.saxon.style.UseWhenFilter.startContent(UseWhenFilter.java:158)
>>
>>     at
>> org.orbeon.saxon.event.StartTagBuffer.startContent(StartTagBuffer.java:131)
>>
>> ...
>>      
>>
>>
>> Thanks,
>>
>> Pavel
>>
>> Erik Bruchez wrote:
>>> Alessandro Vernet wrote:
>>>> Hi Pavel,
>>>>
>>>> The issue you're having on WebSphere 5.1 is likely to be due to a
>>>> class conflict. The class DefaultHandler2 comes with SAX2, and maybe
>>>> WebSphere 5.1 comes with SAX1 and those classes get used by default.
>>>> Is using WebSphere 6 an option for you? If it is, I would go this
>>>> route.
>>>>
>>>> For the additional "/", I can't seem to be able to reproduce this. I
>>>> am tracing the Ajax requests, but don't see any additional "/". Are
>>>> you getting this just when going to Orbeon Forms examples that ship
>>>> with Orbeon Forms?
>>>
>>> I think the issue of the "//" was fixed recently.
>>>
>>> Pavel, you may have better luck with a nightly build and WS 6.1:
>>>
>>>   http://forge.objectweb.org/nightlybuilds/ops/ops/
>>>
>>> -Erik
>>>
>>
>
>