I'd say the best answer is "hasn't been decided yet"! Your thoughts are of course appreciated.
Note however that JAX-RPC support will not be in the core engine! I personally don't care for the pluggable binding framework to be core either (as it can be done by a provider) but I haven't started that battle yet ;-). Sanjiva. ----- Original Message ----- From: "Mark D. Hansen" <[EMAIL PROTECTED]> To: <[email protected]>; "Srinath Perera" <[EMAIL PROTECTED]> Sent: Friday, March 18, 2005 9:00 AM Subject: RE: [Axis2] bringing over org.apache.axis.encoding package to Axis2 > Yes, I am refering to the Axis 1.x de[serialization] framework. Pluggable bind tools are the right way to go. But, you will need some default binding system if you are going to provide JAX-RPC support. I was wondering if the plan is to simply port the Axis 1.x org.apache.axis.encoding.* classes over to Axis2 for that purpose. > > Or maybe it hasn't been decided yet? > > -- Mark > > > -----Original Message----- > > From: Srinath Perera [mailto:[EMAIL PROTECTED] > > Sent: Thursday, March 17, 2005 8:32 PM > > To: [email protected] > > Subject: Re: [Axis2] bringing over org.apache.axis.encoding package to > > Axis2 > > > > > > u refers to the Axis 1.x code, right? > > > > Our approch is the data binding tools are pluggable. So that code may > > come it to Axis2. But the answer is not final yet as the encoding > > discussions has not conclusive yet. > > > > I belive we can write pull to SAX converter with out much hassle, so > > the SAX things are supported yet. > > Thanks > > Srinath > > > > > > On Thu, 17 Mar 2005 14:02:57 -0500, Mark D. Hansen > > <[EMAIL PROTECTED]> wrote: > > > Are there plans to bring the org.apache.axis.encoding stuff > > over to Axis2? Will all the SAX code become StAX code? > > > > > > >
