Unsubscribe

[Sudhir Mongia]

Complex type extension support in Axis2 ADB

[Sudhir Mongia]

Hi Amila,
This is with reference to your article http://wso2.org/library/2670, it says
axis2 adb supports complex type extensions. It doesn;t seems to be working
in my case when I am trying to generate stub. Is there any trick??

I remember I asked you this question earlier as well, but some how didn't
get any reply. This  time I request you to please do answer.

I am using Axis2 1.4.1. Let me  know, If you need more information from my
side.

thanks in advance.

Sudhir

Re: MTOM - sending byte array?

[Sudhir Mongia]

yes, that should be enough.

Sudhir

On Fri, May 15, 2009 at 2:12 PM, Seem  wrote:

>
> Will a byte array be system independent so that every client can recreate
> the
> xml data?
>
> a definition in the wsdl like this would be enough?
> 
>
> or do I need an expectedContentType?
>
> Do I need some more preparations on the service side or can I send the byte
> array just like it is to the client?
>
> Thanks,
> Seem
>
>
> Sudhir Mongia wrote:
> >
> > Hi Seems,
> > If you are expecting a big xml file, it makes sense to define it a byte
> > array and send it as MTOM attachment.
> >
> > Sudhir
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/MTOM---sending-byte-array--tp23549821p23555722.html
> Sent from the Axis - User mailing list archive at Nabble.com.
>
>

Re: MTOM - sending byte array?

[Sudhir Mongia]

Hi Seems,
If you are expecting a big xml file, it makes sense to define it a byte
array and send it as MTOM attachment.

Sudhir

On Fri, May 15, 2009 at 5:30 AM, Seem  wrote:

>
> Hi Andreas,
>
> it is a calculated result i will get from the jena framework for handling
> RDF models inside my service.
>
> So do you think it would be the better way to build an xml file out of the
> byte array and send it afterwards to the client?
>
> But for sending this xml, i also have to use MTOM, right? Or would you
> insert it as a string parameter in the soap body?
>
> it can get a real big xml file
>
> Thanks,
> Seem
>
>
> Andreas Veithen-2 wrote:
> >
> > Seem,
> >
> > If it is XML, why do you want to send it as a byte array and not
> > insert it as XML into the SOAP message?
> >
> > Andreas
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/MTOM---sending-byte-array--tp23549821p23551226.html
> Sent from the Axis - User mailing list archive at Nabble.com.
>
>

Re: Handling Large data in a method call

[Sudhir Mongia]

Hi Amila,
I am waiting to hear from you. We are bound to use xmlbeans and its eating
memory like anything. I thought of seeing another binding approach, tried
with Jibx but that too seems very complex.

Any help.pointer appreciated.

Thanks,
Sudhir

On Fri, May 8, 2009 at 10:14 AM, Sudhir Mongia wrote:

> Hi Amila,
> We are using Axis21.4.1 and it doesn't seems to support Complex type and
> extensions.  I have not tried on Jibx yet.
>
> Sudhir
>
>
> On Thu, May 7, 2009 at 1:07 PM, Amila Suriarachchi <
> amilasuriarach...@gmail.com> wrote:
>
>>
>>
>> On Wed, May 6, 2009 at 10:12 AM, Sudhir Mongia 
>> wrote:
>>
>>> Hi Dennis,
>>> We are not using WS-Security. Still its paining us.
>>>
>>> The problem we are facing is memory consumption while  serialization.
>>>
>>> We are using xmlbeans databinding, we couldn't go for ADB as it doesn't
>>> supports Complex type extension and restrictions and we have not evaluated
>>> other binding options as of now.
>>>
>>
>> What is the Axis2 version you use? ADB supports Complex type extension and
>> restrictions.  But again there is a possibility it won't support for all
>> variations.
>>
>> Generally Xmlbeans slower than other data bindings. so you can try jibx
>> and jaxbri as well.
>>
>> thanks,
>> Amila.
>>
>>
>>> Thanks,
>>> Sudhir
>>>
>>>
>>> On Wed, May 6, 2009 at 3:01 AM, Dennis Sosnoski wrote:
>>>
>>>> Hi Sudhir,
>>>>
>>>> Are you using WS-Security for the service? WS-Security builds an
>>>> in-memory model of the XML if you're using signatures (and perhaps at other
>>>> times - I haven't checked, but there appeared to be some issues in this
>>>> area).
>>>>
>>>> If you're not using WS-Security this type of data should not be causing
>>>> problems. What data binding approach are you using? (ADB, XMLBeans, JiBX,
>>>> JAXB?)
>>>>
>>>>  - Dennis
>>>>
>>>> --
>>>> Dennis M. Sosnoski
>>>> SOA and Web Services in Java
>>>> Axis2 Training and Consulting
>>>> http://www.sosnoski.com - http://www.sosnoski.co.nz
>>>> Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117
>>>>
>>>>
>>>> Sudhir Mongia wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> Has anyone got any experience in this type of problem ? One possible
>>>>> solution we used temporarily is, pass data fragment in in a call and do
>>>>> multiple calls to send the complete data.But we are reluctant to go with
>>>>> this approach in production.
>>>>>
>>>>> Any help/pointer ?
>>>>>
>>>>> Thanks,
>>>>> Sudhir
>>>>>
>>>>> On Mon, May 4, 2009 at 2:23 PM, Sudhir Mongia 
>>>>> >>>> sudhir.mon...@gmail.com>> wrote:
>>>>>
>>>>>Hi,
>>>>>
>>>>>We have a web method exposed by .net app and we using client stubs
>>>>>generated through Axis2. This method accepts an array of objects.
>>>>>The object is very heavy object containing 25+ members variables
>>>>>of double and string type.
>>>>>The calls to this method fails sometimes due to memory when we are
>>>>>trying to send large number of objects e.g. 10-20.
>>>>>
>>>>>Any suggestions/idea , how can we compress the size of data to fix
>>>>>this problem? We have control up to some extent on server side as
>>>>>well.
>>>>>
>>>>>Thanks,
>>>>>Sudhir
>>>>>
>>>>>
>>>>>
>>>
>>
>>
>> --
>> Amila Suriarachchi
>> WSO2 Inc.
>> blog: http://amilachinthaka.blogspot.com/
>>
>
>

Re: Handling Large data in a method call

[Sudhir Mongia]

Hi Amila,
We are using Axis21.4.1 and it doesn't seems to support Complex type and
extensions.  I have not tried on Jibx yet.

Sudhir


On Thu, May 7, 2009 at 1:07 PM, Amila Suriarachchi <
amilasuriarach...@gmail.com> wrote:

