The problem is we update the schema every time a field is added to a Java bean. So mostly likely we would have to version the namespace for every release.
BTW the namespace != to the xsd that defines it. We currently do version the xsd's you can see them listed at: http://activemq.apache.org/schema/core The user would just need to update his document's xsi:schemaLocation configuration to validate against the correct XSD. On Fri, Apr 18, 2008 at 12:47 PM, Alan D. Cabrera <[EMAIL PROTECTED]> wrote: > > On Apr 18, 2008, at 9:35 AM, Hiram Chirino wrote: > > > > On Fri, Apr 18, 2008 at 12:19 PM, Alan D. Cabrera <[EMAIL PROTECTED]> > wrote: > > > > > I agree about version numbers in the URI but faintly hold that opinion. > > > > > > > > > > Problem is do we update the URIs everytime we release? Sounds like it > > would break folks. What would the benefits be? > > > > Only if the schema changed. > > Someone might be working w/ an older schema for production work and a newer > schema for a new thing that's being developed. Having the same namespaces > would be a problem in their IDE. > > > Regards, > Alan > > > -- Regards, Hiram Blog: http://hiramchirino.com Open Source SOA http://open.iona.com
