Hi Armin,

The problem went away when I upgraded to jBoss-3.0.6.

One that I noticed in build-xdoclet.xml (although it didn't end up being the cause of the problem) is that the MANIFEST.MF classpath syntax is supposed to be

Class-Path: xxx.jar yyy.jar

rather than

classpath: xxx.jar yyy.jar

To be more consistent wouldn't it be better to include all the jars that the beans are dependent on, like:

Class-Path: db-ojb-1.0.rc2.jar db-ojb-1.0.rc2-junit.jar

as well as the libs required (like commons-lang-1.0-mod.jar etc.) in the build-xdoclet.xml file.

At the moment only the junit jar is listed.

Thanks,

Phil



Armin Waibel wrote:
> Hi Phil,
>
> I tested CVS with jboss 3.0.4 + 3.0.6
> using sapDB.
> I use the same directory structure:
>
> ojb.sar
> |---------------META-INF
> |                              |
> |                       MANIFEST.MF, jboss-service.xml
> db-ojb-xxx-beans.jar
> db-ojb-xxx.jar
> ojb config files
>
> Did you use current build.xml/xdoclet-build.xml file, I made
> some minor changes (as far as I know;-))
>
>
> regards,
> Armin
>
> ----- Original Message -----
> From: "Phil Warrick" <[EMAIL PROTECTED]>
> To: "OJB Users List" <[EMAIL PROTECTED]>
> Sent: Tuesday, March 18, 2003 3:57 PM
> Subject: [jBoss deployment]: example ejb beans not deploying
>
>
>
>>Hi all,
>>
>>It looks like Armin has done a nice job of improving the
>
> out-of-the-box
>
>>ejb deployment experience.  But something about the new arrangement,
>>where a sar directory containing
>>
>>db-ojb-xxx-beans.jar
>>db-ojb-xxx.jar
>>ojb configuration files
>>jboss META-INF descriptor files
>>
>>causes the beans to not see the classes within db-ojb-xxx.jar.  I get
>>errors like NoClassDefFound for OJBRuntimeException, which is
>
> certainly
>
>>located in db-ojb-xxx.jar.  The OJB services do deploy fine if I leave
>>out the beans jar.  I noticed that the deployer is now a RAR which
>
> might
>
>>influence dependencies.
>>
>>My environment is Win2K, jboss 3.0.4, ojb 1.0rc+  What is your
>>environment Armin?
>>
>>I'm checking the jBoss archives and also watching for clues about the
>>redeployment problem.
>>
>>Any ideas would be most appreciated.
>>
>>Phil
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: [EMAIL PROTECTED]
>>For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>>
>
>




--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to