The real question is: why did it detect an EJB in the EAR?
jboss.j2ee:ear=MVCCSampleEAR.ear,jar=MVCCSampleEAR.ear,name=PersonManager,service=EJB3
What's the exact layout of the EAR?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244330#4244330
Reply to the pos
Here is a directory listing of the exploded EAR
[whitin...@localhost ear]$ ls -R
| .:
| META-INF MVCCSampleEJB.jar
|
| ./META-INF:
| application.xml jboss-app.xml MANIFEST.MF
|
and this is the jboss-app.xml contents.
| http://www.jboss.org/j2ee/dtd/jboss-app_4_2.dtd";>
|
Try removing the "Class-Path:" out of that MANIFEST.MF
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244674#4244674
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244674
__
What does your MANIFEST.MF file contain?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244542#4244542
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244542
___
jboss-user mai
Manifest-Version: 1.0
| Class-Path:
|
Jeremy
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244601#4244601
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244601
___
jbo
> jar -tf MVCCSampleEJB.jar
| META-INF/
| META-INF/MANIFEST.MF
| uk/
| uk/ac/
| uk/ac/xxx/
| uk/ac/xxx//
| uk/ac/xxx//mvcc/
| uk/ac/xxx//mvcc/ejb/
| uk/ac/xxx//mvcc/ejb/servicelocator/
| uk/ac/xxx//mvcc/impl/
| uk/ac/xxx//mvcc/model/
| uk/ac/xxx//
Although it was expected(/known) that the "Class-Path" entries in MANIFEST.MF
cause EJB3 deployments to malfunction, an empty Class-Path element wasn't
expected to cause anything like this. Could you please file a JIRA here
https://jira.jboss.org/jira/browse/EJBTHREE so we can track and fix it
So could you try removing the Class-Path from this MANIFEST.MF of the EJB jar?
We have known some issues where the MANIFEST.MF Class-Path entries caused EJB3
deployments to incorrectly deploy the artifacts.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=42446
Yes that was the problem. Removed the "Class-Path:" entry from the manifest
and it is working.
Thank you for your help.
Jeremy
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244707#4244707
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=p
Post the output of
jar -tf MVCCSampleEJB.jar
and if that EJB jar has a MANIFEST.MF, please post its contents too
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244686#4244686
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=repl
Removed "Class-Path:" and still the same error is reported at server startup.
Jeremy
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244678#4244678
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244678
___
Further update to my last post which was slightly misleading.
Examining again the MANIFEST there was is a control character x0f before the
carriage return and line feed which will explain things. Was a typo.
Trying the manifest again with "Class-Path:" but without the control
character and ev
12 matches
Mail list logo
