[ http://jira.jboss.com/jira/browse/JBAS-29?page=comments#action_12316027 ] Phil Cornelius commented on JBAS-29: ------------------------------------
I have been thinking hard about this.. I think a generic javabean binding service is unnecessary. It is not in the J2EE spec and therefore it is unlikely that anyone would use it as part of their application. Specifically the URL Resource is in the spec and is therefore _required_. Anyone writing a new J2EE app or porting their app to JBoss may use any of the J2EE resources, and although including a URL in the deployment descriptors is acceptable for bespoke apps, it is not for ISV apps. Our app goes to lots of customers on potentially different app servers. Although I agree that 'more general' is good programming practice, I also feel that writing unnecessary code is bad practice. Please reconsider including this patch as is.. and I will support it and build upon it. ----- J2EE.5.4.1.3 <snip> The Application Component Provider must use the java.net.URL resource manager connection factory type for obtaining URL connections. It is recommended that the Application Component Provider name JDBCAPI datasources in the java:comp/env/jdbc subcontext, all JMSconnection factories in the java:comp/env/jms subcontext, all JavaMail API connection factories in the java:comp/env/mail subcontext, and all URL connection factories in the java:comp/env/url subcontext. </snip> > 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 JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
