[JBoss AS Development Deployment Framework] - Linkage Error
by powerpuff
powerpuff [https://community.jboss.org/people/powerpuff] created the discussion
"Linkage Error"
To view the discussion, visit: https://community.jboss.org/message/795224#795224
--------------------------------------------------------------
I am trying to migrate my application from Jboss 4 to Jboss 6.
Its a web service application, which is using Axis2 implementation.
Below jars are reffered by Axis2
<fileset id="axis.runtime.fileset" dir="${common.lib.dir}/axis2/1_4_1">
<include name="axis2-kernel-1.4.1.jar"/>
<include name="axiom-api-1.2.7.jar"/>
<include name="axiom-impl-1.2.7.jar"/>
<include name="neethi-2.0.4.jar"/>
<include name="woden-api-1.0M8.jar"/>
<include name="woden-impl-dom-1.0M8.jar"/>
<include name="wsdl4j-1.6.2.jar"/>
<include name="xmlbeans-2.3.0.jar"/>
<include name="axis2-adb-1.4.1.jar"/>
<include name="XmlSchema-1.4.2.jar"/>
<include name="axis2-spring-1.4.1.jar"/>
<!--include name="stax-1.2.0.jar"/-->
</fileset>
If i include stax-api jar in project build, it is failing during deployment. If i remove stax api jar from application build, i am able to deploy the application successfully but when i try to access the web services i get below linage error:
[org.apache.axis2.transport.http.AxisServlet] loader constraint violation in interface itable initialization: when resolving method "org.apache.axiom.om.impl.llom.OMStAXWrapper.getName()Ljavax/xml/namespace/QName;" the class loader (instance of org/jboss/classloader/spi/base/BaseClassLoader) of the current class, org/apache/axiom/om/impl/llom/OMStAXWrapper, and the class loader (instance of <bootloader>) for interface javax/xml/stream/XMLStreamReader have different Class objects for the type javax/xml/namespace/QName used in the signature: java.lang.LinkageError: loader constraint violation in interface itable initialization: when resolving method "org.apache.axiom.om.impl.llom.OMStAXWrapper.getName()Ljavax/xml/namespace/QName;" the class loader (instance of org/jboss/classloader/spi/base/BaseClassLoader) of the current class, org/apache/axiom/om/impl/llom/OMStAXWrapper, and the class loader (instance of <bootloader>) for interface javax/xml/stream/XMLStreamReader have different Class objects for the type javax/xml/namespace/QName used in the signature
at org.apache.axiom.om.impl.llom.OMElementImpl.getXMLStreamReader(OMElementImpl.java:752) [:]
at org.apache.axiom.om.impl.llom.OMElementImpl.getXMLStreamReaderWithoutCaching(OMElementImpl.java:726) [:]
at com.fdc.valuelink.endpoint.ValueLinkTransactionMessageReceiverInOut.fromOM(Unknown Source) [:]
at com.fdc.valuelink.endpoint.ValueLinkTransactionMessageReceiverInOut.invokeBusinessLogic(Unknown Source) [:]
at org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40) [:]
at org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:100) [:]
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:176) [:]
at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275) [:]
at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:133) [:]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754) [:1.0.0.Final]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [:1.0.0.Final]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:324) [:6.0.0.Final]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [:6.0.0.Final]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [:6.0.0.Final]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) [:6.0.0.Final]
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:181) [:6.0.0.Final]
at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.event(CatalinaContext.java:285) [:1.1.0.Final]
at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.invoke(CatalinaContext.java:261) [:1.1.0.Final]
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:88) [:6.0.0.Final]
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:100) [:6.0.0.Final]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) [:6.0.0.Final]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [:6.0.0.Final]
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) [:6.0.0.Final]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [:6.0.0.Final]
at org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.invoke(ActiveRequestResponseCacheValve.java:53) [:6.0.0.Final]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [:6.0.0.Final]
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [:6.0.0.Final]
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:654) [:6.0.0.Final]
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) [:6.0.0.Final]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_31]
I have read in many posts that including stax api in application lib causes linkage error, here i dont have stax api jar in my application lib folder still its giving linkage error. i am using Java 6 on my server.
Can anyone please help in resolving this error?
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/795224#795224]
Start a new discussion in JBoss AS Development Deployment Framework at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
11 years, 11 months
Re: [jboss-dev-forums] [PicketBox Development] - JBoss AS7: Enabling JASPI Authentication for Web Applications
by 61 Monzillo
61 Monzillo [https://community.jboss.org/people/monzillo] commented on the document
"JBoss AS7: Enabling JASPI Authentication for Web Applications"
To view all comments on this document, visit: https://community.jboss.org/docs/DOC-17782#comment-11491
--------------------------------------------------
validateRequest *should* be called under HttpServletRequest.authenticate; but that has not yet been made explicit in the Servlet Profile of JSR 196 (and will be the subject of the next MR to the spec). ValidateRequest should not be called under HttpServletRequest.login mostly because login presumes a user name/password authentication mechanism (which may not be compatible with the configured auth context). it might be worth considering having login use the callback handler to handle a passwordValidationCallback (if jsr 196 is configured for the app), in which case the login impl login would need access to the same callback handler that was passed to the 196 auth context configured for the app. I will think about how that might be possible, but at this time, the main integration point for jsr 196 and programmatic login should be authenticate (not login).
--------------------------------------------------
11 years, 11 months
[JBoss Tools Development] - JBoss Central - How Does It Work?
by Nick Boldt
Nick Boldt [https://community.jboss.org/people/nickboldt] modified the document:
"JBoss Central - How Does It Work?"
To view the document, visit: https://community.jboss.org/docs/DOC-48297
--------------------------------------------------------------
JBoss Central, based on http://wiki.eclipse.org/Mylyn/Discovery Mylyn Discovery, is in part a UI for installing new features into Eclipse or JBDS. It provider a richer, yet simpler UI than what Eclipse's p2 Install Manager provides out of the box.
*The Software/Update tab in Central is backed by three levels of metadata:*
* directory.xml file listing 1 or more discovery plugins (eg., 1 for the Core features, 1 for the Integration Stack (formerly SOA Tooling) features)
* discovery plugin(s), which define groups of features ("Connectors") to be installed. This amounts to little more than a plugin.xml and some icons.
* update site(s) referenced by the discovery plugin(s), which host the features to be installed. Sites can be 3rd party vendors' sites, or can be mirrored on download.jboss.org / devstudio.jboss.com for better guarantee of performance / version. Each connector can only define a SINGLE URL for that group of features, however. But that single URL can be a composite site, which in turn points to more than 1 site.
*There are two simple rules to follow when writing your discovery plugin.xml:*
* connectorIDs must be stable - should not change between releases
* Where license terms permit, 3rd party content should be mirrored first onto download.jboss.org and/or devstudio.jboss.com, so that the site content can be more easily controlled / guaranteed
*How about some working examples?*
* *JBoss Tools 3.3** http://download.jboss.org/jbosstools/updates/stable/indigo/jbosstools-dir... http://download.jboss.org/jbosstools/updates/stable/indigo/jbosstools-dir... (Source: https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/j... jbosstools-directory.xml)* Contains both Core and SOA - points at the following jars:* org.jboss.tools.central.discovery_.*.jar (Source: https://anonsvn.jboss.org/repos/jbosstools/branches/jbosstools-3.3.x/cent... plugin.xml)
* org.jboss.tools.central.discovery.soa-tooling_*.jar (Source: https://anonsvn.jboss.org/repos/jbosstools/branches/jbosstools-3.3.x/buil... plugin.xml)
* Each jar's plugin.xml then lists a number of connectors, which are groups of features wrapped by a simpler UI than what Eclipse's p2 Install Manager provides out of the box.
* *JBoss Developer Studio 5.0** https://devstudio.jboss.com/updates/5.0/devstudio-directory.xml https://devstudio.jboss.com/updates/5.0/devstudio-directory.xml (Source: http://svn.jboss.org/repos/devstudio/trunk/devstudio.jboss.com/updates/5.... devstudio-directory.xml)* Contains both Core and SOA - points at the following jars:* com.jboss.jbds.central.discovery_*.jar (Source: https://svn.jboss.org/repos/devstudio/branches/devstudio-5.0.x/product/pl... plugin.xml)
* com.jboss.jbds.central.discovery.soa-tooling_*.jar (Source: https://svn.jboss.org/repos/devstudio/branches/devstudio-5.0.x/product-so... plugin.xml)
* Each jar's plugin.xml then lists a number of connectors.
* *JBoss Tools 4.0** http://download.jboss.org/jbosstools/updates/stable/juno/jbosstools-direc... http://download.jboss.org/jbosstools/updates/stable/juno/jbosstools-direc... (Source: https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/j... jbosstools-directory.xml)* Contains both Core and SOA - points at the following jars:* org.jboss.tools.central.discovery_.*.jar (Source: https://github.com/jbosstools/jbosstools-central/blob/jbosstools-4.0.x/ce... plugin.xml)
* org.jboss.tools.central.discovery.soa-tooling_*.jar (Source: https://github.com/jbosstools/jbosstools-build-sites/blob/jbosstools-4.0.... plugin.xml - +*SUBJECT TO CHANGE*+)
* Each jar's plugin.xml then lists a number of connectors.
* *JBoss Developer Studio 6.0** https://devstudio.jboss.com/updates/5.0/devstudio-directory.xml https://devstudio.jboss.com/updates/6.0/devstudio-directory.xml (Source: http://svn.jboss.org/repos/devstudio/trunk/devstudio.jboss.com/updates/6.... devstudio-directory.xml)* Contains both Core and SOA - points at the following jars:* com.jboss.jbds.central.discovery_*.jar (Source: https://svn.jboss.org/repos/devstudio/branches/devstudio-6.0.x/product/pl... plugin.xml)
* com.jboss.jbds.central.discovery.soa-tooling_*.jar (Source: https://svn.jboss.org/repos/devstudio/branches/devstudio-6.0.x/product-so... plugin.xml - +*SUBJECT TO CHANGE*+)
* Each jar's plugin.xml then lists a number of connectors.
* In JBDS 6, these connectors (feature groups) are now labelled as "Tested" or "Supported".
--------------------------------------------------------------
Comment by going to Community
[https://community.jboss.org/docs/DOC-48297]
Create a new document in JBoss Tools Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]
11 years, 11 months
[JBoss Tools Development] - JBoss Central - How Does It Work?
by Nick Boldt
Nick Boldt [https://community.jboss.org/people/nickboldt] modified the document:
"JBoss Central - How Does It Work?"
To view the document, visit: https://community.jboss.org/docs/DOC-48297
--------------------------------------------------------------
*Central consists of three levels of metadata:*
* directory.xml file listing 1 or more discovery plugins (eg., 1 for the Core features, 1 for the Integration Stack (formerly SOA Tooling) features)
* discovery plugin(s), which define groups of features ("Connectors") to be installed. This amounts to little more than a plugin.xml and some icons.
* update site(s) referenced by the discovery plugin(s), which host the features to be installed. Sites can be 3rd party vendors' sites, or can be mirrored on download.jboss.org / devstudio.jboss.com for better guarantee of performance / version. Each connector can only define a SINGLE URL for that group of features, however. But that single URL can be a composite site, which in turn points to more than 1 site.
*There are two simple rules to follow when writing your d**iscovery plugin.xml:*
*
*
* connectorIDs must be stable - should not change between releases
* Where license terms permit, 3rd party content should be mirrored first onto download.jboss.org and/or devstudio.jboss.com, so that the site content can be more easily controlled / guaranteed
*How about some working examples?*
JBoss Tools 3.3:
* http://download.jboss.org/jbosstools/updates/stable/indigo/jbosstools-dir... http://download.jboss.org/jbosstools/updates/stable/indigo/jbosstools-dir... (Source: https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/j... https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/j... )* Contains both Core and SOA - point at the following jars:* org.jboss.tools.central.discovery_1.0.1.v20130112-0624-H128-Final.jar
* org.jboss.tools.central.discovery.soa-tooling_1.0.0.v20121025-2148-H3-GA.jar
* Each jar contains a plugin.xml file:* Source: https://github.com/jbosstools/jbosstools-central/blob/master/central/plug... https://github.com/jbosstools/jbosstools-central/blob/master/central/plug...
* Source: https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat...
JBoss Developer Studio 5.0:
* https://devstudio.jboss.com/updates/5.0/devstudio-directory.xml https://devstudio.jboss.com/updates/5.0/devstudio-directory.xml (Source: http://svn.jboss.org/repos/devstudio/trunk/devstudio.jboss.com/updates/5.... http://svn.jboss.org/repos/devstudio/trunk/devstudio.jboss.com/updates/5.... )* Contains both Core and SOA - point at the following jars:* com.jboss.jbds.central.discovery_1.0.1.v20130119-0035-H249-GA.jar
* com.jboss.jbds.central.discovery.soa-tooling_1.0.2.v20121213-1115-H6-GA.jar
* Each jar contains a plugin.xml file:* Source: https://github.com/jbosstools/jbosstools-central/blob/master/central/plug... http://svn.jboss.org/repos/devstudio/trunk/product/plugins/com.jboss.jbds...
* Source: https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... http://svn.jboss.org/repos/devstudio/trunk/product-soa/plugins/com.jboss....
--------------------------------------------------------------
Comment by going to Community
[https://community.jboss.org/docs/DOC-48297]
Create a new document in JBoss Tools Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]
11 years, 11 months
