[JBoss-dev] [JBoss JIRA] Commented: (JBAS-29) Added URL Service MBean

[Phil C. (JIRA) <jir...@jb...>]

     [ http://jira.jboss.com/jira/browse/JBAS-29?page=comments#action_12315864 ]
     
Phil Cornelius commented on JBAS-29:
------------------------------------

Perhaps so.. but then why not apply the same logic to mail, datasource and jms resources.

I should be able to configure my URL resources outside of my EAR as I can with other app servers.. I'll include a screenshot of websphere.

Can you include this patch now and worry about the more general case later. I have followed the same pattern as for the mail resource.

At the mo I am having to distribute a patched jboss to our customers which is untidy.

> Added URL Service MBean
> -----------------------
>
>          Key: JBAS-29
>          URL: http://jira.jboss.com/jira/browse/JBAS-29
>      Project: JBoss Application Server
>         Type: Patch
>   Components: Naming
>     Versions: JBossAS-4.0.1 Final, JBossAS-4.0.2 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

>
> 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