Hi Wayne, I already tried this and if i apply this TAG <version>5</version> it generates the DOCTYPE and i tried manually delete that TAG and added the modified jboss-app.xml and deployed that EAR on the jboss 5.1.2 EA version.
And WEBSERVICE able to generate WSDL from http://localhost:8080/jbossws/services it worked pretty well. If i deploy the MAVEN GENERATED jboss-app.xml i am getting Exception stack trace from the servlet something like below. org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'TestEjbHandlerImpl': Invocation of init method failed; nested exception is java.lang.LinkageError: loader constraint violation: loader (instance of org/jboss/web/tomcat/service/WebCtxLoader$ENCLoader) previously initiated loading for a different type with name "javax/xml/namespace/QName" THE ONLY WORK AROUND to resolve this problem is something like this. Apply your own jboss-app.xml under this folder structure and remove <jboss></jboss> tag from MAVEN EAR plugin and it will take your local version whenever you hit the mvn install command. |-- pom.xml `-- src `-- main `-- application `-- META-INF `-- jboss-app.xml TO ME it looks like MAVEN EAR PLUGIN team needs to work with Jboss TEAM and have to make this correction in MAVEN EAR PLUGIN. Thanks. On Thu, Feb 2, 2012 at 9:15 AM, Wayne Fay <[email protected]> wrote: > > I created one webservice and i am applying <version>5</version> and we > > are using Jboss 5.1.2EA version. > > > > And it's not able to generate WSDL if i apply DOCTYPE tag over there. > > If i remove that tag from jboss-app.xml it's working all right... > > Talk to the JBoss folks about that. Sounds like a bug on their side. > > > And another reason is if we change the Jboss version from 5.1.2EA to > > 6.0EA at that time also we have to change all our projects to apply > > version change in the POM file. > > This is most likely not true. The DOCTYPE simply says "this file > conforms to the following specification and version." There is nothing > which prevents JBoss v6 from accepting a JBoss v5 configuration file > -- many times app servers will intentionally accept older versions of > files to prevent such headaches and then internally up-convert the > file to the new format in memory or on disk during deployment. Again, > I'd talk to the JBoss folks about this to confirm this is actually > required. > > If you really want to remove the DOCTYPE, you will need to hack the > plugin to remove it, then make that an on/off configuration option. > > Wayne > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
