Ok, I will drop this for now... well after I get a last few words in that is.
This is small beans which adds value to the mbean configuration language. You will find that similar features are found in other systems when dealing with configuration fluff. Jetty and Log4j both have this capability. In fact this was the only way to get them to use the new layout. I expect that other non-jboss components will need similar config when using relative paths to local files, or they path will be relative to where the JVM started. It is a really bad idea to have the behavior of the server change based on what directory the user was in when they started it up. It is also a poor choice to force users into a particular directory (aka bin/). If you have been reading the changes recently, I removed the need for starting in bin/ by fixing the bits which required that be the case. Currently, unless you are running 95 or 98 (which do not support special % fluff which nt does) you do not need to be in the bin/ dir. This is a compatiblity feature, which is simple to implement which will make it much easier to integrate components which need configuration based on a relative path to either the jboss.home.dir or jboss.server.home.dir locations. I hope you will reconsider. I think this is very valuable from a configuration, integration and admisistration standpoint and simple to implement. --jason marc fleury wrote: >drop it for now, > >no case, > >marcf > >|-----Original Message----- >|From: [EMAIL PROTECTED] >|[mailto:[EMAIL PROTECTED]]On Behalf Of Jason >|Dillon >|Sent: Thursday, February 28, 2002 7:52 PM >|To: David Jencks >|Cc: [EMAIL PROTECTED] >|Subject: Re: [JBoss-dev] Property access in *service.xml and relative >|paths >| >| >|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 > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