>
>
> On Wed, May 6, 2009 at 10:12 AM, Sudhir Mongia wrote:
>
>> Hi Dennis,
>> We are not using WS-Security. Still its paining us.
>>
>> The problem we are facing is memory consumption while  serialization.
>>
>> We are using xmlbeans databinding, we couldn't go for ADB as it doesn't
>> supports Complex type extension and restrictions and we have not evaluated
>> other binding options as of now.
>>
>
> What is the Axis2 version you use? ADB supports Complex type extension and
> restrictions.  But again there is a possibility it won't support for all
> variations.
>
> Generally Xmlbeans slower than other data bindings. so you can try jibx and
> jaxbri as well.
>
> thanks,
> Amila.
>
>
>> Thanks,
>> Sudhir
>>
>>
>> On Wed, May 6, 2009 at 3:01 AM, Dennis Sosnoski  wrote:
>>
>>> Hi Sudhir,
>>>
>>> Are you using WS-Security for the service? WS-Security builds an
>>> in-memory model of the XML if you're using signatures (and perhaps at other
>>> times - I haven't checked, but there appeared to be some issues in this
>>> area).
>>>
>>> If you're not using WS-Security this type of data should not be causing
>>> problems. What data binding approach are you using? (ADB, XMLBeans, JiBX,
>>> JAXB?)
>>>
>>>  - Dennis
>>>
>>> --
>>> Dennis M. Sosnoski
>>> SOA and Web Services in Java
>>> Axis2 Training and Consulting
>>> http://www.sosnoski.com - http://www.sosnoski.co.nz
>>> Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117
>>>
>>>
>>> Sudhir Mongia wrote:
>>>
>>>> Hi,
>>>>
>>>> Has anyone got any experience in this type of problem ? One possible
>>>> solution we used temporarily is, pass data fragment in in a call and do
>>>> multiple calls to send the complete data.But we are reluctant to go with
>>>> this approach in production.
>>>>
>>>> Any help/pointer ?
>>>>
>>>> Thanks,
>>>> Sudhir
>>>>
>>>> On Mon, May 4, 2009 at 2:23 PM, Sudhir Mongia 
>>>> >>> sudhir.mon...@gmail.com>> wrote:
>>>>
>>>>Hi,
>>>>
>>>>We have a web method exposed by .net app and we using client stubs
>>>>generated through Axis2. This method accepts an array of objects.
>>>>The object is very heavy object containing 25+ members variables
>>>>of double and string type.
>>>>The calls to this method fails sometimes due to memory when we are
>>>>trying to send large number of objects e.g. 10-20.
>>>>
>>>>Any suggestions/idea , how can we compress the size of data to fix
>>>>this problem? We have control up to some extent on server side as
>>>>well.
>>>>
>>>>Thanks,
>>>>Sudhir
>>>>
>>>>
>>>>
>>
>
>
> --
> Amila Suriarachchi
> WSO2 Inc.
> blog: http://amilachinthaka.blogspot.com/
>

MTOM works only with base64 or it supports other types as well ?

[Sudhir Mongia]

Hi,
Just needed confirmation from the experts.

I was reading through internet that MTOM is supported for the elements
defined as base64Binary in the wsdl. Is this true ? Can't we use MTOM to
transfer objects of any type other then base64Binary?

Thanks,
Sudhir

Re: Handling Large data in a method call

[Sudhir Mongia]

Hi Dennis,
Currently We are going with the other alternative of making multiple calls
to send data. Still need to see other binding options JiBX and JAXB.

Thanks,
Sudhir

On Wed, May 6, 2009 at 11:01 AM, Dennis Sosnoski  wrote:

> HTTP chunking is probably already in use, but in any case is unlikely to
> make any difference in your memory usage. XMLBeans *always* builds the
> document representation in memory - that's just how it's written. The
> representation it builds is not as memory-intensive as that used by
> WS-Security, but it's still a lot more than the size of the data objects
> that are being serialized.
>
> Your other alternative is to use multiple messages to send the data. Since
> you have some control over the server side you should be able to change the
> interface to allow multiple calls to the same operation. This would allow
> you to just break up the data into multiple requests when it gets beyond a
> certain size (perhaps 2 objects, or whatever number makes sense). Maybe
> this is what you meant by the reference to chunking?
>
>  - Dennis
>
>
>
> Sudhir Mongia wrote:
>
>> Hi Dennis,
>>
>> Thanks for your reply, Sorry I missed to thanks you in my previous email,
>> I was slightly inside the problem.
>> Just to add here we are also thinking of using another approaches like
>> http chunking.
>>
>> Thanks,
>> Sudhir
>>
>> On Wed, May 6, 2009 at 10:12 AM, Sudhir Mongia 
>> > sudhir.mon...@gmail.com>> wrote:
>>
>>Hi Dennis,
>>
>>We are not using WS-Security. Still its paining us.
>>The problem we are facing is memory consumption while  serialization.
>>We are using xmlbeans databinding, we couldn't go for ADB as it
>>doesn't supports Complex type extension and restrictions and we
>>have not evaluated other binding options as of now.
>>
>>Thanks,
>>Sudhir
>>
>>
>>On Wed, May 6, 2009 at 3:01 AM, Dennis Sosnoski ><mailto:d...@sosnoski.com>> wrote:
>>
>>Hi Sudhir,
>>
>>Are you using WS-Security for the service? WS-Security builds
>>an in-memory model of the XML if you're using signatures (and
>>perhaps at other times - I haven't checked, but there appeared
>>to be some issues in this area).
>>
>>If you're not using WS-Security this type of data should not
>>be causing problems. What data binding approach are you using?
>>(ADB, XMLBeans, JiBX, JAXB?)
>>
>> - Dennis
>>
>>--Dennis M. Sosnoski
>>SOA and Web Services in Java
>>Axis2 Training and Consulting
>>http://www.sosnoski.com - http://www.sosnoski.co.nz
>>Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117
>>
>>
>>Sudhir Mongia wrote:
>>
>>Hi,
>>
>>    Has anyone got any experience in this type of problem ?
>>One possible solution we used temporarily is, pass data
>>fragment in in a call and do multiple calls to send the
>>complete data.But we are reluctant to go with this
>>approach in production.
>>
>>Any help/pointer ?
>>
>>Thanks,
>>Sudhir
>>
>>On Mon, May 4, 2009 at 2:23 PM, Sudhir Mongia
>>mailto:sudhir.mon...@gmail.com>
>><mailto:sudhir.mon...@gmail.com
>><mailto:sudhir.mon...@gmail.com>>> wrote:
>>
>>   Hi,
>>
>>   We have a web method exposed by .net app and we using
>>client stubs
>>   generated through Axis2. This method accepts an array
>>of objects.
>>   The object is very heavy object containing 25+ members
>>variables
>>   of double and string type.
>>   The calls to this method fails sometimes due to memory
>>when we are
>>   trying to send large number of objects e.g. 10-20.
>>
>>   Any suggestions/idea , how can we compress the size of
>>data to fix
>>   this problem? We have control up to some extent on
>>server side as
>>   well.
>>
>>   Thanks,
>>   Sudhir
>>
>>
>>
>>
>>

