> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
>
> Wayne Stidolph wrote:
> >
> > This puts the JOnAS code in a strange non-spec place: partly EJB 1.1,
> > partly EJB 2.0. The Enhydra use of JOnAS is to be EJB 1.1 compliant;
> > I don't really worry very much about completely add-on behavior (like
> > the message driven beans) but changes that impact existing beans (such
> > as Walt's) could be a problem. So, would it be hard for you to put in
> > a build-time switch that restores EJB 1.1 strict behavior?
> >
> > Wayne Stidolph
> >
> As I say to Walt, I have not said that we are compliant to spec 2.0,
> I have only said it was worth fixing the bug on Create exceptions
> the price to pay is only to to modify few throws clauses in a way that
> will be conform to the next spec
> the 1.1 spec was saying the method may throw...
> 2.2 says the method must throws...
> Do you really think it's a problem? I am not really sure
> we have to complicate code to introduce a mecanism to keep
> compatibility on this prceise point.
Yes, I see it as a problem: a real user (Walt) has already encountered a
need to change source in an existing EJB 1.1 bean to run on the server. And
so it will apply to other existing EJBs where the bean provider decided to
not throw something that they "may" throw... we would be incompatible.
This is probably not a big problem when the user has the bean source
(although Walt claims adding the throws clause resulted in another
error??) - but quite possibly a problem when someone is hoping to build an
app using third-party beans; those third-party bean vendors will not want to
"port" their beans, they will expect them to "just work."
Wayne Stidolph
----
To unsubscribe, send email to [EMAIL PROTECTED] and
include in the body of the message "unsubscribe jonas-users".
For general help, send email to [EMAIL PROTECTED] and
include in the body of the message "help".
