Hi all,
here is set of JIRA with some comments.
· OPENEJB-965: webfault not correctly handled à patch is available.
I guess it’s still usable for trunk.
· OPENEJB-977: upgrade to latest CXF release à we worked with
Jean-Sébastien to do such upgrade. It solves some other issues (965 and
1020) but it has some drawbacks (upgrade JaxB to 2.1). Do you want me to
update this patch again so we can apply it on trunk ?
· OPENEJB-1011: corrupted initial context à should be closed.
Actually it’s not an issue but a misunderstanding (sorry for that).
· OPENEJB-1020: JAX-WS inheritance à it’s a JAX-WS 2.1 feature. So
we need to upgrade CXF and JaxB (OPENEJB-977)
· OPENEJB-1026: must be validated à easy to fix if needed
· OPENEJB-1040: javaee-api à a discussion is in progress in d...@list
· OPENEJB-1046: currently we can change url template
(openejb.wsAddress.format defaults to /{ejbDeploymentId}) and add the
moduleId if needed. So I need to clarify the request with Jean-Sebastien.
Moreover, I need to check the spec to see how EJB web services must be
treated when deployed in a web module (shall we publish ws in the root
context or in the context container?)
· OPENEJB-1048 à I fixed it. If you agree we can close.
· OPENEJB-1049 : stateful cache management à we already discussed
that point on IRC. Behaviour is not relevant with OpenEJB 3.0. From the
picture p74 of the spec, you concluded we are in the “method ready in TX”
and we are allowing non-tx or different tx method invocation without
throwing an explicit error à did you fix it ?
· OPENEJB-1053: manage old servlet deployment descriptors à I’ve
just enhance the existing JUnit test to be sure it fails ;-) (not committed)
· OPENEJB-1061: WSS4J tries to load SUN cacerts à a property can
prevent such a behaviour. I fixed it and Karan has validated under OpenJDK.
à can be closed
· OPENEJB-1063: Main-Class containing fails à I can submit my patch
to warn and replace “/” by “.” Then, we can close this issue as there is
still the OPENEJB-1054 opened.
Jean-Louis
David Blevins wrote:
>
> We've been working towards 3.1.2 for a bit now. Would be great to get
> it buttoned up and a release vote going in the next week or so.
> Geronimo will need it for their 2.2 release and there are a number of
> people on the users list who would probably be very happy as well.
>
> If you have some bits you've been working on, definitely post and we
> can see if we can get it in before release time. I got a few of my
> own in over the last two days, will sweep through Jira and post my own
> list.
>
>
> -David
>
>
>
--
View this message in context:
http://www.nabble.com/3.1.2-status-tp25389152p25389864.html
Sent from the OpenEJB Dev mailing list archive at Nabble.com.