Re: Handling Large data in a method call

[Sudhir Mongia]

Hi Dennis,
Thanks for your reply, Sorry I missed to thanks you in my previous email, I
was slightly inside the problem.

Just to add here we are also thinking of using another approaches like http
chunking.

Thanks,
Sudhir

On Wed, May 6, 2009 at 10:12 AM, Sudhir Mongia wrote:

> Hi Dennis,
> We are not using WS-Security. Still its paining us.
>
> The problem we are facing is memory consumption while  serialization.
>
> We are using xmlbeans databinding, we couldn't go for ADB as it doesn't
> supports Complex type extension and restrictions and we have not evaluated
> other binding options as of now.
>
> Thanks,
> Sudhir
>
>
> On Wed, May 6, 2009 at 3:01 AM, Dennis Sosnoski  wrote:
>
>> Hi Sudhir,
>>
>> Are you using WS-Security for the service? WS-Security builds an in-memory
>> model of the XML if you're using signatures (and perhaps at other times - I
>> haven't checked, but there appeared to be some issues in this area).
>>
>> If you're not using WS-Security this type of data should not be causing
>> problems. What data binding approach are you using? (ADB, XMLBeans, JiBX,
>> JAXB?)
>>
>>  - Dennis
>>
>> --
>> Dennis M. Sosnoski
>> SOA and Web Services in Java
>> Axis2 Training and Consulting
>> http://www.sosnoski.com - http://www.sosnoski.co.nz
>> Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117
>>
>>
>> Sudhir Mongia wrote:
>>
>>> Hi,
>>>
>>> Has anyone got any experience in this type of problem ? One possible
>>> solution we used temporarily is, pass data fragment in in a call and do
>>> multiple calls to send the complete data.But we are reluctant to go with
>>> this approach in production.
>>>
>>> Any help/pointer ?
>>>
>>> Thanks,
>>> Sudhir
>>>
>>> On Mon, May 4, 2009 at 2:23 PM, Sudhir Mongia 
>>> >> sudhir.mon...@gmail.com>> wrote:
>>>
>>>Hi,
>>>
>>>We have a web method exposed by .net app and we using client stubs
>>>generated through Axis2. This method accepts an array of objects.
>>>The object is very heavy object containing 25+ members variables
>>>of double and string type.
>>>The calls to this method fails sometimes due to memory when we are
>>>trying to send large number of objects e.g. 10-20.
>>>
>>>Any suggestions/idea , how can we compress the size of data to fix
>>>this problem? We have control up to some extent on server side as
>>>well.
>>>
>>>Thanks,
>>>Sudhir
>>>
>>>
>>>
>

Re: Handling Large data in a method call

[Sudhir Mongia]

Hi Dennis,
We are not using WS-Security. Still its paining us.

The problem we are facing is memory consumption while  serialization.

We are using xmlbeans databinding, we couldn't go for ADB as it doesn't
supports Complex type extension and restrictions and we have not evaluated
other binding options as of now.

Thanks,
Sudhir

On Wed, May 6, 2009 at 3:01 AM, Dennis Sosnoski  wrote:

> Hi Sudhir,
>
> Are you using WS-Security for the service? WS-Security builds an in-memory
> model of the XML if you're using signatures (and perhaps at other times - I
> haven't checked, but there appeared to be some issues in this area).
>
> If you're not using WS-Security this type of data should not be causing
> problems. What data binding approach are you using? (ADB, XMLBeans, JiBX,
> JAXB?)
>
>  - Dennis
>
> --
> Dennis M. Sosnoski
> SOA and Web Services in Java
> Axis2 Training and Consulting
> http://www.sosnoski.com - http://www.sosnoski.co.nz
> Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117
>
>
> Sudhir Mongia wrote:
>
>> Hi,
>>
>> Has anyone got any experience in this type of problem ? One possible
>> solution we used temporarily is, pass data fragment in in a call and do
>> multiple calls to send the complete data.But we are reluctant to go with
>> this approach in production.
>>
>> Any help/pointer ?
>>
>> Thanks,
>> Sudhir
>>
>> On Mon, May 4, 2009 at 2:23 PM, Sudhir Mongia 
>> > sudhir.mon...@gmail.com>> wrote:
>>
>>Hi,
>>
>>We have a web method exposed by .net app and we using client stubs
>>generated through Axis2. This method accepts an array of objects.
>>The object is very heavy object containing 25+ members variables
>>of double and string type.
>>The calls to this method fails sometimes due to memory when we are
>>trying to send large number of objects e.g. 10-20.
>>
>>Any suggestions/idea , how can we compress the size of data to fix
>>this problem? We have control up to some extent on server side as
>>well.
>>
>>Thanks,
>>Sudhir
>>
>>
>>

Re: Handling Large data in a method call

[Sudhir Mongia]

Hi,
Has anyone got any experience in this type of problem ? One possible
solution we used temporarily is, pass data fragment in in a call and do
multiple calls to send the complete data.But we are reluctant to go with
this approach in production.

Any help/pointer ?

Thanks,
Sudhir

On Mon, May 4, 2009 at 2:23 PM, Sudhir Mongia wrote:

> Hi,
> We have a web method exposed by .net app and we using client stubs
> generated through Axis2. This method accepts an array of objects. The object
> is very heavy object containing 25+ members variables of double and string
> type.
>
> The calls to this method fails sometimes due to memory when we are trying
> to send large number of objects e.g. 10-20.
>
> Any suggestions/idea , how can we compress the size of data to fix this
> problem? We have control up to some extent on server side as well.
>
> Thanks,
> Sudhir
>
>
>
>

Re: Limitations in using ADB for our ws-clent

[Sudhir Mongia]

Hi Amila,

Any word on this.
Damian any thing from your side.
Sudhir

On Thu, Apr 30, 2009 at 7:55 PM, Sudhir Mongia wrote:

