RE: [JBoss-user] Classpath in Manifest file

[Sternagel Annegret (PN-SYS/DAS)]

If you put the home and remote interfaces of the beans into a jar into
jboss\lib\ext directory, you do not need to put hem into searchBean.jar (and
neither the new beanjar itself).

Annegret

> -----Original Message-----
> From: Rajesh Vilasrao Bhujbal [SMTP:[EMAIL PROTECTED]]
> Sent: Mittwoch, 1. August 2001 10:14
> To:   [EMAIL PROTECTED]
> Subject:      [JBoss-user] Classpath in Manifest file
> 
> Hi,
> I had created application which lists home and remote interface class of
> all deployed beans in Jboss. I had had used session bean named searchBean
> for this purpose. searchBean lists beans starting with JNDI name
> "interest/ ....".
>  
> it gives correct result only if I add home and remotes interface of all
> beans in searchBean.jar file. I also tried Manifest file Class-Path
> option. If I write more than two jar files (e.g. Class-Path: one.jar
> two.jar three.jar (carriage return at end)), it will will not add those
> jar files at deployment time. why is it so?
>  
> I don't want to modify my searchBean.jar even if new beans are added to
> jboss. is there any other option to avoid copying home and remote
> interfaces of all beans in searchBean.jar ? 
>  
> Rajesh

_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user