Bug #575767. However, my description in the bug report turned out to be a
descripton of the symptoms, only. Which were I was getting class not found
exceptions on start up. When I looked closer at the log file, I discovered
further up in the log file there was a message that it could not find my jar,
that was referenced in the manifest, and so my jar was not deployed. So the ejbs
and wars that depended on it was throwing class not found errors. So then I
looked into the code and discovered that JBoss was not deploying the jar relative
to the expanded deploy directory like all other jars, etc. I changed the JBoss
code to make it do that and ran some tests and all seemed to work OK. It turned
out to be a simple code change.
For those that want to change their own code, do this:
Open up MainDeployer.java
go to method: parseManifestLibraries
Find this code:
if (sdi.isDirectory)
{
File parentDir = new File(sdi.url.getPath()).getParentFile();
lib = new File (parentDir, tk).toURL();
}
else
{
lib = new URL(sdi.url, tk);
}
Replace with:
if (sdi.isDirectory)
{
File parentDir = new File
(sdi.localUrl.getPath()+"-contents").getParentFile();
lib = new File (parentDir, tk).toURL();
}
else
{
File parentDir = new File (sdi.localUrl.getPath()+"-contents");
lib = new File (parentDir, tk).toURL();
}
Simon Stewart wrote:
> On Thu, Jul 18, 2002 at 08:50:13AM -0700, Greg Turner wrote:
> > This is properly explained in "Professional Java Server Programming J2EE
> > 1.3 Edition" by Wrox Press.
>
> Which is a good book, from what I hear. Must buy it at some point,
> obviously :)
>
> > What you want to do is put the classes that are used in both war and ejb
> > into a separate jar file. Put the jar file in the ear and reference it in
> > a Class-Path ref in the manifest file.
>
> This is just what I needed! Thank you.
>
> > Now I discovered a bug just recently in JBoss that caused these dependent
> > jars to not be deployed. Yesterday, I submitted a bug fix for this. I
> > think I made the correct fix, but it remains to be seen if my fix finds its
> > way into the next release.
>
> What was the bug number? I'd be interested to see whether the fix gets
> pulled into JBoss. Until it is fixed, I'll be running everything in
> the same JVM in any case. Is it okay to put the common classes in the
> ejb.jar for now?
>
> Cheers,
>
> Simon
>
> --
> If you give a man a fire, he'll be warm for a day. If you set a man on fire,
> he'll be warm for the rest of his life.
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-user
--
Greg Turner, JBoss Authorized Consultant
Tiburon Enterprise Systems
http://www.tiburon-e-systems.com
Box 1171
Tiburon, CA 94920
415-332-3363
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