> Hi Amila,
>  I am also running into the same issue.
>
> Could you please confirm which version of Axis2-ADB support both extension
> and restrictions?
>
> I can see the following on  
> <http://ws.apache.org/axis2/1_4_1/adb/adb-howto.html>
> http://ws.apache.org/axis2/1_4_1/adb/adb-howto.html
>
> Known Limitations
>
> ADB is meant to be a 'Simple' databinding framework and was not meant to
> compile all types of schemas. The following limitations are the most
> highlighted.
>
>1. Complex Type Extensions and Restrictions.
>
>
> The documentation says, it is a known limitation.
>
> Thanks,
> Sudhir
>
> On Thu, Apr 30, 2009 at 3:42 PM, Amila Suriarachchi <
> amilasuriarach...@gmail.com> wrote:
>
>>
>>
>> On Thu, Apr 30, 2009 at 8:58 AM, Damian Carey  wrote:
>>
>>> Hello,
>>>
>>> I'm moderately experience Java Desktop (Swing/RMI/DB/Hibernate etc)
>>> developer with some XML experience, but no SOAP experience. My current
>>> Axis2 problem is just that I do not have experienced eyes, and so I
>>> can't accurately "sniff" potential problems. I would be most
>>> appreciative of any suggestions / guidance / advice  regarding these
>>> beginners issues.
>>>
>>> We have a task to connect ourselves to an existing webservice, and we
>>> have been given a WSDL file to develop our web services client.
>>>
>>>
>>> Question 1: Limitations of ADB:
>>> Firstly after reading
>>>
>>> http://ws.apache.org/axis2/1_4_1/userguide-creatingclients.html#choosingclient
>>> I decided on ADB as a client as it seems to be the simplest. However,
>>> that web page has the following intriguing comment regarding ADB :
>>> "... and has difficulty with structures such as XML Schema element
>>> extensions and restrictions".  For what it is worth I have scanned the
>>> WSDL file and found zero instances of the string "extension", and 26
>>> instances of the string "restriction". All the "restriction"s are of
>>> the form
>>> 
>>>
>>>
>>>
>>>
>>> 
>>>
>>> Is it easy to tell if these potential ADB "difficulties" applies to us?
>>> Can experienced eyes look through a WSDL and recognise where ADB
>>> will/may have a problem?
>>> Or is it just a matter of waiting until testing to discover problems?
>>
>>
>> Currently ADB supports both extension and restrictions.
>>
>>>
>>>
>>>
>>> Question 2: Size of the stub:
>>> Going through the process on the Axis2 web site I created the stub.
>>> The WSDL file is >50KB, and the generated STUB is more than 50,000
>>> lines long and 2.4MB in size!!!  Now I was surprised by the size, but
>>> browsing through the stub it all seems reasonable and in order - even
>>> if it is a touch verbose.  I really don't care about the size if it is
>>> going to work OK.  I only care about the size if it may indicate that
>>> there may be a problem.
>>
>>
>> use -u option.
>>
>>>
>>>
>>> Does the massive size of the stub indicate any problem?
>>> Does it suggest that ADB may not cope and perhaps we should pursue one
>>> of the other methods? (such as XMLBeans or JiBX)
>>
>>
>> thanks,
>> Amila.
>>
>>>
>>>
>>>
>>> Any guidance would be much appreciated.
>>> Thanks for your time.
>>>
>>> -Damian
>>>
>>
>>
>>
>> --
>> Amila Suriarachchi
>> WSO2 Inc.
>> blog: http://amilachinthaka.blogspot.com/
>>
>
>

Handling Large data in a method call

[Sudhir Mongia]

Hi,
We have a web method exposed by .net app and we using client stubs generated
through Axis2. This method accepts an array of objects. The object is very
heavy object containing 25+ members variables of double and string type.

The calls to this method fails sometimes due to memory when we are trying to
send large number of objects e.g. 10-20.

Any suggestions/idea , how can we compress the size of data to fix this
problem? We have control up to some extent on server side as well.

Thanks,
Sudhir

Re: Limitations in using ADB for our ws-clent

[Sudhir Mongia]

Hi Amila,
 I am also running into the same issue.

Could you please confirm which version of Axis2-ADB support both extension
and restrictions?

I can see the following on

http://ws.apache.org/axis2/1_4_1/adb/adb-howto.html

Known Limitations

ADB is meant to be a 'Simple' databinding framework and was not meant to
compile all types of schemas. The following limitations are the most
highlighted.

   1. Complex Type Extensions and Restrictions.


The documentation says, it is a known limitation.

Thanks,
Sudhir

On Thu, Apr 30, 2009 at 3:42 PM, Amila Suriarachchi <
amilasuriarach...@gmail.com> wrote:

>
>
> On Thu, Apr 30, 2009 at 8:58 AM, Damian Carey  wrote:
>
>> Hello,
>>
>> I'm moderately experience Java Desktop (Swing/RMI/DB/Hibernate etc)
>> developer with some XML experience, but no SOAP experience. My current
>> Axis2 problem is just that I do not have experienced eyes, and so I
>> can't accurately "sniff" potential problems. I would be most
>> appreciative of any suggestions / guidance / advice  regarding these
>> beginners issues.
>>
>> We have a task to connect ourselves to an existing webservice, and we
>> have been given a WSDL file to develop our web services client.
>>
>>
>> Question 1: Limitations of ADB:
>> Firstly after reading
>>
>> http://ws.apache.org/axis2/1_4_1/userguide-creatingclients.html#choosingclient
>> I decided on ADB as a client as it seems to be the simplest. However,
>> that web page has the following intriguing comment regarding ADB :
>> "... and has difficulty with structures such as XML Schema element
>> extensions and restrictions".  For what it is worth I have scanned the
>> WSDL file and found zero instances of the string "extension", and 26
>> instances of the string "restriction". All the "restriction"s are of
>> the form
>> 
>>
>>
>>
>>
>> 
>>
>> Is it easy to tell if these potential ADB "difficulties" applies to us?
>> Can experienced eyes look through a WSDL and recognise where ADB
>> will/may have a problem?
>> Or is it just a matter of waiting until testing to discover problems?
>
>
> Currently ADB supports both extension and restrictions.
>
>>
>>
>>
>> Question 2: Size of the stub:
>> Going through the process on the Axis2 web site I created the stub.
>> The WSDL file is >50KB, and the generated STUB is more than 50,000
>> lines long and 2.4MB in size!!!  Now I was surprised by the size, but
>> browsing through the stub it all seems reasonable and in order - even
>> if it is a touch verbose.  I really don't care about the size if it is
>> going to work OK.  I only care about the size if it may indicate that
>> there may be a problem.
>
>
> use -u option.
>
>>
>>
>> Does the massive size of the stub indicate any problem?
>> Does it suggest that ADB may not cope and perhaps we should pursue one
>> of the other methods? (such as XMLBeans or JiBX)
>
>
> thanks,
> Amila.
>
>>
>>
>>
>> Any guidance would be much appreciated.
>> Thanks for your time.
>>
>> -Damian
>>
>
>
>
> --
> Amila Suriarachchi
> WSO2 Inc.
> blog: http://amilachinthaka.blogspot.com/
>

