TheseĪre inscrutable, unsolvable, unhelpful messages that are complete and My number one dislike is the error reporting during deployment. Qualms with Java (EE) in general and WildFly in particular. If you do this you will not get conflicts.While I am a great advocate of adopting standards and have come toĭislike ducttaped together solutions of the years, I still have some ov.cdc.neds put only the custom jars in here which are not supplied with the jboss modules. ( I hope i am able to communicate here )Ģ. all the common jars or dependencies which are already their in the Jboss you should mentioned as dependencies and dont put them in the module which you are trying to create for your application.įor example xerces, jaxb, tools.jar ( jdk related ) mention it as modules inside the deployment sturcutre use all the jar modules. įirst Plan : Jboss Deployment should have following things.ġ. I think that should not be your approach. To me looks like that now you are trying to take out all the lib from the web-inf and trying to create the module for your specifically trying to put all the jars out there so that in jboss-deployment you can put only one module which deploys all the jar and so that there is no class loading issues any more. so in that way we can help to get to the point. give more information in terms of for example I have a ear and also have war, my application using following framework etc etc. I think you have to be more informative in terms of whether there is a ear inside the war or what exactly. WEB-INF/lib has servlet-2.3.jar thats why I am excluding in jboss-deployment-structure. Which I am referring in in standalone.xml, but I am still experimenting what will work and what will not but if contributers can and know the how exactly the class loader in Jboss is works and they can provide details in form of documentation it will be great help for most of the issues which is faced by user community. I had lot of issues while configuring the Camel Wildfly where camel patch uses spring framework and it uses web and context libraries but my camel application war file also used the spring framework and it will happen that even if I pack all the spring dependencies inside the war and deploy it inside the widlfly-camel patch release wildfly instance it was not able to resolve some of the classes between the wildfly-camel modules spring and the spring jars which were inside my war. My Question is can there be a flow chart which can assure that if we package things in certain way we will not have issue like above ? But in the current Modular Class loading, I have seen lots of issues when we have a module configured and also have same jar inside out lib. I see this was in WebLogic and Wepsphere earlier. There had been class loading strategy earlier that first the any class required will be loaded it will be done from Parent Class loader and then it will search locally inside the lib of war. I want to volunteer for writing and updating class loading document but I dont have much details unless I dig into the code.īut if contributors on forum can write a thumb rule based document it will be awesome. I think JBoss new class loader is some how in many ways is still a pain and things dont work as anticipated or described in the documentation. I think you should use xercesImpl not the Jboss one, just incase if you want to use xercesImpl-2.9.1-jbossas-2.jar, You can do so by putting inside your Jboss-deployment-structure the module as dependency.
0 Comments
Leave a Reply. |