You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by David Jencks <da...@yahoo.com> on 2009/03/26 13:28:09 UTC
should we update schema namespace for backwards compatible changes?
Following a user request here at apachecon eu I finally implemented
the ability to override env-entry elements in geronimo plans
(GERONIMO-3954) (also, I'm not sure if this works for ejbs -- is
openejb using our env-entry builder?)
This requires a backwards compatible change to the geronimo naming
schema.
In the past we've tended to update the schema namespace by increasing
the version with every change although this has resulted in a lot of
nuisance and does not appear to be a recommended practice.
So far I haven't updated the namespace. I'm very tempted to suggest
that we change our policy a bit and not change the namespace so often.
Thoughts?
thanks
david jencks
Re: should we update schema namespace for backwards compatible changes?
Posted by David Blevins <da...@visi.com>.
On Mar 26, 2009, at 5:28 AM, David Jencks wrote:
> Following a user request here at apachecon eu I finally implemented
> the ability to override env-entry elements in geronimo plans
> (GERONIMO-3954) (also, I'm not sure if this works for ejbs -- is
> openejb using our env-entry builder?)
I don't think so, but there likely is a place in the G ejb deployer
where we can grab the env entries and update them with the overrided
values. I seem to recall we're doing some manipulation of the jaxb
ejb-jar.xml tree already.
-David
Re: should we update schema namespace for backwards compatible
changes?
Posted by Juergen Weber <we...@gmail.com>.
djencks wrote:
>
> Following a user request here at apachecon eu I finally implemented
> the ability to override env-entry elements in geronimo plans
> (GERONIMO-3954) (also, I'm not sure if this works for ejbs -- is
> openejb using our env-entry builder?)
>
Great, but please see also
http://www.nabble.com/Re%3A-Google-Summer-of-Code-p22599207.html
(every single web.xml or ejb-jar.xml entry should be overridable).
Also, concerning EJB3, can you override an injected property with a geronimo
plan, even if the injected property is not overridden by an entry in
ejb-jar.xml ?
geronimo-plan -> ejb-jar.xml -> injected property
Thanks,
Juergen
--
View this message in context: http://www.nabble.com/should-we-update-schema-namespace-for-backwards-compatible-changes--tp22721031s134p22724942.html
Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.
Re: should we update schema namespace for backwards compatible
changes?
Posted by Jarek Gawor <jg...@gmail.com>.
We've had similar conversations before and I think we pretty much
decided that backwards compatible changes without updating the
namespace were ok.
(Although, from my understanding the recommended practice is to change
the namespace each time a change is made)
Jarek
On Thu, Mar 26, 2009 at 8:28 AM, David Jencks <da...@yahoo.com> wrote:
> Following a user request here at apachecon eu I finally implemented the
> ability to override env-entry elements in geronimo plans (GERONIMO-3954)
> (also, I'm not sure if this works for ejbs -- is openejb using our env-entry
> builder?)
>
> This requires a backwards compatible change to the geronimo naming schema.
>
> In the past we've tended to update the schema namespace by increasing the
> version with every change although this has resulted in a lot of nuisance
> and does not appear to be a recommended practice.
>
> So far I haven't updated the namespace. I'm very tempted to suggest that we
> change our policy a bit and not change the namespace so often.
>
> Thoughts?
>
> thanks
> david jencks
>