Re: [jboss-dev] Remoting 3.0

Maybe we should externalize it into a jbossws-addressing.jar. Currently ESB and JBossWS are using different implementations of the same specs. With remoting it would be already three parties. IMHO it should become a subproject of either JBossWS or ESB and publish jars to the repository for others to refer to. /Heiko On Thu, 2007-06-21 at 08:20 +0100, Mark Little wrote: > Sure. In the 4.2 version of ESB we're using a version that is > based on > the original WS-Addressing implementation we developed in Arjuna for > the Web Services transactions product back in 2004 and used for > interoperability testing with Microsoft, IBM etc. It's based on the > 2004 version of WS-A > (http://www.ibm.com/developerworks/library/specification/ws-add/) > > > We have a new version for the next major release of ESB based on the > 2006 release of WS-A (tested here > http://www.w3.org/2002/ws/addr/testsuite/), but the concepts are > pretty much the same (basically you lose ReferenceProperties). > > > This class is the one people are expected to develop endpoint > references (EPRs) against: > > > http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/core/ > rosetta/src/org/jboss/soa/esb/addressing/EPR.java > > > But this one is the one that does the real work: > > http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/core/ > rosetta/src/org/jboss/soa/esb/addressing/PortReference.java > > > BTW, URI would be fine too. EPRs are a superset. > > > Mark. > > > > On 20 Jun 2007, at 19:08, Scott M Stark wrote: > >> We use both URLs and URIs in the vfs, but still rely on the URL >> handler >> mechanism for content. There needs to be some mechanism to obtain >> content streams and properties/attributes for the endpoint. We >> should >> have a common lib for either URIs or EPRs. Give a pointer to the EPR >> code in the ESB codebase. >> >> >> Mark Little wrote: >>> How about moving away from URLs to URIs or EPRs (WS-Addressing >>> Endpoint >>> References)? We use EPRs, which are basically URIs with some >>> additional >>> meta-data (which can be null if you want). URLs are ok and my >>> JBossESB >>> 5.0 prototype runs on current Remoting and does a mapping from EPR >>> down >>> to URL when it needs to, but they are pretty limiting. Plus URL >>> doesn't >>> support SFTP or FTPS. >>> >>> >>> Mark. >>> >>> >>> >>> >>> On 19 Jun 2007, at 14:00, Bill Burke wrote: >>> >>> >>>> The URL for JMS would look real ugly too. New URL protocols are >>>> dangerous too as you may not be able to override the JDK's URL >>>> Handler >>>> (because it can only be set once!). I ran into this problem >>>> with >>>> Tomcat 5. >>>> >>>> >> >> >> _______________________________________________ >> jboss-development mailing list >> jboss-development(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jboss-development >> >> >> >> > > ---- > > > Mark Little > mlittle(a)redhat.com > > > JBoss, a Division of Red Hat > Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod > Street, Windsor, Berkshire, > SI4 1TE, United Kingdom. > Registered in UK and Wales under Company Registration No. 3798903 > Directors: Michael Cunningham (USA), Charlie Peters (USA) and David > Owens (Ireland) > > > > > > > > > _______________________________________________ > jboss-development mailing list > jboss-development(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-development _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development