Axis2 and WSDL20

2006-12-11 Thread jim ma

Hi all ,

Does Aixs2 plan to support WSDL20 ? Currently is there any experimental
stuff related to WSDL20?

Thanks

Jim


Re: Why it only read 28 bytes

2006-12-08 Thread jim ma

Hi all ,

I think this is a bug maybe introduced by jakarta-httpcore-4.0-alpha2.  When
enable the chunk mode for StringEntity , client will read 28 bytes each time
. Client will read many times when a large payload response returned . This
definitely affects Aixs2's performance.

Axis2 need to set chunk buffersize for HttpCore before invoking
StringEntity.setChunk(true) ?

Regards

Jim

On 12/5/06, jim ma <[EMAIL PROTECTED]> wrote:


Hi all ,

I downloaded the aixs2 1.1 std kit and tried a simple sample contains one
operation: echoString() . After I deployed the service in repository and
launch the server with axis2server.I wrote the following code to send the
payload to aixs2server and soap response :

httpCon.getOutputStream().write(payload);
httpCon.getOutputStream().flush();
byte[] buffer = new byte[1024];
count = httpCon.getInputStream().read(buffer);
while (count > 0) {
   System.out.println ("---readed" + count);
   count = httpCon.getInputStream().read(buffer);
}

I found the thing confused me : each time it only can read 28 bytes from
inputStream . Large size respsone will be readed many times.  But I deployed
it into tomcat , It will read 1024 bytes each time.

Which line code in Artix2 1.1 cause this ?

Thanks

Jim







Why it only read 28 bytes

2006-12-05 Thread jim ma

Hi all ,

I downloaded the aixs2 1.1 std kit and tried a simple sample contains one
operation: echoString() . After I deployed the service in repository and
launch the server with axis2server.I wrote the following code to send the
payload to aixs2server and soap response :

httpCon.getOutputStream().write(payload);
httpCon.getOutputStream().flush();
byte[] buffer = new byte[1024];
count = httpCon.getInputStream().read(buffer);
while (count > 0) {
  System.out.println("---readed" + count);
  count = httpCon.getInputStream().read(buffer);
}

I found the thing confused me : each time it only can read 28 bytes from
inputStream . Large size respsone will be readed many times.  But I deployed
it into tomcat , It will read 1024 bytes each time.

Which line code in Artix2 1.1 cause this ?

Thanks

Jim


Re: How to configure axis2-1.1 to support JAXB-RI

2006-11-30 Thread jim ma

Great thanks, Brennan.

This feature will be supported in the next release ?

Jim

On 11/30/06, Brennan Spies <[EMAIL PROTECTED]> wrote:


 Jim,



Your best bet is to generate databinding using some other supported tech (
i.e., XmlBeans). Then alter the generated classes (the MessageReceiver and
Skeleton) so that you use JAXB-RI. This generally involves going to and from
Axiom (OMElement) as the information is passed from and back to the SOAP
body—this shouldn't involve much effort since the StAX api is supported by
JAXB.


 --

*From:* jim ma [mailto:[EMAIL PROTECTED]
*Sent:* Tuesday, November 28, 2006 10:00 PM
*To:* axis-user@ws.apache.org
*Subject:* How to configure axis2-1.1 to support JAXB-RI



Hi all ,

I noticed aixs2 1.1 can support JAXB-RI databinding experimentally. I have
copied all the jar files related to jaxb ri under lib directory(in axis2-std
kit). But wsdl2java complains "JAX-B RI binding extension not in
classpath".  Is there something need to configure or codegen tool can not
generate jaxb ri databinding code  ?

I also want to know runtime can support jaxb ri databinding.

Thanks

Jim



How to configure axis2-1.1 to support JAXB-RI

2006-11-28 Thread jim ma

Hi all ,

I noticed aixs2 1.1 can support JAXB-RI databinding experimentally. I have
copied all the jar files related to jaxb ri under lib directory(in axis2-std
kit). But wsdl2java complains "JAX-B RI binding extension not in
classpath".  Is there something need to configure or codegen tool can not
generate jaxb ri databinding code  ?

I also want to know runtime can support jaxb ri databinding.

Thanks

Jim