Re: comparison of different databinding

[Sudhir Mongia]

Thanks Richard and Robert. I'll look into these links.
Sudhir.

On Thu, Apr 23, 2009 at 12:54 AM, robert lazarski
wrote:

> On Wed, Apr 22, 2009 at 3:29 PM, Li, Zhenge  wrote:
> > Hi Sudhir,
> >
> >
> >
> > I ran into below links a while ago.
> >
> >
> >
> > Some charts in:
> >
> > http://wso2.org/library/588
> >
> >
> >
> > Comments by Mark D. Hansen, Author of "SOA Using Java Web Services".
> >
> >
> http://saloon.javaranch.com/cgi-bin/ubb/ultimatebb.cgi?ubb=get_topic&f=51&t=004657
> >
> >
> >
> > -richard
> >
>
> Both links are helpful but I think missing the benefits of each, plus
> a few options are missing. My rough rule of thumb for my projects are:
>
> 1) If you have been given a WSDL to use and don't have existing code
> to send over the wire - use xmlbeans or jaxb since they have close to
> if not complete 100% xml schema spec support. Some frameworks like
> JIBX are improving but not at 100% yet. I prefer xmlbeans because it
> has a validate() method for it Objects, which is great for debugging.
> xmlbeans gets a bad rap for being slower than the other options, but
> often in my case only negligibly so.
>
> 2) If you don't have an WSDL yet and you want to send pre-existing
> objects - like hibernate BO's for example - the JIBX tools to create
> an xml schema and wsdl from code is about the best out there at the
> moment.
>
> 3) If you have neither an WSDL or pre-existing code, and are committed
> to using only axis2 or perhaps the Spring WS framework, adb is a
> reasonable choice.
>
> 4) If performance is the top concern, I'd say JIBX is a good choice.
>
> 5) If JSR standards are important, use JAX-WS and JAXB.
>
> All of those options are available in Axis2.
>
> - R
>
>
> > 
> >
> > From: Sudhir Mongia [mailto:sudhir.mon...@gmail.com]
> > Sent: April 22, 2009 2:31 PM
> > To: axis-user@ws.apache.org
> > Subject: comparison of different databinding
> >
> >
> >
> > Hi,
> >
> >
> >
> > We have very complex wsdl and I was looking into the data
> binding approaches
> > in AXIS2 and trying to find out which one suits my project.
> >
> >
> >
> > Then I just thought of writing here if we have any comparative study
> > chart/table ready with us, which lists pros/cons and applicably each in
> > different scenarios.
> >
> >
> >
> > Please share if anyone has done this execise.
> >
> >
> >
> > Thnx,
> >
> > Sudhir Mongia
>

comparison of different databinding

[Sudhir Mongia]

Hi,

We have very complex wsdl and I was looking into the data binding approaches
in AXIS2 and trying to find out which one suits my project.

Then I just thought of writing here if we have any comparative study
chart/table ready with us, which lists pros/cons and applicably each in
different scenarios.

Please share if anyone has done this execise.

Thnx,
Sudhir Mongia

Re: Axis2 Jboss and SSL issue

[Sudhir Mongia]

You can see the tutorials here to enable SSL on JBoss.
http://www.theserverside.com/discussions/thread.tss?thread_id=22243
http://roneiv.wordpress.com/2008/01/03/jboss-tutorial-how-to-enable-ssl-https-on-jboss-as-well-as-other-nice-to-know-configurations/


Thanks,
Sudhir

On Thu, Apr 16, 2009 at 3:47 PM, Darshana ®  wrote:

> Hi,
>
> I'm trying to configure SSL for axis2 on jboss. Problem is I dont know
> where to put the .jks file. I tried putting the jks file to following
> locations.
>
> WEB-INF directory of the web archive.
> META-INF directory of the web archive
> jboss home directory
> {jboss home}/server/default directory
> {jboss home}/server/default/deploy directory
> {jboss home}/bin directory
>
> Also I tried with the absolute path of the .jks (localhost.jks in my case)
> file.
>
> Following are my Keystore and Truststore parameters in
> transportReceiver and transportSender beans included in the axis2.xml
>
> 
> 
> localhost.jks
> JKS
> 123456
> 123456
> 
> 
> 
> 
> localhost.jks
> JKS
> 123456
> 
> 
>
> When I'm starting the jboss server, everytime it gives an error like this.
>
> java.lang.NullPointerException
> at
> org.apache.axis2.transport.nhttp.HttpCoreNIOSSLListener.getSSLContext(HttpCoreNIOSSLListener.java:96)
> at
> org.apache.axis2.transport.nhttp.HttpCoreNIOListener.init(HttpCoreNIOListener.java:151)
> at
> org.apache.axis2.engine.ListenerManager.start(ListenerManager.java:125)
> at
> org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:442)
> at
> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1161)
> at
> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:981)
> at
> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4069)
> at
> org.apache.catalina.core.StandardContext.start(StandardContext.java:4373)
> at
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:761)
> at
> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:741)
> at
> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:553)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:297)
> at
> org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
> at
> org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> at
> org.apache.catalina.core.StandardContext.init(StandardContext.java:5310)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>
> But when I commented out above mentioned parameters from axis2.xml
> file, server starts sucessfully without any errors.
>
> Please give me idea, where should I put the localhost.jks file
>

Facing Problem while Implementing WSSecurity Token based Authentication

[Sudhir Mongia]

Hi,
I have created a sample Say Hello Webservice and I am trying to do basic
implementation of WSSecurity using Axis2 and RamPart.

I am following the tutorial http://wso2.org/library/3190. Apart from this
also followed the link http://wso2.org/library/3787.which addresses
the compatibility issues with Axis2 1.4 and rampart 1.4. I have policy added
in services.xml and at bindings level in WSDL. At the end when I am trying
to run it I am getting "Invalid Security Error".

Here is the details of Environment
Axis2 version :Axis2 1.4
Rampart version: Rampart 1.4
Application Server :JBoss 4.0.5

WSDL file and services.xml is attached with this email.

I have pasted here request and response soap message, captured from TCPMON.
I have given the errors which I am getting on server side and client side.

Request SOAP Message


http://www.w3.org/2003/05/soap-envelope";>

http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";
soapenv:mustUnderstand="true">
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";
wsu:Id="UsernameToken-31658378">
apache
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText
">password




http://HelloWeb/xsd";>
Sudhir Mongia 1




Response Soap Message


