Yes, as I just said in a separate email I'll make sure a stable JiBX 1.1
release is out by the end of the month. I assume it's okay if this is a
beta release, just so long as it's not a snapshot, right? I'd like to
make further changes before the official 1.1 production release of JiBX,
but if using a beta is a problem I can make 1.1 official and move the
remaining changes into 1.2.
I had the new code working, but ran into a problem with Axiom changes.
I'm waiting to get those resolved so I can add test cases for the JiBX
code in Axis2. The nice part of this is that JAXB 2.0 support should be
easy to add in once that's officially released, using the same Axiom and
code generation hooks as I've used for JiBX.
- Dennis
Sanjiva Weerawarana wrote:
+1, but since Dennis I believe has control over JibX maybe he can get it
done and ready. He did say he'll work hard to get it ready for 1.0 ..
Dennis?
Sanjiva.
On Fri, 2006-04-21 at 13:45 -0400, Davanum Srinivas wrote:
Then we ship w/o the jibx extension....
-- dims
On 4/21/06, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:
Hi all;
In Axis2 there are few SNAPSHOT dependencies and I think its is not good
idea to do the 1.0 release with SNAPSHOT. And we will be able to get the
stable release of the following before 1.0
- AXIOM
- XMLSchema
- WSS4J
- TCPMonitor
But the problem is the possibility of getting stable release of "jibx"
dependencies. What should be our plan if we can not get stable release
of jibx before 1st of May.
I dont like to wait till last moment to take decision so your comments
and suggestions are very valuable at this moment.
--
Thanks,
Deepal
................................................................
~Future is Open~
--
Davanum Srinivas : http://wso2.com/blogs/
