> Then how do you reference these files? You mention referencing the top of
If there was some sort of ServiceContext, passed into the service bean, on
init, then it could hold this information.
> the file hierarchy but how do you know where to find it? The only simple
> solution that I can think of is you doing a getResource() on your
> classloader that would point to the top of the hierarchy and you can work
Some legecy services will want files. Some services will only make sence
when working off of files. I can understand that the boot/loading system
should not be tied to files, but there is no reason why we should force
service writters to stop using files.
Right?
> from there. I would strongly recommend not making that "anchor" file a
> configuration file (something widespread in jboss) since the configurations
Widespread through more than JBoss. Plugin vendors will probably want
access to the filesystem for whatever.
> The last point is where to get the name for the sar directory (I don't know
> that you are going to deploy "jetty"). This probably means that we will
Why wouldn't you deploy jetty? Do you mean that it could be in the
main jboss-service.xml, lets just make it a deployable. Lets make
everything deployable except for the core system services.
> need to introduce a sar.xml that is a collection of the jcml information and
> some self descripting stuff such as the name of the "sar" (in our case
> "jetty"). hmmmm
remeber long ago when I was talking about using a FileSystem abstraction...
and remeber the bit about defining local resources required by a service in
the service deployment descriptor, these go hand in hand. Top it off with
the ServiceContext, and you have all the means to support this type of
per-service configuration.
> Maybe I should read that service proposal thing. Can anyone provide a
> pointer.
Which service proposal thingy do you mean?
--jason
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
