What would be cool is if jboss eventually used a ClassLoader system that
allowed service classes to be self-contained. In other words,
jbossmq-service.xml could have:
<classpath lib="jbossmq.jar">
<export classes="org.jboss.mq.*">
<export classes="org.jboss.mq.il.**">
<export classes="org.jboss.mq.il.*">
</classpath>
<classpath lib="concurrent-1.x.jar"/>
Only the classes explicitly exported would be made available to the other
services. This would let jbossmq use ver 1.x of concurrent.jar while
another service used version 2.x of concurrent.jar since it's classes were
not exported.
Just an idea.
Regards,
Hiram
>From: Jason Dillon <[EMAIL PROTECTED]>
>To: Hiram Chirino <[EMAIL PROTECTED]>
>CC: [EMAIL PROTECTED],
>[EMAIL PROTECTED]
>Subject: Re: [JBoss-dev] Property access in *service.xml and relative paths
>Date: Fri, 01 Mar 2002 14:55:28 -0800
>
>Currently the primary jboss-service.xml does exactly this, so Dave might
>not be including <classpath/> in other files, since this one already
>does it.
>
>I hope that eventually we use explicit jar refs, so we don't bloat the
>heap with unused libs.
>
>--jason
>
>
>Hiram Chirino wrote:
>
>>How does the server know where the jars are if the <classpath../> is
>>not there. Does it just load up all the lib/* jars??
>>
>>Regards,
>>Hiram
>>
>>
>>>From: David Jencks <[EMAIL PROTECTED]>
>>>To: Hiram Chirino <[EMAIL PROTECTED]>
>>>CC: [EMAIL PROTECTED], [EMAIL PROTECTED]
>>>Subject: Re: [JBoss-dev] Property access in *service.xml and relative
>>>paths
>>>Date: Fri, 1 Mar 2002 10:39:55 -0500
>>>
>>>Are you sure you need the <classpath .../> element at all? Unless you
>>>are
>>>loading from an http: url you should be fine by removing this element
>>>entirely. I guess I better go through everything and do this... I
>>>already
>>>got a lot of messages from them being in the db config examples.
>>>
>>>david jencks
>>>
>>>On 2002.03.01 10:23:00 -0500 Hiram Chirino wrote:
>>> > it would be kinda nice if the url's in the service.xml file were
>>>relative
>>> > to
>>> > the service.xml file. Do I make sense?? so if the service.xml
>>>files is:
>>> > /jboss/server/default/deploy/jbossmq-service.xml
>>> > To load all the jboss/lib jars :
>>> > <classpath codebase="../../../../lib" archives="*"/>
>>> > To load all the jars in the server's lib dirctory:
>>> > /jboss/server/default/lib
>>> > <classpath codebase="../lib" archives="*"/>
>>> >
>>> > Regards,
>>> > Hiram
>>> >
>>> > >From: Jason Dillon <[EMAIL PROTECTED]>
>>> > >To: David Jencks <[EMAIL PROTECTED]>
>>> > >CC: [EMAIL PROTECTED]
>>> > >Subject: Re: [JBoss-dev] Property access in *service.xml and relative
>>> > paths
>>> > >Date: Thu, 28 Feb 2002 19:51:32 -0800
>>> > >
>>> > >I sent mail on this before I commited the layout change. It has todo
>>> > >with which directory/url do we use to qualify relative paths. It
>>>also
>>> > >has todo with allow a global and per-server config library directory.
>>> > >
>>> > >--jason
>>> > >
>>> > >
>>> > >David Jencks wrote:
>>> > >
>>> > >>On 2002.02.28 22:35:27 -0500 Jason Dillon wrote:
>>> > >>
>>> > >>>I was thinking that a solution to the problem that MD now has
>>>due to
>>> > the
>>> > >>>layout changes that I made WRT relatives paths could be solved by
>>> > >>>forcing users to be explicit about which path they which to use
>>>(ie.
>>> > not
>>> > >>>allowing relative paths).
>>> > >>>
>>> > >>
>>> > >>What are these problems? I haven't noticed any. Using <classpath
>>>.../>
>>> >
>>> > >>can
>>> > >>cause problems, but it is almost always better to just leave the tag
>>> > out.
>>> > >>
>>> > >>david jencks
>>> > >>
>>> > >>
>>> > >>>To make this work we need to expose some system property access
>>>inside
>>> > >>>of the *service.xml files... probably as an attribute value
>>>subst and
>>> > an
>>> > >>>element... for example:
>>> > >>>
>>> > >>><!-- this is everything under jboss-*/lib -->
>>> > >>><classpath codebase="${jboss.home.dir}/lib" archives="*"/>
>>> > >>>
>>> > >>><!-- This is everything under jboss-*/server/<config>/lib -->
>>> > >>><classpath codebase="${jboss.server.home.dir}/lib" archives="*"/>
>>> > >>>
>>> > >>><!-- This would set the MyConfigName attribute to the servers
>>>config
>>> > >>>name.
>>> > >>><attribute name="MyConfigName">
>>> > >>> <property name="jboss.server.name"/>
>>> > >>></attribute>
>>> > >>>
>>> > >>>Could also expose a element ot set a property:
>>> > >>>
>>> > >>><!-- Set a property myprop to some value -->
>>> > >>><setproperty name="myprop" value="somevalue"/>
>>> > >>>
>>> > >>>Which could then be used in config elements later in the file...
>>> > >>>
>>> > >>>And to finally solve the two lib problem... just more than one
>>> > classpath
>>> > >>>(if that isn't the case already):
>>> > >>>
>>> > >>><classpath codebase="${jboss.server.home.dir}/lib" archives="*"/>
>>> > >>><classpath codebase="${jboss.home.dir}/lib" archives="*"/>
>>> > >>>
>>> > >>>This would prefer libs from inside jboss.server.home.dir/lib before
>>> > >>>jboss.home.dir/lib
>>> > >>>
>>> > >>>--jason
>>> > >>>
>>> > >>>
>>> > >>>_______________________________________________
>>> > >>>Jboss-development mailing list
>>> > >>>[EMAIL PROTECTED]
>>> > >>>https://lists.sourceforge.net/lists/listinfo/jboss-development
>>> > >>>
>>> > >>>
>>> > >
>>> > >
>>> > >
>>> > >_______________________________________________
>>> > >Jboss-development mailing list
>>> > >[EMAIL PROTECTED]
>>> > >https://lists.sourceforge.net/lists/listinfo/jboss-development
>>> >
>>> >
>>> >
>>> >
>>> > _________________________________________________________________
>>> > Get your FREE download of MSN Explorer at
>>> > http://explorer.msn.com/intl.asp.;
>>> >
>>> >
>>> >
>>
>>
>>
>>
>>
>>_________________________________________________________________
>>Send and receive Hotmail on your mobile device: http://mobile.msn.com
>
>
>
_________________________________________________________________
MSN Photos is the easiest way to share and print your photos:
http://photos.msn.com/support/worldwide.aspx
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development