[ http://jira.jboss.com/jira/browse/JBAS-29?page=history ]
Phil Cornelius updated JBAS-29:
-------------------------------
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?
was:
<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?
Version: JBossAS-4.0.2RC1
> Added URL Service MBean
> -----------------------
>
> Key: JBAS-29
> URL: http://jira.jboss.com/jira/browse/JBAS-29
> Project: JBoss Application Server
> Type: Patch
> Versions: JBossAS-4.0.1 Final, JBossAS-4.0.2RC1
> Environment: patches against src of JBossAS-4.0.1RC1, JBossAS-4.0.1RC2
> Reporter: Phil Cornelius
> Assignee: Scott M Stark
> Priority: Minor
>
> Original Estimate: 2 hours
> Remaining: 2 hours
>
> <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?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
