This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I noticed that the weblogic.xml is generated automatically when you, lets say, create a new netbeans project and specify that you are going to use weblogic. it's specific to weblogic, and I have tried to take one of my Sun Java App Server 8.2 projects and deploy it on weblogic, but it doesn't work unless the project has weblogic.xml ahead of time. (not sure if this is the only difference between projects made for Weblogic and projects made for sun app server)
weblogic.xml is not required for an application to be deployed to WL. At least for WL10 and I think it was the same for WL7, I can't speak to any other versions. I have several apps deployed to WL, some use it some don't. It's for setting some WL specific configs and some other configs which are not necessarrily WL specific. Some of them can even be set by other means if I'm not mistaken. If you are trying to deploy to WL and it is complaining about not having a weblogic.xml then I suspect Netbeans is setting something in your project build archive which is in turn instructing WL to look for weblogic.xml on deployment. All JEE app-servers typically have some server specific config files which can be included in the app archive, though they are not necessarrily required.
Joined: Apr 09, 2010
I suppose in that case it never hurts to have a blank weblogic.xml file?