Details
-
Patch
-
Resolution: Done
-
Major
-
JBossAS-4.0.1 Final, JBossAS-4.0.2RC1, JBossAS-4.0.2 Final
-
None
Description
<duplicated from sourceforge/>
Further to RFE991650
http://sourceforge.net/tracker/index.php?func=detail&aid=991650&group_id=22866&atid=376688
Attached is a patch that adds the URLResource Service
needed to actually bind the URLResources into the jboss
jndi directory.
Until now the only way of adding a resource of type
java.net.URL was to explicity write it in to the jboss
deployment descriptors.
Scott wrote the jboss server code to bind the URL
resource references to a jboss jndi name.. (as in the
RFE above) but there wasn't an easy way to bind the
actual URLs to those jndi names.
Would appreciate it if this made it to RC2
The patch is against the jboss-4.0.1RC1-src
Why do this?
If you are OEMing your product on jboss then would be
nice to keep system paths and external resources loosly
coupled from the EAR file.. best way is to use a J2EE
URL resource.. if these resources are bound in a
service file (like all other resources) then they are
easy to change with an installer say, or even at runtime...
Tasks associated with this patch are welcome.
Yours
Phil
PS. I noticed the JSR-77 URLResource class in the
management module and wasn't sure how this ties in?
Attachments
Issue Links
- relates to
-
JBAS-1826 Need support for GlobalNamingResources in server.xml
- Closed