http://www.w3.org/2003/05/soap-envelope";>


soapenv:Receiver
InvalidSecurity






Error on Client side
org.apache.axis2.AxisFault: InvalidSecurity
at
org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:512)
at
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:370)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:416)
at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:228)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
at
com.sample.webservice.client.HelloWebServiceStub.sayHello(HelloWebServiceStub.java:192)
at com.sample.webservice.client.TestWebService.main(TestWebService.java:52)

Error on Server side
16:10:00,138 INFO  [STDOUT] 16:10:00,138 ERROR [AxisEngine] InvalidSecurity
org.apache.axis2.AxisFault: InvalidSecurity
at
org.apache.rampart.handler.PostDispatchVerificationHandler.invoke(PostDispatchVerificationHandler.java:143)
at org.apache.axis2.engine.Phase.invoke(Phase.java:317)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:264)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:163)
at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275)
at
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:131)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at
org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
at
org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at
org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at
org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
at java.lang.Thread.run(Thread.java:595)


Any Pointer on this. Please let me know, if you need more information from
my side.

Thanks,
Sudhir
http://HelloWeb/"; xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"; xmlns:mime="http://sc

Question about WSSecurity in Axis2

[Sudhir Mongia]

Hi,
We need to secure our web service. We got to know about rampart module to
implement. Before looking into any kind of documentation for rampart, We
were in impression that we need to do changes on server side and the client
will come to know about the security related information through WSDL only.

When we looked into that rampart, It changed our basic perception.Rampart
documentation says "when using Rampart with Axis2, it must be engaged at
both ends".Why so ?? If my client is Java  based then we can engage rampart
module on client side. What if our client is .Net client and needs to access
the web service?

Is it the way it works? Then, How the policy and keys related information
will be communicated to client?

Is there any other way we can implement WSSecurity in Axis2 ? So that we'll
be doing changes on server side and client will need to look into wsdl only.

I know I am putting questions marks after each sentence. But I can't help
it, this is what I think as of now and expecting you people to throw some
light on the issue.

Thanks,
Sudhir

WSSecurity Implementaton

[Sudhir Mongia]

Hi,
I have been asked to learn and implement WSSecurity in Web services exposed
by us. We are using Axis2 version 1.4.

Can anyone tell where to start?

Thanks,
Sudhir

Re: Facing Problem with AXIS21.4

[Sudhir Mongia]

Hi Asankha,
Thanks a lot, I can see the problem that you have mentioned. I need to check
it from the .Net side, which sometimes generates these bad requests.

Thanks,
Sudhir

On Tue, Dec 9, 2008 at 4:48 PM, Sudhir Mongia <[EMAIL PROTECTED]>wrote:

> Hi Asankha,
> Thanks for the quick reply. Let me go back and check what you are
> saying.will get back to you soon.
>
> Thanks,
> Sudhir
>
>
>
>
> On Tue, Dec 9, 2008 at 4:42 PM, Asankha C. Perera <[EMAIL PROTECTED]>wrote:
>
>>  Hi Sudhir
>>
>> Error 1  :com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected
>> character '-' (code 45) in prolog; expected '<'
>>   at [row,col {unknown-source}]: [2,1]
>>
>>  Request
>> POST /wsabacus/services/wsabacus HTTP/1.1
>> User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client
>> Protocol 2.0.50727.1433)
>> Content-Type: application/soap+xml; charset=utf-8;
>> action="urn:getCalculationStatus"
>> Host: 10.253.101.130:
>> Cookie: JSESSIONID=ABD43A765104D4ED3A0EFF61DAD68ED8
>> Content-Length: 1463
>> Expect: 100-continue
>>
>>  MIMEBoundary633643641416156381
>> content-id: <[EMAIL PROTECTED]>
>> content-type: application/xop+xml; charset=utf-8;
>> type="application/soap+xml; charset=utf-8"
>> content-transfer-encoding: binary
>>
>>  http://www.w3.org/2004/08/xop/include";
>> xmlns:soap="http://www.w3.org/2003/05/soap-envelope"; xmlns:xsi="
>> http://www.w3.org/2001/XMLSchema-instance"; xmlns:xsd="
>> http://www.w3.org/2001/XMLSchema"; xmlns:wsa="
>> http://schemas.xmlsoap.org/ws/2004/08/addressing"; xmlns:wsse="
>> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";
>> xmlns:wsu="
>> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";>> xmlns:env="http://www.w3.org/2003/05/soap-envelope
>> ">urn:getCalculationStatusurn:uuid:bf39e47c-c561-4e7c-b7db-bc47980381db
>> http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous
>> 
>> http://10.253.101.130:/wsabacus/services/wsabacus> wsu:Id="Timestamp-565f869f-fdd6-40ef-a2fe-a716685f44b2">2008-12-08T14:45:41Z2008-12-08T14:50:41Z> xmlns="http://wsabacus/xsd
>> ">087ed846
>> MIMEBoundary633643641416156381--
>>
>> This request is invalid. See http://www.w3.org/TR/SOAP-attachmentsSection #5 
>> - Http Binding for a sample. The backend is expecting the mime
>> boundary in the content type. Since it doesn't find it, it thinks the
>> request is XML and tries to parse, and hits the first "-" of the payload
>> (i.e. MIME...part) and complains of this character
>>
>>  > xml:lang="en-US">com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected
>> character '-' (code 45) in prolog; expected '<'
>>  at [row,col {unknown-source}]:
>> [2,1]
>>
>>
>>   Error 2: Mime parts not found. Stream ended while searching for the
>> boundary
>>
>>
>>  MIMEBoundary633643641375692552--
>> POST /wsabacus/services/wsabacus HTTP/1.1
>> User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client
>> Protocol 2.0.50727.1433)
>> Host: 10.253.101.130:
>> Cookie: JSESSIONID=ABD43A765104D4ED3A0EFF61DAD68ED8
>> Content-Type: multipart/related; type="application/xop+xml";
>> boundary=--MIMEBoundary633643641416156381; start="<
>> [EMAIL PROTECTED]>"; start-info="application/soap+xml;
>> charset=utf-8"
>> Content-Length: 1462
>> Expect: 100-continue
>>
>>
>>  MIMEBoundary633643641818451206
>> content-id: <[EMAIL PROTECTED]>
>> content-type: application/xop+xml; charset=utf-8;
>> type="application/soap+xml; charset=utf-8"
>> content-transfer-encoding: binary
>>
>>  http://www.w3.org/2004/08/xop/include";
>> xmlns:soap="http://www.w3.org/2003/05/soap-envelope"; xmlns:xsi="
>> http://www.w3.org/2001/XMLSchema-instance"; xmlns:xsd="
>> http://www.w3.org/2001/XMLSchema"; xmlns:wsa="
>> http://schemas.xmlsoap.org/ws/2004/08/addressing"; xmlns:wsse="
>> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";
>> xmlns:wsu="
>> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";>> xmlns:env="http://www.w3.org/2003/05/soap-envelope
>> ">urn:deleteDataseturn:uuid:25605344-dae6-4777-b493-77e650eae14f
>> http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous
>> 
>> http://10.253.101.130:/wsabacus/services/wsabacus> wsu:Id="Timestamp-c155c096-4465-47f0-ad44-86054a9189fd">2008-12-08T14:46:21Z2008-12-08T14:51:21Z> xmlns="http://wsabacus/xsd
>> ">Q20_20081208_194107_CoBankv3
>> MIMEBoundary633643641818451206--
>>
>> The content type in this one states the boundary as "
>> --MIMEBoundary633643641416156381" but this is not found on the payload;
>> which contains "MIMEBoundary633643641818451206"
>>
>> cheers
>> asankha
>>
>> --
>> Asankha C. Pererahttp://adroitlogic.org
>> http://esbmagic.blogspot.com
>>
>>
>

