[at7000ft]

When an ear/jar/war is deployed to JBoss with a version of log4j.jar several pages of log4j related errors are dumped to the console (JBoss has it in it’s lib). Everything still runs but the problem is solved by simply not depoying log4j.jar as a dependent jar. Question is since log4j.jar is a part of the XFire Core Libraries which are needed in a MyEclipse Web Service project is it possible to control which jars are deployed (or not) with the war?

Thanks

Rick H

[Riyad Kalla]

Rick,
We currently don’t support deployment filtering on a file-by-file basis (will add it in a future release) but what you can do is filter by type of JAR. What you can do is edit the contents of the XFire libraries by going to Window > Prefs > MyEclipse > Project Capabilities, after that, if you still need Log4J, you can manually add it to your build path, then under your project properties and under MyEclipse > Deployment, you can turn off the deployment of external JARs to avoid sending it back out.

[d_pavel]

Hi All,

Ryiad would you so kind to be more specific abot this :

then under your project properties and under MyEclipse > Deployment, you can turn off the deployment of external JARs to avoid sending it back out.

I mean I did the first part of what you said but the deployed war still contains the log.4j …
Now I can access MyEclipse > Web > Deployment but not MyEclipse > Deployment …
Once again I don’t see the option to “turn off the deployment of external JARs” unless you create a web project, but in my case I created a web service project and under project properties – MyEclipse > Deployment – I don’t have this option available.

Please guide me to what I’m not doing right.

Thanks in advance.

[Riyad Kalla]

d_pavel,
I’m sorry that was a mistype, you found the correct screen. I would suggest just removing Log4J from the project library for now. WE will address this issue in our 5.5 release with a filtering mechanism. It isn’t our all-out-deployment filtering, but will be able to handle situations like this.

[roger_pearse]

This message has not been recovered.

[Author]

Posts