[ http://jira.jboss.com/jira/browse/JBAS-29?page=comments#action_12315869 ] Phil Cornelius commented on JBAS-29: ------------------------------------
your first point.. My patch only supports trivial URLs but properly addresses the fact that the URL Resource, as one of the 5 J2EE resources, is missing from JBAS. This patch will allow users to decouple their external file resources from their EAR in a portable and J2EE standard way.. At present the only way to do this in JBoss is to embed the URL into the jboss dd inside the EAR.. which is not consistent with 'service file method' of the other 4 resources. I shouldn't have to have a different EAR file for each different customer deployment..that is the whole point. And I strongly believe this is the right way to do it. your second point I am not saying that this shouldn't be generalized.. but in the meantime this patch addresses an inconsistency in jboss. It is a first step.. and a first code contribution from me, I can't see the harm in including it. > 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 > Attachments: URLResource_jboss-4.0.1RC2.patch, was_urlresource.png > > 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 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