Re: Facing Problem with AXIS21.4

[Sudhir Mongia]

Hi Asankha,
Thanks for the quick reply. Let me go back and check what you are
saying.will get back to you soon.

Thanks,
Sudhir




On Tue, Dec 9, 2008 at 4:42 PM, Asankha C. Perera <[EMAIL PROTECTED]>wrote:

>  Hi Sudhir
>
> Error 1  :com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected
> character '-' (code 45) in prolog; expected '<'
>   at [row,col {unknown-source}]: [2,1]
>
>  Request
> POST /wsabacus/services/wsabacus HTTP/1.1
> User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client
> Protocol 2.0.50727.1433)
> Content-Type: application/soap+xml; charset=utf-8;
> action="urn:getCalculationStatus"
> Host: 10.253.101.130:
> Cookie: JSESSIONID=ABD43A765104D4ED3A0EFF61DAD68ED8
> Content-Length: 1463
> Expect: 100-continue
>
>  MIMEBoundary633643641416156381
> content-id: <[EMAIL PROTECTED]>
> content-type: application/xop+xml; charset=utf-8;
> type="application/soap+xml; charset=utf-8"
> content-transfer-encoding: binary
>
>  http://www.w3.org/2004/08/xop/include";
> xmlns:soap="http://www.w3.org/2003/05/soap-envelope"; xmlns:xsi="
> http://www.w3.org/2001/XMLSchema-instance"; xmlns:xsd="
> http://www.w3.org/2001/XMLSchema"; xmlns:wsa="
> http://schemas.xmlsoap.org/ws/2004/08/addressing"; xmlns:wsse="
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";
> xmlns:wsu="
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";> xmlns:env="http://www.w3.org/2003/05/soap-envelope
> ">urn:getCalculationStatusurn:uuid:bf39e47c-c561-4e7c-b7db-bc47980381db
> http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous
> 
> http://10.253.101.130:/wsabacus/services/wsabacus wsu:Id="Timestamp-565f869f-fdd6-40ef-a2fe-a716685f44b2">2008-12-08T14:45:41Z2008-12-08T14:50:41Z xmlns="http://wsabacus/xsd
> ">087ed846
> MIMEBoundary633643641416156381--
>
> This request is invalid. See http://www.w3.org/TR/SOAP-attachments Section
> #5 - Http Binding for a sample. The backend is expecting the mime boundary
> in the content type. Since it doesn't find it, it thinks the request is XML
> and tries to parse, and hits the first "-" of the payload (i.e.
> MIME...part) and complains of this character
>
>   xml:lang="en-US">com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected
> character '-' (code 45) in prolog; expected '<'
>  at [row,col {unknown-source}]:
> [2,1]
>
>
>   Error 2: Mime parts not found. Stream ended while searching for the
> boundary
>
>
>  MIMEBoundary633643641375692552--
> POST /wsabacus/services/wsabacus HTTP/1.1
> User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client
> Protocol 2.0.50727.1433)
> Host: 10.253.101.130:
> Cookie: JSESSIONID=ABD43A765104D4ED3A0EFF61DAD68ED8
> Content-Type: multipart/related; type="application/xop+xml";
> boundary=--MIMEBoundary633643641416156381; start="<
> [EMAIL PROTECTED]>"; start-info="application/soap+xml;
> charset=utf-8"
> Content-Length: 1462
> Expect: 100-continue
>
>
>  MIMEBoundary633643641818451206
> content-id: <[EMAIL PROTECTED]>
> content-type: application/xop+xml; charset=utf-8;
> type="application/soap+xml; charset=utf-8"
> content-transfer-encoding: binary
>
>  http://www.w3.org/2004/08/xop/include";
> xmlns:soap="http://www.w3.org/2003/05/soap-envelope"; xmlns:xsi="
> http://www.w3.org/2001/XMLSchema-instance"; xmlns:xsd="
> http://www.w3.org/2001/XMLSchema"; xmlns:wsa="
> http://schemas.xmlsoap.org/ws/2004/08/addressing"; xmlns:wsse="
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";
> xmlns:wsu="
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";> xmlns:env="http://www.w3.org/2003/05/soap-envelope
> ">urn:deleteDataseturn:uuid:25605344-dae6-4777-b493-77e650eae14f
> http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous
> 
> http://10.253.101.130:/wsabacus/services/wsabacus wsu:Id="Timestamp-c155c096-4465-47f0-ad44-86054a9189fd">2008-12-08T14:46:21Z2008-12-08T14:51:21Z xmlns="http://wsabacus/xsd
> ">Q20_20081208_194107_CoBankv3
> MIMEBoundary633643641818451206--
>
> The content type in this one states the boundary as "
> --MIMEBoundary633643641416156381" but this is not found on the payload;
> which contains "MIMEBoundary633643641818451206"
>
> cheers
> asankha
>
> --
> Asankha C. Pererahttp://adroitlogic.org
> http://esbmagic.blogspot.com
>
>

Re: Facing Problem with AXIS21.4

[Sudhir Mongia]

Hi,

Thanks for the reply.
I got the following soap messages for request and response using TCPMON.

Error 1  :com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character
'-' (code 45) in prolog; expected '<'
 at [row,col {unknown-source}]: [2,1]

Request
POST /wsabacus/services/wsabacus HTTP/1.1
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client
Protocol 2.0.50727.1433)
Content-Type: application/soap+xml; charset=utf-8;
action="urn:getCalculationStatus"
Host: 10.253.101.130:
Cookie: JSESSIONID=ABD43A765104D4ED3A0EFF61DAD68ED8
Content-Length: 1463
Expect: 100-continue

