Not applicable
19-03-2008
07:27 PDT
- Mark as New
- Follow
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report
I had the exact same problem. I solved it to change my
application from a ear deployment to a war deployment. This was
when I was using JBoss.
The people on the JBoss channel tried to explain me but you
need to make profisions to make the jar available 'at some point'
Unfortunately I am not extremely knowledgable in that area
and I cannot really help you to solve using a ear deployment, just
that I know about the problem and it has something todo how ear
deployments work.
So for me it was simple and I changed it to .war
ries
application from a ear deployment to a war deployment. This was
when I was using JBoss.
The people on the JBoss channel tried to explain me but you
need to make profisions to make the jar available 'at some point'
Unfortunately I am not extremely knowledgable in that area
and I cannot really help you to solve using a ear deployment, just
that I know about the problem and it has something todo how ear
deployments work.
So for me it was simple and I changed it to .war
ries
Views
Replies
0 Likes
Total Likes