[
https://issues.apache.org/jira/browse/JS2-973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12707301#action_12707301
]
Ate Douma commented on JS2-973:
-------------------------------
I found another issue on WAS 6.1 while running the (full) JSR-286 TCK.
It turns out IBM JDK5 has a bug causing the following exception:
java.lang.TypeNotPresentException: Type
javax.xml.bind.annotation.XmlRootElement not present
at
com.ibm.oti.reflect.AnnotationHelper.getAnnotation(AnnotationHelper.java:38)
at
com.ibm.oti.reflect.AnnotationHelper.getDeclaredAnnotations(AnnotationHelper.java:50)
at java.lang.Class.getDeclaredAnnotations(Class.java:1620)
at java.lang.Class.getAnnotations(Class.java:1581)
at java.lang.Class.getAnnotation(Class.java:1561)
at
com.sun.xml.bind.v2.model.annotation.RuntimeInlineAnnotationReader.getClassAnnotation(RuntimeInlineAnnotationReader.java:102)
at
com.sun.xml.bind.v2.model.annotation.RuntimeInlineAnnotationReader.getClassAnnotation(RuntimeInlineAnnotationReader.java:53)
at
com.sun.xml.bind.v2.model.impl.ModelBuilder.getTypeInfo(ModelBuilder.java:325)
at
com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextImpl.java:442)
at
com.sun.xml.bind.v2.runtime.JAXBContextImpl.<init>(JAXBContextImpl.java:297)
at
com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:139)
at
com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:117)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:211)
at javax.xml.bind.ContextFinder.find(ContextFinder.java:372)
at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:574)
at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:522)
at
org.apache.jetspeed.events.EventCoordinationServiceImpl.serialize(EventCoordinationServiceImpl.java:282)
...
I found several references to this problem, for example:
https://issues.apache.org/jira/browse/TUSCANY-2519
This bug seems to be solved with IBM JDK6, but for Websphere 6.1 we have to
deal with it.
The only (but working) solution I could find was moving the jaxb-api-2.1.jar
from jetspeed/WEB-INF/lib to the shared libraries.
But I don't think we should solve it by doing that as general solution, e.g.
move that jar to shared for every installation.
Our general rule is to keep dependencies in shared to the utmost minimum, to
guard against possibly version clashes when for a custom portal a newer (or
older) version would be required there.
And, this is really only a IBM JDK5 bug.
However, we can provide documentation/instructions how to customise a *WAR*
based installation and deployment on Websphere 6.1
And, for EAR based deployments, we can support this by adjusting our enterprise
ear build to extract the jaxb-api-2.1.jar from the jetspeed.war and move it to
the shared jars within the ear itself.
That won't affect other installations, so will not violate our general rule
above.
I'll will start working on adding this to the enterprise-ear project.
> Running Jetspeed 2.2 on Websphere 6.1 / Oracle10
> ------------------------------------------------
>
> Key: JS2-973
> URL: https://issues.apache.org/jira/browse/JS2-973
> Project: Jetspeed 2
> Issue Type: Task
> Affects Versions: 2.2.0
> Reporter: Ate Douma
> Assignee: Ate Douma
> Fix For: 2.2.0
>
>
> Testing current Jetspeed 2.2-SNAPSHOT on Websphere 6.1 I;'ve encountered some
> issues which I'm recording here for the record and/or as outstanding TODO
> tasks.
> - xml-apis jar: all the JAXP apis are now part of Java5+ and having this jar
> in WEB-INF/lib causes problems on Websphere
> TODO: remove/exclude this dependency in maven poms
> - stax-api-1.0.1.jar: this artifact (incorrectly) contains
> javax.xml.namespace.* classes (QName specifically) which breaks JAXB on
> Websphere
> TODO: upgrade to stax-api-1.0.2.jar which no longer contains the
> javax.xml.namespace package
> - DDLUtils generates SEQUENCE seq_SECURITY_DOMAIN_DOMAIN_ID and TRIGGER
> trg_SECURITY_DOMAIN_DOMAIN_ID for SECURITY_DOMAIN.UIX_DOMAIN_NAME for an
> Oracle database
> During creation of the schema in the database the trigger code fails to be
> created. However, both the sequence and the trigger are not needed anyway.
> TODO: figure out how to disable the sequence and trigger generation from
> DDLUtils
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