MIMEBoundary633643641416156381
content-id: <[EMAIL PROTECTED]>
content-type: application/xop+xml; charset=utf-8;
type="application/soap+xml; charset=utf-8"
content-transfer-encoding: binary

http://www.w3.org/2004/08/xop/include";
xmlns:soap="http://www.w3.org/2003/05/soap-envelope"; xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance"; xmlns:xsd="
http://www.w3.org/2001/XMLSchema"; xmlns:wsa="
http://schemas.xmlsoap.org/ws/2004/08/addressing"; xmlns:wsse="
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";
xmlns:wsu="
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";>http://www.w3.org/2003/05/soap-envelope
">urn:getCalculationStatusurn:uuid:bf39e47c-c561-4e7c-b7db-bc47980381db
http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous

http://10.253.101.130:/wsabacus/services/wsabacus2008-12-08T14:45:41Z2008-12-08T14:50:41Zhttp://wsabacus/xsd
">087ed846
MIMEBoundary633643641416156381--

Response
HTTP/1.1 100 Continue

HTTP/1.1 500 Internal Server Error
Server: Apache-Coyote/1.1
X-Powered-By: Servlet 2.4; JBoss-4.0.5.GA (build: CVSTag=Branch_4_0
date=200610162339)/Tomcat-5.5
Content-Type: multipart/related;
boundary=MIMEBoundaryurn_uuid_57D42B83CEC681852E1228747548978;
type="application/xop+xml"; start="<
0.urn:uuid:[EMAIL PROTECTED]<[EMAIL PROTECTED]>>";
start-info="application/soap+xml"; action="
http://www.w3.org/2005/08/addressing/soap/fault";
Transfer-Encoding: chunked
Date: Mon, 08 Dec 2008 14:45:44 GMT
Connection: close

38d
--MIMEBoundaryurn_uuid_57D42B83CEC681852E1228747548978
Content-Type: application/xop+xml; charset=utf-8;
type="application/soap+xml"
Content-Transfer-Encoding: binary
Content-ID: <0.urn:uuid:[EMAIL PROTECTED]<[EMAIL PROTECTED]>
>

http://www.w3.org/2003/05/soap-envelope";>http://www.w3.org/2005/08/addressing";>
http://www.w3.org/2005/08/addressing/soap/fault
soapenv:Receivercom.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected
character '-' (code 45) in prolog; expected '<'
 at [row,col {unknown-source}]:
[2,1]

38

--MIMEBoundaryurn_uuid_57D42B83CEC681852E1228747548978
2
--
0


Error 2: Mime parts not found. Stream ended while searching for the boundary

Request


MIMEBoundary633643641375692552--
POST /wsabacus/services/wsabacus HTTP/1.1
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client
Protocol 2.0.50727.1433)
Host: 10.253.101.130:
Cookie: JSESSIONID=ABD43A765104D4ED3A0EFF61DAD68ED8
Content-Type: multipart/related; type="application/xop+xml";
boundary=--MIMEBoundary633643641416156381; start="<
[EMAIL PROTECTED]>"; start-info="application/soap+xml;
charset=utf-8"
Content-Length: 1462
Expect: 100-continue


MIMEBoundary633643641818451206
content-id: <[EMAIL PROTECTED]>
content-type: application/xop+xml; charset=utf-8;
type="application/soap+xml; charset=utf-8"
content-transfer-encoding: binary

http://www.w3.org/2004/08/xop/include";
xmlns:soap="http://www.w3.org/2003/05/soap-envelope"; xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance"; xmlns:xsd="
http://www.w3.org/2001/XMLSchema"; xmlns:wsa="
http://schemas.xmlsoap.org/ws/2004/08/addressing"; xmlns:wsse="
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";
xmlns:wsu="
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";>http://www.w3.org/2003/05/soap-envelope
">urn:deleteDataseturn:uuid:25605344-dae6-4777-b493-77e650eae14f
http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous

http://10.253.101.130:/wsabacus/services/wsabacus2008-12-08T14:46:21Z2008-12-08T14:51:21Zhttp://wsabacus/xsd
">Q20_20081208_194107_CoBankv3
MIMEBoundary633643641818451206--

Response

HTTP/1.1 100 Continue

HTTP/1.1 500 Internal Server Error
Server: Apache-Coyote/1.1
X-Powered-By: Servlet 2.4; JBoss-4.0.5.GA (build: CVSTag=Branch_4_0
date=200610162339)/Tomcat-5.5
Content-Type: multipart/related;
boundary=MIMEBoundaryurn_uuid_57D42B83CEC681852E1228747589256;
type="application/xop+xml"; start="<
0.urn:uuid:[EMAIL PROTECTED]<[EMAIL PROTECTED]>>";
start-info="application/soap+xml"; action="
http://www.w3.org/2005/08/addressing/soap/fault";
Transfer-Encoding: chunked
Date: Mon, 08 Dec 2008 14:46:25 GMT
Connection: close

33a
--MIMEBoundaryurn_uuid_57D42B83CEC681852E1228747589256
Content-Type: application/xop+xml; charset=utf-8;
type="application/soap+xml"
Co

Facing Problem with AXIS21.4

[Sudhir Mongia]

Hi ,
We are using Axis2 1.4 in our project. Its working well for us.

During testing our testing team has reported two issues, which we didn't
face in development and these are sometimes difficult to reproduce even. I
can see the following text in soap faults.

1) Mime parts not found. Stream ended while searching for the boundary

2) com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character '-'
(code 45) in prolog; expected '<'
 at [row,col {unknown-source}]: [2,1]

Any pointer on these. Is there any way to debug axis to find the cause these
problems.

Thanks ,

Sudhir Mongia

getting error "com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character '-' (code 45) in prolog; expected '<'

[Sudhir Mongia]

Hi,
We are using Axis 1.4 and getting the following error sometimes while doing
stress testing. In normal testing we are getting proper results.

"com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character '-'
(code 45) in prolog; expected '<'
at [row,col {unknown-source}]: [2,1]"

Any clue.

Thanks,
Sudhir Mongia

Session Attribute in service.xml

[Sudhir Mongia]

Hi,

We are using Axis2 1.4. We need to add *scope *attribute to servie tag* * in
service.xml.


We have build scripts to generate service.xml file and other files with
wsdl2java task, it doesn't add scope attribute by default and I couldn't see
any option to get scope attribute added to the generated services.xml file.

Any help/suggestion appreciated.

Thanks,
Sudhir Mongia