-
15. Re: EJB 3.0 Entity problem - Error: Incomplete Deployment li
The folder's name is in capital letters, the output of that command just showed it in lowercase. I also verified this by unjarring the jar file and it is in caps there too.
-
16. Re: EJB 3.0 Entity problem - Error: Incomplete Deployment li
That's actually weird. Can you just delete that META-INF folder and manually create a new one and place the persistence.xml in there? Also, you did not mention how you are creating that jar file.
-
17. Re: EJB 3.0 Entity problem - Error: Incomplete Deployment li
Just tried that and still didn't work...
I will try to check back here later, I have to leave for a few hours.
To create the jar file:jar cvf %JBOSS_HOME%\server\default\deploy\tps-entity.jar tps\entity\Flight.class META-INF\persistence.xml tps\entity\IFlight.class tps\entity\FlightBean.class
Thanks. -
18. Re: EJB 3.0 Entity problem - Error: Incomplete Deployment li
"HappyNewYear" wrote:
The folder's name is in capital letters, the output of that command just showed it in lowercase. I also verified this by unjarring the jar file and it is in caps there too.
Don't trust Windows case-sensitivitym trust the output of "jar". :)
This explanation would be consistent with the errors you're getting.
S,
ALR -
19. Re: EJB 3.0 Entity problem - Error: Incomplete Deployment li
You were right. I changed it manually and it successfully deployed! Thanks for the help!
-
20. Re: EJB 3.0 Entity problem - Error: Incomplete Deployment li
I just ran into the same issue. I found the answer here, which is good, but I'm curious if this is a bug? I'm working from the O'Reilly EJB 3.0 book (5th ed) and the introductory example shows the persistence unit's name being specified. "Should" that have worked?
Thanks! -
21. Re: EJB 3.0 Entity problem - Error: Incomplete Deployment li
Yes it was a bug - in my code not in JBoss. My capitalization of the unit names was different in the annotation and persistence.xml. Sorry for the "noise".
-
22. Re: EJB 3.0 Entity problem - Error: Incomplete Deployment li
I too have been victim to this 'case insensitivity'. Only took me a day to finally find this thread. Spent a lot of time using Google, but it never delivered this. What was maddening for me was I had one jar that worked, because I used Eclipse-export-jar and put the persistence.xml in that, and had another version using Ant and had the case wrong. To make it worse, I used Winzip to view the jars and it shows lower case folders by default. Lesson for me...search the forum!
Thanks,
Herman Post