File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes EJB and other Java EE Technologies and the fly likes Incompatible Java EE specification level? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "Incompatible Java EE specification level?" Watch "Incompatible Java EE specification level?" New topic
Author

Incompatible Java EE specification level?

Mark E Hansen
Ranch Hand

Joined: Apr 01, 2009
Posts: 643
I hope I'm in the correct forum. Please correct me otherwise.

I'm trying to learn how to build a J2EE application consisting of some EJBs and a web application consisting of a Servlet.
I'm using Eclipse 3.5.1 (Galileo) with Eclipse JBoss Tools, JBoss AS 5.1.0 and Java 1.6.0_06.

I followed this tutorial for creating the J2EE application:

http://www-wi.uni-muenster.de/pi/lehre/ss09/EAI/tutorials/tutorial_jboss_project.html

which worked mostly fine. However, when I build I notice the following warning in the IDE:

IWAE0008E The module "library-ejb.jar" is at an incompatible Java EE specification level than that of the "library]:library" Enterprise Application.

FYI: The J2EE application name is "library", the EJB component is named "library-ejb" and the web application component is named "library-web".

I'm not sure if this is a problem, as the application compiles and runs. However, it seems like something I should correct. I've been all through the deployment descriptors, but can't tell what it's telling me is wrong.

Can someone please tell me how I can correct this? I've searched for this warning (by number and text) and can't find anything which proposes a solution.

I know I'll have more questions, but just wanted to use this as a way to get my feet wet in this forum.

Thanks for any pointers.
Jaikiran Pai
Marshal

Joined: Jul 20, 2005
Posts: 10090
    
164

IWAE0008E The module "library-ejb.jar" is at an incompatible Java EE specification level than that of the "library]:library" Enterprise Application.


I haven't heard of that before. And a google search shows up results for IBM related message property files. What does your ejb-jar.xml (if any) look like and also the application.xml. Probably it's comparing the xsd declaration on these 2 files and complaining about some mismatch.

[My Blog] [JavaRanch Journal]
Mark E Hansen
Ranch Hand

Joined: Apr 01, 2009
Posts: 643
Here's the ejb-jar.xml:



And here is the application.xml:



Just in case it's helpful, here's the web.xml for the web application component:



Thank you for your help.
Leonardo Carreira
Ranch Hand

Joined: Apr 07, 2009
Posts: 489

Hi Mark E Hansen..

Try to change your Namespace configuration in application.xml, as below :


Hope that helps..


Sorry, perhaps my english language isn't too good.. Prepare for SCJP 6, Please God help me.. ☼
References : [Java.Boot] [JavaChamp] [JavaPrepare]
Mark E Hansen
Ranch Hand

Joined: Apr 01, 2009
Posts: 643
Thanks, that got rig of the warning. I wonder why the tutorial had the wrong version numbers? Whey they just old?

Thanks again!

Leonardo Carreira
Ranch Hand

Joined: Apr 07, 2009
Posts: 489

Please post rig of the warnings, thanks..
Mark E Hansen
Ranch Hand

Joined: Apr 01, 2009
Posts: 643
Leonardo Carreira wrote:Please post rig of the warnings, thanks..


I'm sorry, I don't understand what you mean by "post rig of the warnings".

I think I spoke too soon. I made the changes to the application.xml file, compiled the application and saw the warning go away. However, a couple minutes later the warning came back. I've verified that the application.xml file is as you suggested. I'll include it here just in case I missed something:



Can you see what I've done wrong?

Thanks,

Leonardo Carreira
Ranch Hand

Joined: Apr 07, 2009
Posts: 489

Mark E Hansen wrote:
I'm sorry, I don't understand what you mean by "post rig of the warnings".

sorry, i was mistaken use words, what i meant was you're still got error, and i told you to post the warning messages...
sorry about my english..

How about if you try to change your application.xml as below :



and please post the warning messages that told by JBoss..
Thanks..
Jaikiran Pai
Marshal

Joined: Jul 20, 2005
Posts: 10090
    
164

Mark E Hansen wrote:I've verified that the application.xml file is as you suggested. I'll include it here just in case I missed something:





It's not the same It should be:


Mark E Hansen
Ranch Hand

Joined: Apr 01, 2009
Posts: 643
Oh, I see. "j2ee" -> "javaee".

I've made that change.

Note that I think there must be something wrong with Eclipse, as the warning will come and go without making changes to the application. I can't understand why that is happening. In one case I remember, I saw the warning, re-built the application with no changes and the warning was still there. I walked away and came back to it a few minutes later and the warning was gone. Perhaps Eclipse is building in the back ground (although I have that turned off)?

Now, I'm getting the following error now when I launch Eclipse:



and I see only the deployment descriptors in the project explorer - all the application files are no longer showing. I think it's time to abandon this J2EE application and start a fresh one. I'll report back once I've done that and see where I'm at.

Thanks again for all the help.



Mark E Hansen
Ranch Hand

Joined: Apr 01, 2009
Posts: 643
Well, I created the application from scratch (following the tutorial) and it is once again working properly.

I don't know what caused the warning (mentioned at the beginning of this thread). The first time I created the application it worked as well. The warning showed up later, so it may happen again.

Once thing I noticed is that this time around, there is no application.xml file. However, I was able to build/deploy/run the application. I don't know why there isn't one now when there was one the first time.

Thanks again,

 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Incompatible Java EE specification level?