from:"D"

Thanks again Andreas.  Based on what you said, I was able to find that the wsdd 
was incorrect for that particular service.  It is not spitting out the correct 
XML, and axis2 is happy with it.

Trenton D. Adams
Systems Analyst/Web Software Engineer
Navy Penguins at your service!
Athabasca University
(780) 675-6195
:wq!

- "Trenton D. Adams"  wrote:

> From: "Trenton D. Adams" 
> To: "Andreas Veithen" 
> Cc: axis-user@ws.apache.org
> Sent: Tuesday, May 12, 2009 5:11:43 PM GMT -07:00 US/Canada Mountain
> Subject: Re: axis 2 unexpected Subelement (BUG???)
>
> Thanks Andreas, I think I get it now.  Right, element b is in fact the
> same namespace of a, just the contents are of a different namespace. 
> Right?
> 
> Trenton D. Adams
> Systems Analyst/Web Software Engineer
> Navy Penguins at your service!
> Athabasca University
> (780) 675-6195
> :wq!
> 
> - "Andreas Veithen"  wrote:
> 
> > From: "Andreas Veithen" 
> > To: "Trenton D. Adams" 
> > Cc: axis-user@ws.apache.org
> > Sent: Tuesday, May 12, 2009 5:00:23 PM GMT -07:00 US/Canada
> Mountain
> > Subject: Re: axis 2 unexpected Subelement (BUG???)
> >
> > --QUOTE--
> > This fragment:
> > elementFormDefault="qualified"
> > 
> > indicates that any elements used by the XML instance document which
> > were declared in this schema must be namespace qualified.
> > --QUOTE--
> > 
> > ... and the namespace is the targetNamespace of the schema where
> the
> > element has been declared
> > (http://APASProxy.ServiceContracts/2007/04),
> > not the namespace of the type (http://APASProxy.DataTypes/2007/04).
> > The type doesn't determine the name of the element, only its
> content
> > model.
> > 
> > If you are still not convinced, think about the following element
> > declaration:
> > 
> >   
> >
> > 
> >  
> > 
> >
> >   
> > 
> > According to your reasoning, the element b should have namespace
> > http://www.w3.org/2001/XMLSchema. This is definitely not true.
> > 
> > Andreas
> > 
> > On Wed, May 13, 2009 at 00:38, Trenton D. Adams
> 
> > wrote:
> > > Hi Andrea,
> > >
> > > This is really confusing.  How can GetHostInstitutionResult not
> > depend on it's type?  If it doesn't depend on it's type, then why
> have
> > a "type"?
> > >
> > > As far as I can tell, elementFormDefault="qualified" doesn't
> imply
> > anything about having the same namespace af the parent.  All it
> tells
> > parsers and validators, is that if you set it to "qualified" then
> all
> > of your XML elements in a document, related to that schema, MUST be
> > prefixed with a namespace prefix.
> > >
> > > From w3c schools...
> > > --QUOTE--
> > > This fragment:
> > > elementFormDefault="qualified"
> > >
> > > indicates that any elements used by the XML instance document
> which
> > were declared in this schema must be namespace qualified.
> > > --QUOTE--
> > >
> > > I have tested this locally with perl validation, and it is
> correct.
> >  If I have formElementDefault="qualified", then this is invalid and
> > fails the xml validation...
> > >
> > > 
> > > 
> > > 
> > > 
> > >
> > > But this is correct, and would succeed on xml validation...
> > > 
> > > 
> > > 
> > > 
> > >
> > > The qualification setting has nothing to do with what you said
> "it
> > must have the namespace of the schema in which it is declared".
>  The
> > GetHostInstitutionResult type was declared in a different schema,
> and
> > that is the namespace that it should have.  So, the XML returned by
> > the service is indeed correct, but the stub code generated is
> > incorrect.  It should be qualifying it, which it is, but with the
> > "type" that the element was declared with in the WSDL.
> > >
> > > I hope that makes some sense.
> > >
> > > Thanks.
> > >
> > > Trenton D. Adams
> > > Systems Analyst/Web Software Engineer
> > > Navy Penguins at your service!
> > > Athabasca University
> > > (780) 675-6195
> > > :wq!
> > >
> > > - "Andreas Veithen"  wrote:
> > >
> > >> From: "Andreas Veithen" 
> > >> To: "

Re: axis 2 unexpected Subelement (BUG???)

Thanks Andreas, I think I get it now.  Right, element b is in fact the same 
namespace of a, just the contents are of a different namespace.  Right?

Trenton D. Adams
Systems Analyst/Web Software Engineer
Navy Penguins at your service!
Athabasca University
(780) 675-6195
:wq!

- "Andreas Veithen"  wrote:

> From: "Andreas Veithen" 
> To: "Trenton D. Adams" 
> Cc: axis-user@ws.apache.org
> Sent: Tuesday, May 12, 2009 5:00:23 PM GMT -07:00 US/Canada Mountain
> Subject: Re: axis 2 unexpected Subelement (BUG???)
>
> --QUOTE--
> This fragment:
> elementFormDefault="qualified"
> 
> indicates that any elements used by the XML instance document which
> were declared in this schema must be namespace qualified.
> --QUOTE--
> 
> ... and the namespace is the targetNamespace of the schema where the
> element has been declared
> (http://APASProxy.ServiceContracts/2007/04),
> not the namespace of the type (http://APASProxy.DataTypes/2007/04).
> The type doesn't determine the name of the element, only its content
> model.
> 
> If you are still not convinced, think about the following element
> declaration:
> 
>   
>
> 
>  
> 
>
>   
> 
> According to your reasoning, the element b should have namespace
> http://www.w3.org/2001/XMLSchema. This is definitely not true.
> 
> Andreas
> 
> On Wed, May 13, 2009 at 00:38, Trenton D. Adams 
> wrote:
> > Hi Andrea,
> >
> > This is really confusing.  How can GetHostInstitutionResult not
> depend on it's type?  If it doesn't depend on it's type, then why have
> a "type"?
> >
> > As far as I can tell, elementFormDefault="qualified" doesn't imply
> anything about having the same namespace af the parent.  All it tells
> parsers and validators, is that if you set it to "qualified" then all
> of your XML elements in a document, related to that schema, MUST be
> prefixed with a namespace prefix.
> >
> > From w3c schools...
> > --QUOTE--
> > This fragment:
> > elementFormDefault="qualified"
> >
> > indicates that any elements used by the XML instance document which
> were declared in this schema must be namespace qualified.
> > --QUOTE--
> >
> > I have tested this locally with perl validation, and it is correct.
>  If I have formElementDefault="qualified", then this is invalid and
> fails the xml validation...
> >
> > 
> > 
> > 
> > 
> >
> > But this is correct, and would succeed on xml validation...
> > 
> > 
> > 
> > 
> >
> > The qualification setting has nothing to do with what you said "it
> must have the namespace of the schema in which it is declared".  The
> GetHostInstitutionResult type was declared in a different schema, and
> that is the namespace that it should have.  So, the XML returned by
> the service is indeed correct, but the stub code generated is
> incorrect.  It should be qualifying it, which it is, but with the
> "type" that the element was declared with in the WSDL.
> >
> > I hope that makes some sense.
> >
> > Thanks.
> >
> > Trenton D. Adams
> > Systems Analyst/Web Software Engineer
> > Navy Penguins at your service!
> > Athabasca University
> > (780) 675-6195
> > :wq!
> >
> > - "Andreas Veithen"  wrote:
> >
> >> From: "Andreas Veithen" 
> >> To: "Trenton D. Adams" 
> >> Cc: axis-user@ws.apache.org
> >> Sent: Tuesday, May 12, 2009 12:39:34 PM GMT -07:00 US/Canada
> Mountain
> >> Subject: Re: axis 2 unexpected Subelement (BUG???)
> >>
> >> The namespace of GetHostInstitutionResult doesn't depend on its
> type.
> >> Since it appears in a sequence and elementFormDefault="qualified",
> it
> >> must have the namespace of the schema in which it is declared,
> i.e.
> >> "http://APASProxy.ServiceContracts/2007/04";, exactly as the
> generated
> >> code expects it.
> >>
> >> Andreas
> >>
> >> On Tue, May 12, 2009 at 20:29, Trenton D. Adams
> 
> >> wrote:
> >> > Okay, thanks Andreas.  I'm not sure I understand completely.
>  The
> >> GetHostInstitutionResult is supposed to be of the schema type
> >> "http://APASProxy.DataTypes/2007/04";, no???
> >> >
> >> > Anyhow, here's the items you mentioned...
> >> >  
> >> >   >> targetNamespace="http://APASProxy.ServiceContracts/20

activemq 1.5.1 requires java 1.5

Hi Guys,

I downloaded the source code for axis2, and while building, I noticed that it 
downloaded activemq 1.5.1.  That version requires java 1.5, but the axis2 is 
supposed to require only java 1.4.2.

Perhaps a version restriction needs to be made in the pom.xml?  I'm not able to 
tell what dependency is pulling activemq in.



Trenton D. Adams
Systems Analyst/Web Software Engineer
Navy Penguins at your service!
Athabasca University
(780) 675-6195
:wq!

__ 
This communication is intended for the use of the recipient to whom it
is addressed, and may contain confidential, personal, and or privileged
information. Please contact us immediately if you are not the intended
recipient of this communication, and do not copy, distribute, or take
action relying on it. Any communications received in error, or
subsequent reply, should be deleted or destroyed.
---

Re: axis 2 unexpected Subelement (BUG???)

By the way, just a reminder, I am a beginner in schemas and such.  So I very 
well might not have a clue. hehe

Trenton D. Adams
Systems Analyst/Web Software Engineer
Navy Penguins at your service!
Athabasca University
(780) 675-6195
:wq!

- "Trenton D. Adams"  wrote:

> From: "Trenton D. Adams" 
> To: "Andreas Veithen" 
> Cc: axis-user@ws.apache.org
> Sent: Tuesday, May 12, 2009 4:38:49 PM GMT -07:00 US/Canada Mountain
> Subject: Re: axis 2 unexpected Subelement (BUG???)
>
> Hi Andrea,
> 
> This is really confusing.  How can GetHostInstitutionResult not depend
> on it's type?  If it doesn't depend on it's type, then why have a
> "type"?
> 
> As far as I can tell, elementFormDefault="qualified" doesn't imply
> anything about having the same namespace af the parent.  All it tells
> parsers and validators, is that if you set it to "qualified" then all
> of your XML elements in a document, related to that schema, MUST be
> prefixed with a namespace prefix.
> 
> From w3c schools...
> --QUOTE--
> This fragment:
> elementFormDefault="qualified"
> 
> indicates that any elements used by the XML instance document which
> were declared in this schema must be namespace qualified.
> --QUOTE--
> 
> I have tested this locally with perl validation, and it is correct. 
> If I have formElementDefault="qualified", then this is invalid and
> fails the xml validation...
> 
> 
> 
> 
> 
> 
> But this is correct, and would succeed on xml validation...
> 
> 
> 
> 
> 
> The qualification setting has nothing to do with what you said "it
> must have the namespace of the schema in which it is declared".  The
> GetHostInstitutionResult type was declared in a different schema, and
> that is the namespace that it should have.  So, the XML returned by
> the service is indeed correct, but the stub code generated is
> incorrect.  It should be qualifying it, which it is, but with the
> "type" that the element was declared with in the WSDL.
> 
> I hope that makes some sense.
> 
> Thanks.
> 
> Trenton D. Adams
> Systems Analyst/Web Software Engineer
> Navy Penguins at your service!
> Athabasca University
> (780) 675-6195
> :wq!
> 
> - "Andreas Veithen"  wrote:
> 
> > From: "Andreas Veithen" 
> > To: "Trenton D. Adams" 
> > Cc: axis-user@ws.apache.org
> > Sent: Tuesday, May 12, 2009 12:39:34 PM GMT -07:00 US/Canada
> Mountain
> > Subject: Re: axis 2 unexpected Subelement (BUG???)
> >
> > The namespace of GetHostInstitutionResult doesn't depend on its
> type.
> > Since it appears in a sequence and elementFormDefault="qualified",
> it
> > must have the namespace of the schema in which it is declared, i.e.
> > "http://APASProxy.ServiceContracts/2007/04";, exactly as the
> generated
> > code expects it.
> > 
> > Andreas
> > 
> > On Tue, May 12, 2009 at 20:29, Trenton D. Adams
> 
> > wrote:
> > > Okay, thanks Andreas.  I'm not sure I understand completely.  The
> > GetHostInstitutionResult is supposed to be of the schema type
> > "http://APASProxy.DataTypes/2007/04";, no???
> > >
> > > Anyhow, here's the items you mentioned...
> > >  
> > >   > targetNamespace="http://APASProxy.ServiceContracts/2007/04";
> > xmlns="http://www.w3.org/2001/XMLSchema";>
> > >
> > > If the WSDL is wrong, I'm then wondering if this was an axis1
> bug,
> > as according to the wsdl comment, it was generated by axis 1.4.
> > >
> > > Thanks.
> > >
> > > Trenton D. Adams
> > > Systems Analyst/Web Software Engineer
> > > Navy Penguins at your service!
> > > Athabasca University
> > > (780) 675-6195
> > > :wq!
> > >
> > > - "Andreas Veithen"  wrote:
> > >
> > >> From: "Andreas Veithen" 
> > >> To: axis-user@ws.apache.org, "Trenton D. Adams"
> > 
> > >> Sent: Tuesday, May 12, 2009 12:07:21 PM GMT -07:00 US/Canada
> > Mountain
> > >> Subject: Re: axis 2 unexpected Subelement (BUG???)
> > >>
> > >> It is not. The fact that GetHostInstitutionResult is of type
> > >> tns1:RegisteredEducationalInstitution doesn't tell anything
> about
> > the
> > >> namespace of GetHostInstitutionResult. This depends on the
> > >> targetNamespace and elementFormDefault of the schema

Re: axis 2 unexpected Subelement (BUG???)

Hi Andrea,

This is really confusing.  How can GetHostInstitutionResult not depend on it's 
type?  If it doesn't depend on it's type, then why have a "type"?

As far as I can tell, elementFormDefault="qualified" doesn't imply anything 
about having the same namespace af the parent.  All it tells parsers and 
validators, is that if you set it to "qualified" then all of your XML elements 
in a document, related to that schema, MUST be prefixed with a namespace prefix.

From w3c schools...
--QUOTE--
This fragment:
elementFormDefault="qualified"

indicates that any elements used by the XML instance document which were 
declared in this schema must be namespace qualified.
--QUOTE--

I have tested this locally with perl validation, and it is correct.  If I have 
formElementDefault="qualified", then this is invalid and fails the xml 
validation...






But this is correct, and would succeed on xml validation...





The qualification setting has nothing to do with what you said "it must have 
the namespace of the schema in which it is declared".  The 
GetHostInstitutionResult type was declared in a different schema, and that is 
the namespace that it should have.  So, the XML returned by the service is 
indeed correct, but the stub code generated is incorrect.  It should be 
qualifying it, which it is, but with the "type" that the element was declared 
with in the WSDL.

I hope that makes some sense.

Thanks.

Trenton D. Adams
Systems Analyst/Web Software Engineer
Navy Penguins at your service!
Athabasca University
(780) 675-6195
:wq!

- "Andreas Veithen"  wrote:

> From: "Andreas Veithen" 
> To: "Trenton D. Adams" 
> Cc: axis-user@ws.apache.org
> Sent: Tuesday, May 12, 2009 12:39:34 PM GMT -07:00 US/Canada Mountain
> Subject: Re: axis 2 unexpected Subelement (BUG???)
>
> The namespace of GetHostInstitutionResult doesn't depend on its type.
> Since it appears in a sequence and elementFormDefault="qualified", it
> must have the namespace of the schema in which it is declared, i.e.
> "http://APASProxy.ServiceContracts/2007/04";, exactly as the generated
> code expects it.
> 
> Andreas
> 
> On Tue, May 12, 2009 at 20:29, Trenton D. Adams 
> wrote:
> > Okay, thanks Andreas.  I'm not sure I understand completely.  The
> GetHostInstitutionResult is supposed to be of the schema type
> "http://APASProxy.DataTypes/2007/04";, no???
> >
> > Anyhow, here's the items you mentioned...
> >  
> >   targetNamespace="http://APASProxy.ServiceContracts/2007/04";
> xmlns="http://www.w3.org/2001/XMLSchema";>
> >
> > If the WSDL is wrong, I'm then wondering if this was an axis1 bug,
> as according to the wsdl comment, it was generated by axis 1.4.
> >
> > Thanks.
> >
> > Trenton D. Adams
> > Systems Analyst/Web Software Engineer
> > Navy Penguins at your service!
> > Athabasca University
> > (780) 675-6195
> > :wq!
> >
> > - "Andreas Veithen"  wrote:
> >
> >> From: "Andreas Veithen" 
> >> To: axis-user@ws.apache.org, "Trenton D. Adams"
> 
> >> Sent: Tuesday, May 12, 2009 12:07:21 PM GMT -07:00 US/Canada
> Mountain
> >> Subject: Re: axis 2 unexpected Subelement (BUG???)
> >>
> >> It is not. The fact that GetHostInstitutionResult is of type
> >> tns1:RegisteredEducationalInstitution doesn't tell anything about
> the
> >> namespace of GetHostInstitutionResult. This depends on the
> >> targetNamespace and elementFormDefault of the schema, which you
> don't
> >> show in your post.
> >>
> >> Andreas
> >>
> >> On Tue, May 12, 2009 at 19:55, Trenton D. Adams
> 
> >> wrote:
> >> > Okay, I figured out what is happening.  Is this an axis bug?
> >> >
> >> > It is putting the incorrect schema into the stub code...
> >> >                                    if (reader.isStartElement()
> &&
> >> new
> >>
> javax.xml.namespace.QName("http://APASProxy.ServiceContracts/2007/04","GetHostInstitutionResult";).equals(reader.getName())){
> >> >
> >> >
> >>
>  object.setGetHostInstitutionResult(RegisteredEducationalInstitution.Factory.parse(reader));
> >> >
> >> >                                        reader.next();
> >> >
> >> >                              }  // End of if for expected
> property
> >> start element
> >> >
> >> >                                    else {
> >> >
> >> >                                    }
> >> >
> >> > That "ServiceContracts" should read "DataTypes".  The wsdl says
> >> this...
> >> > 
> >> >  >> targetNamespace="http://APASProxy.ServiceContracts/2007/04";
> >> xmlns:apachesoap="http://xml.apache.org/xml-soap";
> >> xmlns:impl="http://APASProxy.ServiceContracts/2007/04";
> >> xmlns:intf="http://APASProxy.ServiceContracts/2007/04";
> >> xmlns:tns1="http://APASProxy.DataTypes/2007/04";
> >> xmlns:tns2="http://_04._2007.APASProxy.DataTypes";
> >> xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
> >> xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/";
> >> xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
> >> >  >> >
> >

Re: axis 2 unexpected Subelement (BUG???)

Translation: are you saying that there is a discrepancy between what the WSDL 
claims, and what the SOAP service is actually offering as a response then?

How might something like that occur, with say axis1?  After all, the WSDL is 
apparently automatically generated.  So you would think that it would do it 
correctly.  But, this wsdl2java stuff doesn't work for this service on axis1 or 
axis2.

Any pointers would be appreciated.  I don't know much about axis yet, and if 
you could save me some grunt work on where to look, that would be VERY 
appreciated.

Thanks.

Trenton D. Adams
Systems Analyst/Web Software Engineer
Navy Penguins at your service!
Athabasca University
(780) 675-6195
:wq!

- "Andreas Veithen"  wrote:

> From: "Andreas Veithen" 
> To: "Trenton D. Adams" 
> Cc: axis-user@ws.apache.org
> Sent: Tuesday, May 12, 2009 12:39:34 PM GMT -07:00 US/Canada Mountain
> Subject: Re: axis 2 unexpected Subelement (BUG???)
>
> The namespace of GetHostInstitutionResult doesn't depend on its type.
> Since it appears in a sequence and elementFormDefault="qualified", it
> must have the namespace of the schema in which it is declared, i.e.
> "http://APASProxy.ServiceContracts/2007/04";, exactly as the generated
> code expects it.
> 
> Andreas
> 
> On Tue, May 12, 2009 at 20:29, Trenton D. Adams 
> wrote:
> > Okay, thanks Andreas.  I'm not sure I understand completely.  The
> GetHostInstitutionResult is supposed to be of the schema type
> "http://APASProxy.DataTypes/2007/04";, no???
> >
> > Anyhow, here's the items you mentioned...
> >  
> >   targetNamespace="http://APASProxy.ServiceContracts/2007/04";
> xmlns="http://www.w3.org/2001/XMLSchema";>
> >
> > If the WSDL is wrong, I'm then wondering if this was an axis1 bug,
> as according to the wsdl comment, it was generated by axis 1.4.
> >
> > Thanks.
> >
> > Trenton D. Adams
> > Systems Analyst/Web Software Engineer
> > Navy Penguins at your service!
> > Athabasca University
> > (780) 675-6195
> > :wq!
> >
> > - "Andreas Veithen"  wrote:
> >
> >> From: "Andreas Veithen" 
> >> To: axis-user@ws.apache.org, "Trenton D. Adams"
> 
> >> Sent: Tuesday, May 12, 2009 12:07:21 PM GMT -07:00 US/Canada
> Mountain
> >> Subject: Re: axis 2 unexpected Subelement (BUG???)
> >>
> >> It is not. The fact that GetHostInstitutionResult is of type
> >> tns1:RegisteredEducationalInstitution doesn't tell anything about
> the
> >> namespace of GetHostInstitutionResult. This depends on the
> >> targetNamespace and elementFormDefault of the schema, which you
> don't
> >> show in your post.
> >>
> >> Andreas
> >>
> >> On Tue, May 12, 2009 at 19:55, Trenton D. Adams
> 
> >> wrote:
> >> > Okay, I figured out what is happening.  Is this an axis bug?
> >> >
> >> > It is putting the incorrect schema into the stub code...
> >> >                                    if (reader.isStartElement()
> &&
> >> new
> >>
> javax.xml.namespace.QName("http://APASProxy.ServiceContracts/2007/04","GetHostInstitutionResult";).equals(reader.getName())){
> >> >
> >> >
> >>
>  object.setGetHostInstitutionResult(RegisteredEducationalInstitution.Factory.parse(reader));
> >> >
> >> >                                        reader.next();
> >> >
> >> >                              }  // End of if for expected
> property
> >> start element
> >> >
> >> >                                    else {
> >> >
> >> >                                    }
> >> >
> >> > That "ServiceContracts" should read "DataTypes".  The wsdl says
> >> this...
> >> > 
> >> >  >> targetNamespace="http://APASProxy.ServiceContracts/2007/04";
> >> xmlns:apachesoap="http://xml.apache.org/xml-soap";
> >> xmlns:impl="http://APASProxy.ServiceContracts/2007/04";
> >> xmlns:intf="http://APASProxy.ServiceContracts/2007/04";
> >> xmlns:tns1="http://APASProxy.DataTypes/2007/04";
> >> xmlns:tns2="http://_04._2007.APASProxy.DataTypes";
> >> xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
> >> xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/";
> >> xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
> >> >  >> >
> >

Re: axis 2 unexpected Subelement (BUG???)

Okay, thanks Andreas.  I'm not sure I understand completely.  The 
GetHostInstitutionResult is supposed to be of the schema type 
"http://APASProxy.DataTypes/2007/04";, no???

Anyhow, here's the items you mentioned...
 
  http://APASProxy.ServiceContracts/2007/04"; 
xmlns="http://www.w3.org/2001/XMLSchema";>

If the WSDL is wrong, I'm then wondering if this was an axis1 bug, as according 
to the wsdl comment, it was generated by axis 1.4.

Thanks.

Trenton D. Adams
Systems Analyst/Web Software Engineer
Navy Penguins at your service!
Athabasca University
(780) 675-6195
:wq!

- "Andreas Veithen"  wrote:

> From: "Andreas Veithen" 
> To: axis-user@ws.apache.org, "Trenton D. Adams" 
> Sent: Tuesday, May 12, 2009 12:07:21 PM GMT -07:00 US/Canada Mountain
> Subject: Re: axis 2 unexpected Subelement (BUG???)
>
> It is not. The fact that GetHostInstitutionResult is of type
> tns1:RegisteredEducationalInstitution doesn't tell anything about the
> namespace of GetHostInstitutionResult. This depends on the
> targetNamespace and elementFormDefault of the schema, which you don't
> show in your post.
> 
> Andreas
> 
> On Tue, May 12, 2009 at 19:55, Trenton D. Adams 
> wrote:
> > Okay, I figured out what is happening.  Is this an axis bug?
> >
> > It is putting the incorrect schema into the stub code...
> >                                    if (reader.isStartElement() &&
> new
> javax.xml.namespace.QName("http://APASProxy.ServiceContracts/2007/04","GetHostInstitutionResult";).equals(reader.getName())){
> >
> >                                              
>  object.setGetHostInstitutionResult(RegisteredEducationalInstitution.Factory.parse(reader));
> >
> >                                        reader.next();
> >
> >                              }  // End of if for expected property
> start element
> >
> >                                    else {
> >
> >                                    }
> >
> > That "ServiceContracts" should read "DataTypes".  The wsdl says
> this...
> > 
> >  targetNamespace="http://APASProxy.ServiceContracts/2007/04";
> xmlns:apachesoap="http://xml.apache.org/xml-soap";
> xmlns:impl="http://APASProxy.ServiceContracts/2007/04";
> xmlns:intf="http://APASProxy.ServiceContracts/2007/04";
> xmlns:tns1="http://APASProxy.DataTypes/2007/04";
> xmlns:tns2="http://_04._2007.APASProxy.DataTypes";
> xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
> xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
> >  >

Re: axis 2 unexpected Subelement (BUG???)

Okay, I figured out what is happening.  Is this an axis bug?

It is putting the incorrect schema into the stub code...
if (reader.isStartElement() && new 
javax.xml.namespace.QName("http://APASProxy.ServiceContracts/2007/04","GetHostInstitutionResult";).equals(reader.getName())){


object.setGetHostInstitutionResult(RegisteredEducationalInstitution.Factory.parse(reader));
  
reader.next();

  }  // End of if for expected property start 
element

else {

}
  
That "ServiceContracts" should read "DataTypes".  The wsdl says this...

http://APASProxy.ServiceContracts/2007/04"; 
xmlns:apachesoap="http://xml.apache.org/xml-soap"; 
xmlns:impl="http://APASProxy.ServiceContracts/2007/04"; 
xmlns:intf="http://APASProxy.ServiceContracts/2007/04"; 
xmlns:tns1="http://APASProxy.DataTypes/2007/04"; 
xmlns:tns2="http://_04._2007.APASProxy.DataTypes"; 
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; 
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"; 
xmlns:xsd="http://www.w3.org/2001/XMLSchema";>

Re: axis 2 unexpected Subelement

Oops, I was wrong, it wasn't the code below failing, it was the second attempt 
using the wsdl2java classes that failed...

final APASQueueServiceStub service;
service = new APASQueueServiceStub();
APASQueueServiceStub.GetHostInstitution hostInst;
hostInst = new APASQueueServiceStub.GetHostInstitution();
APASQueueServiceStub.GetHostInstitutionResponse resp = 
service.GetHostInstitution(hostInst);
System.out.println("Institution: " +

resp.getGetHostInstitutionResult().getEducationalInstitutionName());

I can post the WSDL if you like.

Trenton D. Adams
Systems Analyst/Web Software Engineer
Navy Penguins at your service!
Athabasca University
(780) 675-6195
:wq!

- "Trenton D. Adams"  wrote:

> From: "Trenton D. Adams" 
> To: "axis-user" 
> Sent: Tuesday, May 12, 2009 9:49:05 AM GMT -07:00 US/Canada Mountain
> Subject: axis 2 unexpected Subelement
>
> Hi Guys,
> 
> I can't figure out why I'm getting this error; is there something
> wrong with the service's XML output?
> 
> ServiceClient client;
> client = new ServiceClient();
> Options options = new Options();
> options.setTo(new
> EndpointReference("https://apasproxy.athabascau.ca/axis/services/APASQueueService";));
> client.setOptions(options);
> OMElement request;
> OMFactory factory;
> factory = OMAbstractFactory.getOMFactory();
> request = factory.createOMElement(new
> QName("http://APASProxy.DataTypes/2007/04/";, "GetHostInstitution"));
> OMElement response;
> response = client.sendReceive(request);
> System.out.println(response.toString());
> 
>  xmlns="http://APASProxy.DataTypes/2007/04/";> xmlns:ns1="http://APASProxy.DataTypes/2007/04";>48002000Athabasca
> University
> org.apache.axis2.AxisFault: org.apache.axis2.databinding.ADBException:
> Unexpected subelement GetHostInstitutionResult
>   at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
>   at
> servicecontracts.apasproxy._2007._04.APASQueueServiceStub.fromOM(APASQueueServiceStub.java:35302)
>   at
> servicecontracts.apasproxy._2007._04.APASQueueServiceStub.GetHostInstitution(APASQueueServiceStub.java:2467)
>   at ca.athabascau.apas.APAS.main(APAS.java:70)
>   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:597)
>   at
> com.intellij.rt.execution.application.AppMain.main(AppMain.java:90)
> Caused by: java.lang.Exception:
> org.apache.axis2.databinding.ADBException: Unexpected subelement
> GetHostInstitutionResult
>   at
> servicecontracts.apasproxy._2007._04.APASQueueServiceStub$GetHostInstitutionResponse$Factory.parse(APASQueueServiceStub.java:12645)
>   at
> servicecontracts.apasproxy._2007._04.APASQueueServiceStub.fromOM(APASQueueServiceStub.java:35226)
>   ... 7 more
> Caused by: org.apache.axis2.databinding.ADBException: Unexpected
> subelement GetHostInstitutionResult
>   at
> servicecontracts.apasproxy._2007._04.APASQueueServiceStub$GetHostInstitutionResponse$Factory.parse(APASQueueServiceStub.java:12639)
>   ... 8 more
> 
> Process finished with exit code 0
> 
> 
> 
> Trenton D. Adams
> Systems Analyst/Web Software Engineer
> Navy Penguins at your service!
> Athabasca University
> (780) 675-6195
> :wq!
> 
> __ 
> This communication is intended for the use of the recipient to
> whom it
> is addressed, and may contain confidential, personal, and or
> privileged
> information. Please contact us immediately if you are not the
> intended
> recipient of this communication, and do not copy, distribute, or
> take
> action relying on it. Any communications received in error, or
> subsequent reply, should be deleted or destroyed.
> ---

axis 2 unexpected Subelement

Hi Guys,

I can't figure out why I'm getting this error; is there something wrong with 
the service's XML output?

ServiceClient client;
client = new ServiceClient();
Options options = new Options();
options.setTo(new 
EndpointReference("https://apasproxy.athabascau.ca/axis/services/APASQueueService";));
client.setOptions(options);
OMElement request;
OMFactory factory;
factory = OMAbstractFactory.getOMFactory();
request = factory.createOMElement(new 
QName("http://APASProxy.DataTypes/2007/04/";, "GetHostInstitution"));
OMElement response;
response = client.sendReceive(request);
System.out.println(response.toString());

http://APASProxy.DataTypes/2007/04/";>http://APASProxy.DataTypes/2007/04";>48002000Athabasca
 
University
org.apache.axis2.AxisFault: org.apache.axis2.databinding.ADBException: 
Unexpected subelement GetHostInstitutionResult
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
at 
servicecontracts.apasproxy._2007._04.APASQueueServiceStub.fromOM(APASQueueServiceStub.java:35302)
at 
servicecontracts.apasproxy._2007._04.APASQueueServiceStub.GetHostInstitution(APASQueueServiceStub.java:2467)
at ca.athabascau.apas.APAS.main(APAS.java:70)
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:597)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:90)
Caused by: java.lang.Exception: org.apache.axis2.databinding.ADBException: 
Unexpected subelement GetHostInstitutionResult
at 
servicecontracts.apasproxy._2007._04.APASQueueServiceStub$GetHostInstitutionResponse$Factory.parse(APASQueueServiceStub.java:12645)
at 
servicecontracts.apasproxy._2007._04.APASQueueServiceStub.fromOM(APASQueueServiceStub.java:35226)
... 7 more
Caused by: org.apache.axis2.databinding.ADBException: Unexpected subelement 
GetHostInstitutionResult
at 
servicecontracts.apasproxy._2007._04.APASQueueServiceStub$GetHostInstitutionResponse$Factory.parse(APASQueueServiceStub.java:12639)
    ... 8 more

Process finished with exit code 0



Trenton D. Adams
Systems Analyst/Web Software Engineer
Navy Penguins at your service!
Athabasca University
(780) 675-6195
:wq!

__ 
This communication is intended for the use of the recipient to whom it
is addressed, and may contain confidential, personal, and or privileged
information. Please contact us immediately if you are not the intended
recipient of this communication, and do not copy, distribute, or take
action relying on it. Any communications received in error, or
subsequent reply, should be deleted or destroyed.
---

WSDL2Java and manual soap calls not working

2009-05-08 Thread Trenton D. Adams

Hi Guys,

I'm a newbie, and I'm using axis-1.4.  I have a web service that I am 
connecting to, which I did not write, which was written using axis-1.4.  I am 
having problems using the WSDL2Java generated files, as well as using the soap 
call api.  Neither appear to work as expected.

I'm almost at my wits end, and feel like doing a manual call using 
HttpsURLConnection.  But boy would it be nice to be able to use the WSDL2Java 
generated classes, or at the very least, use the axis-SOAP api to make the call.

In both cases, I am getting proper XML responses.  I can tell, because I step 
through the code, and the soap response has the same XML that I would get if I 
did the request manually.

1. WSDL2Java does not generate code that is able to access the soap service I 
am accessing; I get an error that says...
org.xml.sax.SAXException: Invalid element in 
DataTypes.APASProxy._2007._04.ReceivedTranscript - ReceivedTranscript

The code was generated from the wsdl from the service directly.  i.e. 
http://localhost/axis/service/ServiceName?wsdl

I have no idea where to start.  Simple requests that take no parameters, and 
return strings, work just fine.  But when it's a complex return value, such as 
an array, it doesn't appear to work, AT ALL.  Here's an example of one that 
fails for me; which I do manually here to show that it works fine without the 
WSDL generated classes.


openssl s_client -connect hostname:443

POST /axis/services/APASQueueService HTTP/1.0
Content-Type: text/xml; charset=utf-8
Accept: application/soap+xml, application/dime, multipart/related, text/*
User-Agent: Axis/1.4
Host: apasproxy.athabascau.ca
Cache-Control: no-cache
Pragma: no-cache
SOAPAction: 
"http://APASProxy.ServiceContracts/2007/04/GetRegisteredEducationalInstitutions";
Content-Length: 351

http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:xsd="http://www.w3.org/200
1/XMLSchema" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>http://APASProxy.ServiceContracts/2007/04"/>

http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>http://APASProxy.ServiceContracts/2007/04";>http://APASProxy.DataTypes/2007/04";>48024000
..blah, blah, blah, yada, yada, yada.
closed

2. I am unable to make an axis Call connection either; I keep getting an error 
that says
org.xml.sax.SAXException: SimpleDeserializer encountered a child element, which 
is NOT expected, in something it was trying to deserialize.

The above one, is the "simple" request I mentioned earlier.  Just a string 
retrieval.

Here's an example of the java code...
Service soapService = new Service();
Call call = (Call) soapService.createCall();
call.setTargetEndpointAddress(
  new java.net.URL
  ("https://hostname/axis/services/APASQueueService";));
call.setOperationName(
  new QName("", "GetHostInstitution"));
call.setReturnType(XMLType.XSD_STRING);   // this is not working
try {
  System.out.println(call.invoke(
new Object[] { }));
} catch (java.rmi.RemoteException re) {
  re.printStackTrace();
}

Here's an example from doing it manually.  If I step through the code, it is 
getting the same response, but is unable to handle it.  Try to ignore any 
wrapping that occurs, as I'm sure my mail client will wrap some of it.

openssl s_client -connect hostname:443

POST /axis/services/APASQueueService HTTP/1.0
Content-Type: text/xml; charset=utf-8
Accept: application/soap+xml, application/dime, multipart/related, text/*
User-Agent: Axis/1.4
Host: hostname
Cache-Control: no-cache
Pragma: no-cache
SOAPAction: "http://APASProxy.ServiceContracts/2007/04/GetHostInstitution";
Content-Length: 333

http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:xsd="http://www.w3.org/200
1/XMLSchema" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>http://APASProxy.ServiceContracts/2007/04"/>
HTTP/1.1 200 OK
Date: Fri, 08 May 2009 15:40:34 GMT
Content-Type: text/xml;charset=utf-8
Connection: close

http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>http://APASProxy.ServiceContracts/2007/04";>http://APASProxy.DataTypes/2007/04";>48002000Athabasca
 
Universityclosed

Trenton D. Adams
Systems Analyst/Web Software Engineer
Navy Penguins at your service!
Athabasca University
(780) 675-6195
:wq!

__ 
This communication is intended for the use of the recipient to whom it
is addressed, and may contain confidential, personal, and or privileged
information. Please contact us immediately if you are not the intended
recipient of this communication, and do not copy, distribute, or take
action relying on it. Any communications received in error, or
subsequent reply, should be deleted or destroyed.
---

The org.apache.axis2.jaxws.message.databinding.impl.JAXBBlockImpl block object is already consumed.

2009-04-20 Thread Marvin D. Toll


Environment:  WebSphere Platform 6.1 [BASE 6.1.0.21 cf210844.13] [WEBSERVICES
6.1.0.21 cf210844.03]
Topic: Retrieving the SOAP Message.

The SOAPMessageContext can be retrieved in one of two ways:

Handler
  public boolean handleMessage(SOAPMessageContext
soapMessageContext)
EndPoint
@Resource
  private WebServiceContext webServiceContext;
  // webServiceContext.getMessageContext();

If there is no inbound payload the SOAPMessage may be retrieved as follows
using either strategy:

SOAPMessage soapMessage = soapMessageContext.getMessage();

However, if there is an inbound payload the @Resource strategy yields the
following when retrieving the SOAP message:

Caused by: javax.xml.ws.WebServiceException: An internal error occurred. The
org.apache.axis2.jaxws.message.databinding.impl.JAXBBlockImpl block object
is already consumed. Processing cannot continue.  Run with the debug option
to determine where the block was first consumed.
at
org.apache.axis2.jaxws.ExceptionFactory.createWebServiceException(ExceptionFactory.java:178)
at
org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(ExceptionFactory.java:79)
at
org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(ExceptionFactory.java:125)
at
org.apache.axis2.jaxws.message.impl.BlockImpl.outputTo(BlockImpl.java:376)
at
org.apache.axis2.jaxws.message.impl.BlockImpl.serialize(BlockImpl.java:309)
at
org.apache.axiom.om.impl.llom.OMSourcedElementImpl.internalSerialize(OMSourcedElementImpl.java:570)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:789)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:773)
at
org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize(SOAPEnvelopeImpl.java:247)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:773)
at 
org.apache.axiom.om.impl.llom.OMNodeImpl.serialize(OMNodeImpl.java:345)
at 
org.apache.axiom.om.impl.llom.OMNodeImpl.serialize(OMNodeImpl.java:389)
at
org.apache.axis2.jaxws.message.impl.MessageImpl.getAsSOAPMessage(MessageImpl.java:192)
at
org.apache.axis2.jaxws.handler.SoapMessageContext.getMessage(SoapMessageContext.java:111)
at
com.ford.it.wscore.context.WscBaseProviderOrchestrator.getSoapMessage(WscBaseProviderOrchestrator.java:564)
at
com.ford.it.wscore.context.WscBaseProviderOrchestrator.getSoapPart(WscBaseProviderOrchestrator.java:581)
at
com.ford.it.wscore.context.WscBaseProviderOrchestrator.parseXmlFromSoapPart(WscBaseProviderOrchestrator.java:748)
at
com.ford.it.wscore.context.WscBaseProviderOrchestrator.logRequest(WscBaseProviderOrchestrator.java:226)
... 37 more


Note: Only non-API Google hits on this exception are in reference to an
Axis2 unmarshaling bug resolved 4/2007.

Any ideas why we see different behavior depending on which strategy used to
retrieve the SOAP Message?

Thanks,
Marvin

-- 
View this message in context: 
http://www.nabble.com/The-org.apache.axis2.jaxws.message.databinding.impl.JAXBBlockImpl-block-object-is-already-consumed.-tp23138529p23138529.html
Sent from the Axis - User mailing list archive at Nabble.com.

RE: HI i am fresher for axis2 webservices

2008-09-24 Thread D . H . T . M . Gameren

Hi,

I have taken a look at your service and the problem is the way you build
your aar-file.

1.  the common structure is
META-INF   this contains services.xml + wsdl-file
libcontains extra jar's when needed.
Xx tree containing you class files.

2.  Your aar-file only contains sources no classes and no wsdl-file.

3.  i see you have created the service based on pojo's , 
I prefer creating classes based on a wsdl but that is a matter of
choice.

4.  I think you have to modify the class-names in you services.xml
aswell
(just an extra observation)


Good luck

Dirk







-Original Message-
From: yendam [mailto:[EMAIL PROTECTED] 
Sent: woensdag 24 september 2008 15:01
To: axis-user@ws.apache.org
Subject: RE: HI i am fresher for axis2 webservices




D.H.T.M.Gameren wrote:
> 
> 
> i am sending one project what i am doing it is showing errors
> please rectify where is that error is and send me working example war
file
> thanks
> or please send me any websrvice example which is already devoloped
> http://www.nabble.com/file/p19648228/WeatherService.rar
WeatherService.rar 
> 
> 
> 
> I guess you did not include your services.xml in your aar-file or not
at
> the right place.
> It should be in the META-INF
> 
> Regards
> Dirk
> 
> -Original Message-
> From: yendam [mailto:[EMAIL PROTECTED] 
> Sent: dinsdag 23 september 2008 12:37
> To: axis-user@ws.apache.org
> Subject: Re: HI i am fresher for axis2 webservices
> 
> 
> HI,Charitha
> 
> 
> i am creating axis2 webservices
> 
> 
> http://wso2.org/library/95
> 
> i made .aar file and doing using tomcat ..
> i have started tomcat and opened adminstration 
> 
> http://localhost:8080/axis2/axis2-admin/upload
> 
> using this i have uploaded .aar file but still i am getting errors 
> 
> when i click on faulty services
> 
> 
> Error: org.apache.axis2.deployment.DeploymentException: The
services.xml
> file cannot be found for the service: C:\Program Files\Apache Software
> Foundation\Tomcat 6.0\webapps\axis2\WEB-INF\services\SimpleService.aar
> at
>
org.apache.axis2.deployment.repository.util.ArchiveReader.processService
> Group(ArchiveReader.java:144)
> at
>
org.apache.axis2.deployment.ServiceDeployer.deploy(ServiceDeployer.java:
> 78)
> at
>
org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(De
> ploymentFileData.java:137)
> at
>
org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.j
> ava:571)
> at
>
org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList
> .java:141)
> at
>
org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener
> .java:318)
> at
>
org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryL
> istener.java:220)
> at
>
org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryL
> istener.java:312)
> at
>
org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(Sche
> dulerTask.java:64)
> at
>
org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.ja
> va:71)
> at
>
org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask.run(S
> cheduler.java:83)
> at java.util.TimerThread.mainLoop(Unknown Source) at
> java.util.TimerThread.run(Unknown Source) Caused by:
> org.apache.axis2.deployment.DeploymentException: The services.xml file
> cannot be found for the service: C:\Program Files\Apache Software
> Foundation\Tomcat 6.0\webapps\axis2\WEB-INF\services\SimpleService.aar
> at
>
org.apache.axis2.deployment.repository.util.ArchiveReader.processService
> Group(ArchiveReader.java:141)
> .. 12 more 
> 
> 
> 
> 
> please help me,,
> 
> Thanks
> Santosh.Y
> 
> 
> Charitha Kankanamge wrote:
>> 
>> Hi,
>> Can you please be more specific and tell us about the errors you 
>> encountered?
>> 
>> Regards
>> Charitha
>> 
>> http://charithaka.blogspot.com
>> 
>> yendam wrote:
>> 
>>> i am doing all the process in 
>>>
>
http://www.eclipse.org/webtools/community/tutorials/BottomUpAxis2WebServ
> ice/bu_tutorial.html 
>>> but i cant able to excute it...i am using eclipse europa and jdk1.6 
>>> and tomcat6.0... please help me
>>>
>

>>> View this message in context: HI i am fresher for axis2 webservices 
>>>
>
 19605463.html>
>>> Sent from the Axis - User mailing list archive 
>>>  at Nabble.com.
>>>
>>>-
-
> --
>>>
>>>No virus found in this incoming message.
>>>Checked by AVG. 
>>>Version: 7.5.524 / Virus Database: 270.7.0/1682 - Release Date:
> 9/20/2008
> 10:24 AM
>>>  
>>>
>> 
>> 
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>> 
>> 
>> 
> 
> -- 
> View this message in context:
>
http://www.nabble.com/HI

RE: HI i am fresher for axis2 webservices

2008-09-23 Thread D . H . T . M . Gameren

I guess you did not include your services.xml in your aar-file or not at
the right place.
It should be in the META-INF

Regards
Dirk

-Original Message-
From: yendam [mailto:[EMAIL PROTECTED] 
Sent: dinsdag 23 september 2008 12:37
To: axis-user@ws.apache.org
Subject: Re: HI i am fresher for axis2 webservices

HI,Charitha

i am creating axis2 webservices

http://wso2.org/library/95

i made .aar file and doing using tomcat ..
i have started tomcat and opened adminstration 

http://localhost:8080/axis2/axis2-admin/upload

using this i have uploaded .aar file but still i am getting errors 

when i click on faulty services

Error: org.apache.axis2.deployment.DeploymentException: The services.xml
file cannot be found for the service: C:\Program Files\Apache Software
Foundation\Tomcat 6.0\webapps\axis2\WEB-INF\services\SimpleService.aar
at
org.apache.axis2.deployment.repository.util.ArchiveReader.processService
Group(ArchiveReader.java:144)
at
org.apache.axis2.deployment.ServiceDeployer.deploy(ServiceDeployer.java:
78)
at
org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(De
ploymentFileData.java:137)
at
org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.j
ava:571)
at
org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList
.java:141)
at
org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener
.java:318)
at
org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryL
istener.java:220)
at
org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryL
istener.java:312)
at
org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(Sche
dulerTask.java:64)
at
org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.ja
va:71)
at
org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask.run(S
cheduler.java:83)
at java.util.TimerThread.mainLoop(Unknown Source) at
java.util.TimerThread.run(Unknown Source) Caused by:
org.apache.axis2.deployment.DeploymentException: The services.xml file
cannot be found for the service: C:\Program Files\Apache Software
Foundation\Tomcat 6.0\webapps\axis2\WEB-INF\services\SimpleService.aar
at
org.apache.axis2.deployment.repository.util.ArchiveReader.processService
Group(ArchiveReader.java:141)
.. 12 more 

please help me,,

Thanks
Santosh.Y

Charitha Kankanamge wrote:
> 
> Hi,
> Can you please be more specific and tell us about the errors you 
> encountered?
> 
> Regards
> Charitha
> 
> http://charithaka.blogspot.com
> 
> yendam wrote:
> 
>> i am doing all the process in 
>>
http://www.eclipse.org/webtools/community/tutorials/BottomUpAxis2WebServ
ice/bu_tutorial.html 
>> but i cant able to excute it...i am using eclipse europa and jdk1.6 
>> and tomcat6.0... please help me
>>

>> View this message in context: HI i am fresher for axis2 webservices 
>>

>> Sent from the Axis - User mailing list archive 
>>  at Nabble.com.
>>
>>--
--
>>
>>No virus found in this incoming message.
>>Checked by AVG. 
>>Version: 7.5.524 / Virus Database: 270.7.0/1682 - Release Date:
9/20/2008
10:24 AM
>>  
>>
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-- 
View this message in context:
http://www.nabble.com/HI-i-am-fresher-for-axis2-webservices-tp19605463p1
9625050.html
Sent from the Axis - User mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

==
The information transmitted via this e-mail is intended only for the person or
entity to which it is addressed and may contain confidential and/or privileged 
material.  Any review, retransmission, dissemination or other use of, or 
taking of any action in reliance upon this information by persons or entities 
other than the intended recipient is prohibited. If you received this in error, 
please contact the sender and delete the material from any computer.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Excluding admin functions from axis deployment.

2008-09-08 Thread Ramani, Yagnesh D.

Hello,

 

Our deployment in production required to remove all admin functions
start/stop/engage/disengage operation on web service. We want to just keep
the server start and stop as only operation to be done on the web service. Is
there any way we can achieve that?

 

Yagnesh

Re: difference in wsdl output between codegen and command line

2008-05-15 Thread D P

Hi Amila,

Thank you for your response.  Unfortunately, I compared the wsdl file
produced when including the -ap switch to output without the switch, and the
files are identical. Also could you please explain why you think this switch
should resolve my issue?  The docs indicate this switch operates on the port
types section, whereas my problem is that i'm not observing an expected soap
1.2 binding in the bindings section.

I hesitated posting a wsdl because of cleanup required to remove client
specific information, but if you think it'll help I'd be happy to give it a
shot.

On Tue, May 13, 2008 at 11:07 PM, Amila Suriarachchi <
[EMAIL PROTECTED]> wrote:

> use -ap
>
> thanks,
> Amila.
>
>
> On Tue, May 13, 2008 at 2:24 AM, D P <[EMAIL PROTECTED]> wrote:
>
>> Hello all:
>>
>> Eclipse 3.2.2 and Codegen Wizard 1.3 on WinXP
>> Axis1.3 on Redhat linux
>>
>> I noticed that the the wsdl output from the code gen wizard contains
>> bindings for both soap 1.1 and 1.2, but the wsdl output from the command
>> line tool does not. Is there a switch in the command line tool that allows
>> me to make the wsdl output match what the code gen wizard outputs, i.e.
>> bindings for both versions of soap?  I checked through all possible
>> switches, nothing appears to be what i need.
>>
>> TIA.
>>
>
>
>
> --
> Amila Suriarachchi,
> WSO2 Inc.

difference in wsdl output between codegen and command line

2008-05-12 Thread D P

Hello all:

Eclipse 3.2.2 and Codegen Wizard 1.3 on WinXP
Axis1.3 on Redhat linux

I noticed that the the wsdl output from the code gen wizard contains
bindings for both soap 1.1 and 1.2, but the wsdl output from the command
line tool does not. Is there a switch in the command line tool that allows
me to make the wsdl output match what the code gen wizard outputs, i.e.
bindings for both versions of soap?  I checked through all possible
switches, nothing appears to be what i need.

TIA.

RE: Capture custom exception

2008-03-25 Thread D . H . T . M . Gameren

Hi,

 

Just define a custom exception as a 'sub'  of a fault . You should be able to 
catch the exception when invoking your stub 

 

Regards

dirk

 

-Original Message-
From: Adrián Cuartero [mailto:[EMAIL PROTECTED] 
Sent: maandag 24 maart 2008 20:48
To: axis-user@ws.apache.org
Subject: Capture custom exception

 

Hi all

I keep trying throwing a custom exception and i've read there's a problem 
capturing this exception in the client side.

Anyone knows how to capture this custom exceptions?

Thanks

 




Enviado desde Correo Yahoo!
Disfruta de una bandeja de entrada más inteligente. 

 .




The information transmitted via this e-mail is intended only for the person or 
entity to which it is addressed and may contain confidential and/or privileged 
material.  Any review, retransmission, dissemination or other use of, or taking 
of any action in reliance upon this information by persons or entities other 
than the intended recipient is prohibited. If you received this in error, 
please contact the sender and delete the material from any computer.

Re: Re: classloading question with axis2 and jboss

2008-03-17 Thread Lucente, Richard D

The issue has to do with class loading order.  After a serious round of
debugging, what I found was that the tomcat classloader attempts to load
the class then fails.  The parent classloader within JBoss attempts to
load the class then fails.  Finally axis2 loads the class using the web
service's classloader from the service.aar's lib directory.  In a
generic case, this is how things worked in my deployment.
 
The issue I'm having is that I'm attempting to override the
javax.xml.registry.* classes shipped with JBoss with updated interfaces
to talk to a third party provider.  My service.aar contains a lib
directory with the custom jars inside.  However, the classloading scheme
described above causes the JBoss javax.xml.registry.* classes to always
be found first.  I never can load from my classloader.  When I attempted
to get the service classloader from the current MessageContext, I still
got the tomcat classloader which failed and then delegated to JBoss.
JBoss then loaded its implementation.
 
I'm using JBoss 4.0.5.GA and Axis2-1.2.
 
Can I change the classloading order so the service.aar's classloader
goes first?
 
Help!

RE: classloading question with axis2 and jboss

2008-03-13 Thread Lucente, Richard D

It's probably helpful to mention I'm using axis2-1.2 with
jboss-4.0.5.GA.  The api's I have don't quite match those in the linked
article, but I'll try what you suggest and let you know how that goes.

-Original Message-
From: Deepal Jayasinghe [mailto:[EMAIL PROTECTED] 
Sent: Thursday, March 13, 2008 1:26 AM
To: axis-user@ws.apache.org
Subject: Re: classloading question with axis2 and jboss


> I deployed a service.aar file with the following internal structure:
>  
> service.aar
>   META-INF
> MANIFEST.MF
> services.xml
> xsd0.xsd
> service.wsdl
>   lib
> jar1.jar
> jar2.jar
>   classes
> class1.class
>
> When class1 attempts to access a class in jar1.jar, the tomcat 
> webappclassloader fails to see the jars in the aar file and instead 
> delegates to its parent which is a jboss class loader.  This attempts 
> to find the class in other jboss class directories and then returns a 
> ClassNotFoundException.
>
> Axis2 is deployed as an exploded war directory within jboss.  My aar 
> file is deployed to mywar/WEB-INF/services.
>
> What do I need to do to load embedded jars from aar files within the 
> jboss/tomcat environment?  Should I just put these jars in the 
> mywar/WEB-INF/lib directory (which means other services see them as 
> well)?  I would prefer the isolation that comes with embedded jars if 
> possible.
>   
Well I have tested this and I am sure this is working fine. But one more
thing its depend on where you trying to load the class. If you trying to
load the class at the service invocation time you will not have any
problem but if you trying to do this at the deployment time you might
have some problem unless you follow the following KB.

http://wso2.org/library/98

Anyway I am more than happy to help you if you can send me you aar file
(or create a JIRA)

Thank you!
Deepal
> -



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

classloading question with axis2 and jboss

2008-03-12 Thread Lucente, Richard D

I deployed a service.aar file with the following internal structure:
 
service.aar
  META-INF
MANIFEST.MF
services.xml
xsd0.xsd
service.wsdl
  lib
jar1.jar
jar2.jar
  classes
class1.class

When class1 attempts to access a class in jar1.jar, the tomcat
webappclassloader fails to see the jars in the aar file and instead
delegates to its parent which is a jboss class loader.  This attempts to
find the class in other jboss class directories and then returns a
ClassNotFoundException.

Axis2 is deployed as an exploded war directory within jboss.  My aar
file is deployed to mywar/WEB-INF/services.

What do I need to do to load embedded jars from aar files within the
jboss/tomcat environment?  Should I just put these jars in the
mywar/WEB-INF/lib directory (which means other services see them as
well)?  I would prefer the isolation that comes with embedded jars if
possible.

- Rich

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Generating service.xml with wsdl2java

2008-02-20 Thread D . H . T . M . Gameren

Hi,

 

I suggest to create an ant-script which alters the 'default'
services.xml so you don't have to change

This manually everytime.

For instance alter the call to the skelton to the implementation

 

Regards

Dirk 

 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] 
Sent: woensdag 20 februari 2008 14:29
To: axis-user@ws.apache.org
Subject: Generating service.xml with wsdl2java

 

Hi all,

 

I am generating the server-side code from a wsdl with wsdl2java which
generates the corresponding java classes and the service.xml.

Now I am changing the service.xml to add some handlers, messagereceiver,
etc.

 

When some methods are added to wsdl, I am generating the code again with
wsdl2java and it replaces my service.xml which means I lose all my
changes of it.

Is there a way to automatically synchronize the old service.xml with the
new one?

 

Thanks,

Matthias.




The information transmitted via this e-mail is intended only for the person or 
entity to which it is addressed and may contain confidential and/or privileged 
material.  Any review, retransmission, dissemination or other use of, or taking 
of any action in reliance upon this information by persons or entities other 
than the intended recipient is prohibited. If you received this in error, 
please contact the sender and delete the material from any computer.

RE: writing a client

2008-02-15 Thread D . H . T . M . Gameren

Hi,

 

Indeed this is the aproach.

 

First genereate client-stub and then create a ServiceClient which calls
the stubmethods.

 

See small example voor de client main.

 

public static void main(String[] args) throws RemoteException {

// TODO Auto-generated method stub

DemoStub stub = new DemoStub();

DemoRequest request = new DemoRequest();

InputBean ib = new InputBean();

Structure[] ss = new Structure[5];

Structure str = new Structure();

for (int i = 0; i < 5; i++) {

str.setX(100 * (i + 1));

str.setY(200 * (i + 1));

ss[i] = str;

}

 

ib.setStruct(ss);

request.setInputBean(ib);

 

DemoResponse response = stub.bepaal(request);

OutputBean ob = response.getOutputBean();

 

 }

 

 

regards

Dirk

 

 

 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] 
Sent: vrijdag 15 februari 2008 13:12
To: axis-user@ws.apache.org
Subject: writing a client

 

Hi,

 

Could you please let me how to go about writing a client?

I mean what is the approach.

 

1)   Generate the client-side stub using wsdltojava & call methods
on the stub

2)   Start from using ServiceClient ..

 

What is the suggested approach?

 

Thanks,

Ajit   

 

 

DISCLAIMER:
This message contains privileged and confidential information and is
intended only for an individual named. If you are not the intended
recipient, you should not disseminate, distribute, store, print, copy or
deliver this message. Please notify the sender immediately by e-mail if
you have received this e-mail by mistake and delete this e-mail from
your system. E-mail transmission cannot be guaranteed to be secure or
error-free as information could be intercepted, corrupted, lost,
destroyed, arrive late or incomplete or contain viruses. The sender,
therefore, does not accept liability for any errors or omissions in the
contents of this message which arise as a result of e-mail transmission.
If verification is required, please request a hard-copy version.




The information transmitted via this e-mail is intended only for the person or 
entity to which it is addressed and may contain confidential and/or privileged 
material.  Any review, retransmission, dissemination or other use of, or taking 
of any action in reliance upon this information by persons or entities other 
than the intended recipient is prohibited. If you received this in error, 
please contact the sender and delete the material from any computer.

RE: [ws]Creating request response

2008-02-15 Thread D . H . T . M . Gameren

 

Hi,

 

For testing webservices i use SOAP-ui as a client

See  http://www.soapui.org/

 

You create a project and attach a wsdl (url)  and it generates a sample
message which you can fill-out.

Is this what you mean?

 

Regards

 

dirk

 

 

 

-Original Message-
From: Aditya Anad [mailto:[EMAIL PROTECTED] 
Sent: vrijdag 15 februari 2008 11:31
To: axis-user@ws.apache.org
Subject: [ws]Creating request response

 

Hi all,

 

I need to create a SOAP request And SOAP response from a given WSDL
manually and vice versa. I am through with WSDL.Is there any link or
manually u can refer which can help me up.

 

Regards

Aditya

 CAUTION - Disclaimer *
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended
solely for the use of the addressee(s). If you are not the intended
recipient, please notify the sender by e-mail and delete the original
message. Further, you are not to copy, disclose, or distribute this
e-mail or its contents to any other person and any such actions are
unlawful. This e-mail may contain viruses. Infosys has taken every
reasonable precaution to minimize this risk, but is not liable for any
damage you may sustain as a result of any virus in this e-mail. You
should carry out your own virus checks before opening the e-mail or
attachment. Infosys reserves the right to monitor and review the content
of all messages sent to or from this e-mail address. Messages sent to or
from this e-mail address may be stored on the Infosys e-mail system.
***INFOSYS End of Disclaimer INFOSYS***




The information transmitted via this e-mail is intended only for the person or 
entity to which it is addressed and may contain confidential and/or privileged 
material.  Any review, retransmission, dissemination or other use of, or taking 
of any action in reliance upon this information by persons or entities other 
than the intended recipient is prohibited. If you received this in error, 
please contact the sender and delete the material from any computer.

Separate XSD from WSDL

2008-01-21 Thread D . H . T . M . Gameren


Hi ,

I am trying to separate schema's from web-service wsdl.
This because of we  want to reuse this schema's

One way or the other I don't succeed in this.
I import the schema in the wsdl, but when generating my service and
client-stub but the are not complete.
I did create an entry in the XML-Catalog in Eclipse but this makes no
difference.

Anyone got an idea.
Thx

Dirk 




The information transmitted via this e-mail is intended only for the person or 
entity to which it is addressed and may contain confidential and/or privileged 
material.  Any review, retransmission, dissemination or other use of, or taking 
of any action in reliance upon this information by persons or entities other 
than the intended recipient is prohibited. If you received this in error, 
please contact the sender and delete the material from any computer.

RE: Exceptions

2008-01-21 Thread D . H . T . M . Gameren

 
Martin,
 
This is a sample wsdl
 

Dirk van Gameren 
--- 
Developer Consumer Finance 
*   Phone number: +31 (0)40 233 9586
*  Fax number:+31 (0)40 233 8655
*  E-mail:[EMAIL PROTECTED] 
--- 

-Original Message-
From: Martin Gainty [mailto:[EMAIL PROTECTED] 
Sent: 19 januari 2008 2:05
To: axis-user@ws.apache.org
Subject: Re: Exceptions



Can you display or attach WSDL ?

Bedankt
Martin

- Original Message - 
From: [EMAIL PROTECTED] 
To: axis-user@ws.apache.org 
Sent: Thursday, January 17, 2008 10:23 AM
Subject: Exceptions


 

Hi,

 

I am using WSDL2Java  tool to generate code.

In the WSDL I am using an  UserDefinedException which I
subclassed from AxisFault.

 

In the  generated a clientcode , the operation in the
ClientStub is throwing AxisFault and not my specific defined exception.

The generated service skeleton is throwing the right
Exception.

 

Anyone knows how to solve this.

 

Regards

Dirk van Gameren


---

Developer Consumer Finance

* Phone number: +31 (0)40 233 9586
* Fax number: +31 (0)40 233 8655
* E-mail: [EMAIL PROTECTED] 


---

 



The information transmitted via this e-mail is intended
only for the person or entity to which it is addressed and may contain
confidential and/or privileged material.  Any review, retransmission,
dissemination or other use of, or taking of any action in reliance upon
this information by persons or entities other than the intended
recipient is prohibited. If you received this in error, please contact
the sender and delete the material from any computer.






The information transmitted via this e-mail is intended only for the person or 
entity to which it is addressed and may contain confidential and/or privileged 
material.  Any review, retransmission, dissemination or other use of, or taking 
of any action in reliance upon this information by persons or entities other 
than the intended recipient is prohibited. If you received this in error, 
please contact the sender and delete the material from any computer.


sample.wsdl
Description: Binary data
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Exceptions

2008-01-18 Thread D . H . T . M . Gameren

 

Hi,

 

I am using WSDL2Java  tool to generate code.

In the WSDL I am using an  UserDefinedException which I subclassed from
AxisFault.

 

In the  generated a clientcode , the operation in the ClientStub is
throwing AxisFault and not my specific defined exception.

The generated service skeleton is throwing the right Exception.

 

Anyone knows how to solve this.

 

Regards

Dirk van Gameren

---

Developer Consumer Finance

* Phone number: +31 (0)40 233 9586
* Fax number: +31 (0)40 233 8655
* E-mail: [EMAIL PROTECTED] 

---

 




The information transmitted via this e-mail is intended only for the person or 
entity to which it is addressed and may contain confidential and/or privileged 
material.  Any review, retransmission, dissemination or other use of, or taking 
of any action in reliance upon this information by persons or entities other 
than the intended recipient is prohibited. If you received this in error, 
please contact the sender and delete the material from any computer.

RE: Eclipse, wsdl2java and huge warnings

2008-01-18 Thread D . H . T . M . Gameren

This is strange i don't get warnings.
I only use ADB not XMLBeans.

QName is the Qualifiedname , so the full name of the NameSpace including 
operation or schema,

In which class do you encounter this warnings? 

dirk

-Original Message-
From: Weck, Andreas [mailto:[EMAIL PROTECTED] 
Sent: vrijdag 18 januari 2008 9:39
To: axis-user@ws.apache.org
Subject: AW: Eclipse, wsdl2java and huge warnings

I tried the Axis2_CodeGen_wizard_1.3.0, but if have still the same warnings: 

if i use ADB:
- The local variable event is never read
- The local variable handledAttributes is never read
- The local variable namespaceuri is never read
- The local variable nillableValue is never read
- The local variable prefix is never read
- The method writeAttribute(String, String, String, String, XMLStreamWriter) 
from the type [TYPE] is never used locally
- The method writeQName(QName, XMLStreamWriter) from the type [TYPE] is never 
used locally

BTW: What is QName?

if i use XMLBeans:
- The local variable [VARNAME] is never read
- The serializable class [NAME] does not declare a static final 
serialVersionUID field of type long
- The method [NAME] from the type [TYP] is never used locally

Regards,
Andreas

-Ursprüngliche Nachricht-

Maybe , you can use the Eclipse plugin
Axis2_CodeGen_wizard_1.3.0

It does the same. I am using it. It works fine.
You can use it ones and then build an ant-script to Regenerate.

This works without warnings.

Regards

Dirk

 

-Original Message-

Hi all,

i just downloaded the JDK 6 Update 4, axis2 1.3 and Eclipse 3.3. After that 
i've used the wsdl2java command-line tool to create the client classes.

wsdl2java -uri service.wsdl -u

Than i made a new java project in eclipse, with the options (compiler 
compliance level 1.4) and imported all the generated java files into it.
Now it have approximately 500 warnings!!! Mostley like "The local variable 
[VARNAME] is never read" (in can see the first 100 only)

Does anyone have any suggestions around suppressing/fixing these warnings?

Regards,
Andreas


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]







The information transmitted via this e-mail is intended only for the person or 
entity to which it is addressed and may contain confidential and/or privileged 
material.  Any review, retransmission, dissemination or other use of, or taking 
of any action in reliance upon this information by persons or entities other 
than the intended recipient is prohibited. If you received this in error, 
please contact the sender and delete the material from any computer.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]







The information transmitted via this e-mail is intended only for the person or 
entity to which it is addressed and may contain confidential and/or privileged 
material.  Any review, retransmission, dissemination or other use of, or taking 
of any action in reliance upon this information by persons or entities other 
than the intended recipient is prohibited. If you received this in error, 
please contact the sender and delete the material from any computer.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Eclipse, wsdl2java and huge warnings

2008-01-17 Thread D . H . T . M . Gameren

Maybe , you can use the Eclipse plugin 
Axis2_CodeGen_wizard_1.3.0

It does the same. I am using it. It works fine.
You can use it ones and then build an ant-script to
Regenerate.

This works without warnings.

Regards

Dirk

 

-Original Message-
From: Weck, Andreas [mailto:[EMAIL PROTECTED] 
Sent: donderdag 17 januari 2008 13:15
To: axis-user@ws.apache.org
Subject: Eclipse, wsdl2java and huge warnings

Hi all,

i just downloaded the JDK 6 Update 4, axis2 1.3 and Eclipse 3.3. After
that i've used the wsdl2java command-line tool to create the client
classes.

wsdl2java -uri service.wsdl -u

Than i made a new java project in eclipse, with the options (compiler
compliance level 1.4) and imported all the generated java files into it.
Now it have approximately 500 warnings!!! Mostley like "The local
variable [VARNAME] is never read" (in can see the first 100 only)

Does anyone have any suggestions around suppressing/fixing these
warnings?

Regards,
Andreas


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]







The information transmitted via this e-mail is intended only for the person or 
entity to which it is addressed and may contain confidential and/or privileged 
material.  Any review, retransmission, dissemination or other use of, or taking 
of any action in reliance upon this information by persons or entities other 
than the intended recipient is prohibited. If you received this in error, 
please contact the sender and delete the material from any computer.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: secure web services

2008-01-16 Thread D . H . T . M . Gameren

 

Hi ,

 

Maybe you can use rampart for signing and encrypting you Soap-messages.

See.
http://ws.apache.org/axis2/modules/rampart/1_0/security-module.html

 

 

Dirk 

 

-Original Message-
From: Asensio, Rodrigo [mailto:[EMAIL PROTECTED] 
Sent: woensdag 16 januari 2008 12:16
To: axis-user@ws.apache.org
Subject: secure web services

 

Hello, I'm posting a new web service with critical functionality for my
company. Our customers will communicate with us thru this new features.
I would like to know what is a good approach to security in this case.

 

Thank you

Rodrigo

This message (including any attachments) contains confidential 
and/or proprietary information intended only for the addressee. 
Any unauthorized disclosure, copying, distribution or reliance on 
the contents of this information is strictly prohibited and may 
constitute a violation of law. If you are not the intended 
recipient, please notify the sender immediately by responding to 
this e-mail, and delete the message from your system. If you 
have any questions about this e-mail please notify the sender 
immediately. 





The information transmitted via this e-mail is intended only for the person or 
entity to which it is addressed and may contain confidential and/or privileged 
material.  Any review, retransmission, dissemination or other use of, or taking 
of any action in reliance upon this information by persons or entities other 
than the intended recipient is prohibited. If you received this in error, 
please contact the sender and delete the material from any computer.

RE: Problem WS-addressing

2008-01-16 Thread D . H . T . M . Gameren

Paul.

Firewall is off. 

Dirk


-Original Message-
From: Paul Fremantle [mailto:[EMAIL PROTECTED] 
Sent: woensdag 16 januari 2008 10:42
To: axis-user@ws.apache.org
Subject: Re: Problem WS-addressing

Dirk

This might be a firewall problem.

Paul

On Jan 16, 2008 9:27 AM,  <[EMAIL PROTECTED]> wrote:
>
>
>
>
>
>
> Hello,
>
>
>
> I am having a problem with Axis using Addressing.  I have noticed a lot of
> you also have.
>
> The problem of not able to engage addressing I have solved using this info,
> (thx for that)
>
>
>
> When I start my client-app , it's indication it starts a listener on port
> 6060 (default) for the callback.
>
> However when the web-service is trying to send the response it is timed-out.
>
>
>
> When inspecting this with netstat  It seems there isn't a listener on port
> 6060 active.
>
> Anyone got an idea.?
>
>
>
>
>
>
>
>
>
> public class BizRegClient {
>
> public static void main(String[] args) throws RemoteException {
>
> ConfigurationContext cc =
> ConfigurationContextFactory.createConfigurationContextFromFileSystem(
>
> "c:/axis/repository");
>
> ManualServiceStub stub = new ManualServiceStub(cc);
>
> final ServiceClient serviceClient = stub._getServiceClient();
>
>
>
> serviceClient.engageModule("addressing");
>
>
>
> Options options = serviceClient.getOptions();
>
> options.setUseSeparateListener(true);
>
>
>
> Register request = new Register();
>
>
>
>   .
>
>
>
> ..
>
> }
>
> }
>
>
>
> Dirk van Gameren
>
> ---
>
> Developer Consumer Finance
>
> ( Phone number: +31 (0)40 233 9586
>  Ê Fax number: +31 (0)40 233 8655
>  * E-mail: [EMAIL PROTECTED]
>
> ---
>
>
>
> 
> The information transmitted via this e-mail is intended only for the person
> or entity to which it is addressed and may contain confidential and/or
> privileged material. Any review, retransmission, dissemination or other use
> of, or taking of any action in reliance upon this information by persons or
> entities other than the intended recipient is prohibited. If you received
> this in error, please contact the sender and delete the material from any
> computer.
>
>



-- 
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
OASIS WS-RX TC Co-chair

blog: http://pzf.fremantle.org
[EMAIL PROTECTED]

"Oxygenating the Web Service Platform", www.wso2.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]







The information transmitted via this e-mail is intended only for the person or 
entity to which it is addressed and may contain confidential and/or privileged 
material.  Any review, retransmission, dissemination or other use of, or taking 
of any action in reliance upon this information by persons or entities other 
than the intended recipient is prohibited. If you received this in error, 
please contact the sender and delete the material from any computer.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Problem WS-addressing

2008-01-16 Thread D . H . T . M . Gameren

 

Hello,

 

I am having a problem with Axis using Addressing.  I have noticed a lot
of you also have.

The problem of not able to engage addressing I have solved using this
info, (thx for that)

 

When I start my client-app , it's indication it starts a listener on
port 6060 (default) for the callback.

However when the web-service is trying to send the response it is
timed-out.

 

When inspecting this with netstat  It seems there isn't a listener on
port 6060 active.

Anyone got an idea.?

 

 

 

 

public class BizRegClient {

public static void main(String[] args) throws RemoteException {

ConfigurationContext cc =
ConfigurationContextFactory.createConfigurationContextFromFileSystem(

"c:/axis/repository");

ManualServiceStub stub = new ManualServiceStub(cc);

final ServiceClient serviceClient = stub._getServiceClient();

 

serviceClient.engageModule("addressing");

 

Options options = serviceClient.getOptions();

options.setUseSeparateListener(true);

 

Register request = new Register();

 

  .

 

..

}

}

 

Dirk van Gameren

---

Developer Consumer Finance

* Phone number: +31 (0)40 233 9586
* Fax number: +31 (0)40 233 8655
* E-mail: [EMAIL PROTECTED] 

---

 




The information transmitted via this e-mail is intended only for the person or 
entity to which it is addressed and may contain confidential and/or privileged 
material.  Any review, retransmission, dissemination or other use of, or taking 
of any action in reliance upon this information by persons or entities other 
than the intended recipient is prohibited. If you received this in error, 
please contact the sender and delete the material from any computer.

axis1.2 and REST

2007-08-20 Thread D P

Hello all,

I would like to sent a POST message to a service RESTfully. I reviewed the
Axis1.2 docs and understand how the  message is automatically placed in the
body element of a SOAP message on the way in. On the way out to the client,
should my in/out message receiver class attempt to place the response into
the body of a soap message?

Re: specifying retries of client stub

2007-07-05 Thread D P


Sorry, I forgot to mention I'm using Axis2 v1.2

On 7/4/07, D P <[EMAIL PROTECTED]> wrote:


Hello all,
How can I set the client service stub to retry if the underlying http
connection times out or throws some other error?  I believe that sandesha2
can do this, but I'm not able to deploy any additional modules to axis2 at
this time.  Are there any other options?

P

specifying retries of client stub

2007-07-04 Thread D P


Hello all,
How can I set the client service stub to retry if the underlying http
connection times out or throws some other error?  I believe that sandesha2
can do this, but I'm not able to deploy any additional modules to axis2 at
this time.  Are there any other options?

P

[AXIS2] WSDL2Java code generation problem

2007-07-03 Thread Lucente, Richard D

Axis2-1.2 wsdl2java is failing to generate compilable code for the
NotificationConsumer port defined as part of the WS-BaseNotification 1.3
standard.  Wsdl2java appears to have trouble with the definition of
TopicType within the WS-Topics 1.3 schema.  I tried this with adb,
xmlbeans, jibx, jaxme, and jaxbri and got similar results (sometimes
wsdl2java choked on WS-Topics).  Any help appreciated.
 
Specifically, I downloaded the wsdl file from
http://docs.oasis-open.org/wsn/bw-2.wsdl and added the following binding
and service elements:
 

http://schemas.xmlsoap.org/soap/http";
/>

http://docs.oasis-open.org/wsn/bw-2/Notify"; />







http://localhost:8080/wsn-consumer/services/NotificationConsum
er" />


 
I then ran the command:
 
wsdl2java -uri bw-2.wsdl -pn NotificationConsumer
 
The code generator produced the following messages:
 
Using AXIS2_HOME:   D:\pathfinder\axis2-1.2
Using JAVA_HOME:D:\Progra~1\Java\j2sdk1.4.2_12
Retrieving document at 'http://docs.oasis-open.org/wsrf/rw-2.wsdl',
relative to 'file:/D:/pathfinder/temp/'.
Retrieving schema at 'http://docs.oasis-open.org/wsrf/r-2.xsd', relative
to 'http://docs.oasis-open.org/wsrf/rw-2.wsdl'.
Retrieving schema at 'http://docs.oasis-open.org/wsrf/bf-2.xsd',
relative to 'http://docs.oasis-open.org/wsrf/r-2.xsd'.
Retrieving schema at 'http://www.w3.org/2001/xml.xsd', relative to
'http://docs.oasis-open.org/wsrf/bf-2.xsd'.
Retrieving schema at 'http://www.w3.org/2005/08/addressing/ws-addr.xsd',
relative to 'http://docs.oasis-open.org/wsrf/bf-2.xsd'.
Retrieving schema at 'http://docs.oasis-open.org/wsn/b-2.xsd', relative
to 'file:/D:/pathfinder/temp/'.
Retrieving schema at 'http://docs.oasis-open.org/wsrf/bf-2.xsd',
relative to 'http://docs.oasis-open.org/wsn/b-2.xsd'.
Retrieving schema at 'http://docs.oasis-open.org/wsn/t-1.xsd', relative
to 'http://docs.oasis-open.org/wsn/b-2.xsd'.
Retrieving schema at 'http://www.w3.org/2005/08/addressing/ws-addr.xsd',
relative to 'http://docs.oasis-open.org/wsn/b-2.xsd'.
Retrieving document at 'http://docs.oasis-open.org/wsrf/rw-2.wsdl',
relative to 'file:/D:/pathfinder/temp/'.
Retrieving schema at 'http://docs.oasis-open.org/wsrf/r-2.xsd', relative
to 'http://docs.oasis-open.org/wsrf/rw-2.wsdl'.
Retrieving schema at 'http://docs.oasis-open.org/wsrf/bf-2.xsd',
relative to 'http://docs.oasis-open.org/wsrf/r-2.xsd'.
Retrieving schema at 'http://www.w3.org/2001/xml.xsd', relative to
'http://docs.oasis-open.org/wsrf/bf-2.xsd'.
Retrieving schema at 'http://www.w3.org/2005/08/addressing/ws-addr.xsd',
relative to 'http://docs.oasis-open.org/wsrf/bf-2.xsd'.
Retrieving schema at 'http://docs.oasis-open.org/wsn/b-2.xsd', relative
to 'file:/D:/pathfinder/temp/'.
Retrieving schema at 'http://docs.oasis-open.org/wsrf/bf-2.xsd',
relative to 'http://docs.oasis-open.org/wsn/b-2.xsd'.
Retrieving schema at 'http://docs.oasis-open.org/wsn/t-1.xsd', relative
to 'http://docs.oasis-open.org/wsn/b-2.xsd'.
Retrieving schema at 'http://www.w3.org/2005/08/addressing/ws-addr.xsd',
relative to 'http://docs.oasis-open.org/wsn/b-2.xsd'.
 
I then attempted to build with the generated build.xml file and
apache-ant-1.7.0 by typing:
 
ant
 
I received the following output:
 
Buildfile: build.xml
 
init:
[mkdir] Created dir: D:\pathfinder\temp\build
[mkdir] Created dir: D:\pathfinder\temp\build\classes
[mkdir] Created dir: D:\pathfinder\temp\build\lib
[mkdir] Created dir: D:\pathfinder\temp\test
 
pre.compile.test:
 [echo] Stax Availability= true
 [echo] Axis2 Availability= true
 
compile.src:
[javac] Compiling 2 source files to D:\pathfinder\temp\build\classes
[javac]
D:\pathfinder\temp\src\org\oasis_open\docs\wsn\bw_2\NotificationConsumer
Stub.java:1832:
fromString(javax.xml.stream.XMLStreamReader,java.lang.Stri
ng) in
org.oasis_open.docs.wsn.bw_2.NotificationConsumerStub.MessageTypes_type4
.Factory cannot be applied to (java.lang.String,java.lang.String)
[javac]
MessageTypes_type4.Factory.fromString(tempAttribmessageTypes,namespaceur
i));
[javac]
^
[javac]
D:\pathfinder\temp\src\org\oasis_open\docs\wsn\bw_2\NotificationConsumer
Stub.java:1837:
fromString(javax.xml.stream.XMLStreamReader,java.lang.Stri
ng) in
org.oasis_open.docs.wsn.bw_2.NotificationConsumerStub.MessageTypes_type4
.Factory cannot be applied to (java.lang.String,java.lang.String)
[javac]
MessageTypes_t

Re: [AXIS2] Codegen omitting Header item from Client and Server interfaces and skeletons

2007-06-04 Thread D


Doh,

I resolved this issue by fixing my badly written build script to
prevent it overwriting the generated files with old ones :-(

Apologies for polluting the mailing list.

Best Regards,
Darren

On 04/06/07, D <[EMAIL PROTECTED]> wrote:

Hi Folks,

I'm generating clients and servers for 2 services from WSDLs (+ XSDs)
using the Codegen Ant task.

For one WSDL, the generated interfaces and skeletons correctly include
a parameter for an item in the soap:header, but in the second case
they do not.

In both cases classes for the underlying item are created, including
an xyzDocument as should appear in the interface signatures.

The WSDLs follow the same structure and they both validate.

With debug logging turned on during codegen, I have captured the
documents created for input to code generation.

(I have attached the documents to this email... 1.xml is the document
for the skeleton interface on the correct service. 2.xml is the
document for the skeleton interface on the service with the header
item missing).

To me, the documents seem to contain equivalent information describing
the header item, but only the resulting code for one service has the
correct interfaces/skeletons.

I don't see any ERRORs or even WARNings on the log output.



Please can you suggest how I can resolve this?

Many Thanks,
Darren


(P.S. I'm running Java 1.6 on redhat linux and I've got the same
outcome using Axis 1.1.1 and Axis 1.2).




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[AXIS2] Codegen omitting Header item from Client and Server interfaces and skeletons

2007-06-04 Thread D

Hi Folks,

I'm generating clients and servers for 2 services from WSDLs (+ XSDs)
using the Codegen Ant task.

For one WSDL, the generated interfaces and skeletons correctly include
a parameter for an item in the soap:header, but in the second case
they do not.

In both cases classes for the underlying item are created, including
an xyzDocument as should appear in the interface signatures.

The WSDLs follow the same structure and they both validate.

With debug logging turned on during codegen, I have captured the
documents created for input to code generation.

(I have attached the documents to this email... 1.xml is the document
for the skeleton interface on the correct service. 2.xml is the
document for the skeleton interface on the service with the header
item missing).

To me, the documents seem to contain equivalent information describing
the header item, but only the resulting code for one service has the
correct interfaces/skeletons.

I don't see any ERRORs or even WARNings on the log output.

Please can you suggest how I can resolve this?

Many Thanks,
Darren

(P.S. I'm running Java 1.6 on redhat linux and I've got the same
outcome using Axis 1.1.1 and Axis 1.2).

http://www.w3.org/2004/08/wsdl/in-out"; name="WapPush" namespace="" soapaction="urn:pap/WapPush" style="document" usdbimpl="false">

http://www.w3.org/2004/08/wsdl/in-out"; name="SendSms" namespace="" soapaction="urn:sms/SendSms" style="document" usdbimpl="false">

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

unregister

2007-05-07 Thread Johnson, Larry D \(LJOHNSON\)

org.xml.sax.SAXException: Invalid element in ARWSClient.CreateOutputMap - Request_ID

2007-03-28 Thread Ding D

Hi,
I am trying to access WSDL created on remedy system ,
I am getting this error can any one help me on this?
My enviroment:
Axis 1.4,java 1.5
Please let me know if you need anything else.
Thanks,
Ding

Mar 20, 2007 7:13:47 AM org.apache.axis.client.Call
invoke
SEVERE: Exception:
org.xml.sax.SAXException: Invalid element in
ARWSClient.CreateOutputMap - Request_ID
at
org.apache.axis.encoding.ser.BeanDeserializer.onStartChild(BeanDeserializer.java:258)
at
org.apache.axis.encoding.DeserializationContext.startElement(DeserializationContext.java:1035)
at
org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:165)
at
org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:1141)
at
org.apache.axis.message.RPCElement.deserialize(RPCElement.java:236)
at
org.apache.axis.message.RPCElement.getParams(RPCElement.java:384)
at
org.apache.axis.client.Call.invoke(Call.java:2467)
at
org.apache.axis.client.Call.invoke(Call.java:2366)
at
org.apache.axis.client.Call.invoke(Call.java:1812)
at
ARWSClient.IHD_RemedyWebServiceSoapBindingStub.opCreate(IHD_RemedyWebServiceSoapBindingStub.java:291)
at
ARWSClient.TestClient.main(TestClient.java:22)
Exception in thread "main" AxisFault
 faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.userException
 faultSubcode:
 faultString: org.xml.sax.SAXException: Invalid
element in ARWSClient.CreateOutputMap - Request_ID
 faultActor:
 faultNode:
 faultDetail:
   
{http://xml.apache.org/axis/}stackTrace:org.xml.sax.SAXException:
Invalid element in ARWSClient.CreateOutputMap - Req
uest_ID
at
org.apache.axis.encoding.ser.BeanDeserializer.onStartChild(BeanDeserializer.java:258)
at
org.apache.axis.encoding.DeserializationContext.startElement(DeserializationContext.java:1035)
at
org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:165)
at
org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:1141)
at
org.apache.axis.message.RPCElement.deserialize(RPCElement.java:236)
at
org.apache.axis.message.RPCElement.getParams(RPCElement.java:384)
at
org.apache.axis.client.Call.invoke(Call.java:2467)
at
org.apache.axis.client.Call.invoke(Call.java:2366)
at
org.apache.axis.client.Call.invoke(Call.java:1812)
at
ARWSClient.IHD_RemedyWebServiceSoapBindingStub.opCreate(IHD_RemedyWebServiceSoapBindingStub.java:291)
at
ARWSClient.TestClient.main(TestClient.java:22)

{http://xml.apache.org/axis/}hostname:DINGM20

org.xml.sax.SAXException: Invalid element in
ARWSClient.CreateOutputMap - Request_ID
at
org.apache.axis.AxisFault.makeFault(AxisFault.java:101)
at
org.apache.axis.client.Call.invoke(Call.java:2470)
at
org.apache.axis.client.Call.invoke(Call.java:2366)
at
org.apache.axis.client.Call.invoke(Call.java:1812)
at
ARWSClient.IHD_RemedyWebServiceSoapBindingStub.opCreate(IHD_RemedyWebServiceSoapBindingStub.java:291)
at
ARWSClient.TestClient.main(TestClient.java:22)
Caused by: org.xml.sax.SAXException: Invalid element
in ARWSClient.CreateOutputMap - Request_ID
at
org.apache.axis.encoding.ser.BeanDeserializer.onStartChild(BeanDeserializer.java:258)
at
org.apache.axis.encoding.DeserializationContext.startElement(DeserializationContext.java:1035)
at
org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:165)
at
org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:1141)
at
org.apache.axis.message.RPCElement.deserialize(RPCElement.java:236)
at
org.apache.axis.message.RPCElement.getParams(RPCElement.java:384)
at
org.apache.axis.client.Call.invoke(Call.java:2467)
... 4 more



 

Bored stiff? Loosen up... 
Download and play hundreds of games for free on Yahoo! Games.
http://games.yahoo.com/games/front

IHD_RemedyWebService.wsdl
Description: 97359196-IHD_RemedyWebService.wsdl
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Axis2] Generated client stub causes Null Pointer Exception in UTF8OutputStreamWriter.write

2007-03-23 Thread D


Apologies, when I put the fix in ALL my schema files, the issue was resolved.

Many Thanks,
Darren

On 22/03/07, D <[EMAIL PROTECTED]> wrote:

Hi Davanum,

Once registered with jira, I searched and found what looks (to my untrained
eye) like the same issue, already logged:

AXIS2-1964 Null Pointer Exception in Service STUB class at
_operationClient.execute(true); line for AXIS2 1.1.1

Best Regards,
Darren

P.S. Recommendation in the last comment: adding
elementFormDefault="qualified" did not fix the issue in my case :-(



On 22/03/07, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
> nope. please log a jira bug with enough code for us to recreate the
problem.
>
> thanks,
> dims
>
> On 3/22/07, D <[EMAIL PROTECTED]> wrote:
> > Thanks Davanum,
> >
> > That resolved the issue on the request side, but unfortunately what
looks
> > (to me?!) like a similar error now occurs when the server is serializing
its
> > response.
> >
> > (This is the same client and server, generated successfully using
> > wsdl2java).
> >
> > org.apache.axis2.AxisFault: unknown
> > at
> >
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:271)
> > at
> >
org.apache.axis2.description.OutInAxisOperationClient.execute
> > (OutInAxisOperation.java:202)
> > at
> >
com.xyz.generated.wsmms.send.MmsSendServiceStub.SendMms(MmsSendServiceStub.java:184)
> > at
> > com.xyz.wsmms.test.MMSSend.execute(MMSSend.java :161)
> > at com.xyz.wsmms.test.MMSSend.main (MMSSend.java:283)
> > Caused by: java.lang.Exception: java.lang.NullPointerException
> > at
> > com.ctc.wstx.sw.BaseNsStreamWriter.doWriteDefaultNs
(BaseNsStreamWriter.java:528)
> > at
> >
com.ctc.wstx.sw.SimpleNsStreamWriter.writeDefaultNamespace
> > (SimpleNsStreamWriter.java:111)
> > at
> > com.ctc.wstx.sw.SimpleNsStreamWriter.writeNamespace
(SimpleNsStreamWriter.java:119)
> > at
> >
org.apache.axiom.om.impl.MTOMXMLStreamWriter.writeNamespace(MTOMXMLStreamWriter.java
> > :146)
> > at
> >
org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serializeElement
(StreamingOMSerializer.java:243)
> > at
> >
org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serializeNode(StreamingOMSerializer.java
> > :76)
> > at
> >
org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serialize
(StreamingOMSerializer.java:59)
> > at
> >
org.apache.axiom.om.impl.util.OMSerializerUtil.serializeByPullStream(OMSerializerUtil.java
> > :473)
> > at
> >
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize
(OMElementImpl.java:823)
> > at
> >
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:848)
> > at
> >
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize
(OMElementImpl.java:819)
> > at
> >
org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize(SOAPEnvelopeImpl.java:180)
> > at
> >
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume
> > (OMElementImpl.java:848)
> > at
> >
org.apache.axiom.om.impl.llom.OMNodeImpl.serializeAndConsume(OMNodeImpl.java:429)
> > at
> >
org.apache.axis2.transport.http.CommonsHTTPTransportSender.sendUsingOutputStream
(CommonsHTTPTransportSender.java
> > :272)
> > at
> >
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:208)
> > at
> > org.apache.axis2.engine.AxisEngine.send
(AxisEngine.java:674)
> > at
> >
org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive
> > (AbstractInOutSyncMessageReceiver.java:48)
> > at
> > org.apache.axis2.engine.AxisEngine.receive
(AxisEngine.java:497)
> > at
> >
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java
> > :328)
> > at
> > org.apache.axis2.transport.http.HTTPWorker.service
(HTTPWorker.java:230)
> > at
> >
org.apache.axis2.transport.http.server.DefaultHttpServiceProcessor.doService(DefaultHttpServiceProcessor.java:189)
> >  at
> > org.apache.http.protocol.HttpService.handleRequest
(HttpService.java:123)
> > at
> >
org.apache.axis2.transport.http.server.DefaultHttpServiceProcessor.run(DefaultHttpServiceProcessor.java:261)
> > at
> >
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask
(ThreadPoolExecutor.java:665)
> > at
> >

Re: axis2: noise on Soap-messages

2007-03-23 Thread D


Hi,

I think this is data present when using chunked http encoding...it's not
noise...it's helping http work!

Regards,
Darren

On 23/03/07, Tromp Bert <[EMAIL PROTECTED]> wrote:


 Hi,

I'm doing some tests for using axis2 with rampart as a soap-server/client.
 I've been trying out the examples that are provided with axis2 and
rampart and this works fine. But when I use MSSoapTrace to trace the
messages between client and server, there is always some data before and
after the soap-envelope.

e.g.

*104*

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

**

Is there something wrong with my configuration or what should I do to make
it go away?

I'm using:

axis2-1.2.1
rampart-1.1
jdk 1.5.0_11

Regards,
Bert
 --
 This message and its attachments may contain confidential information
protected by intellectual property rights or other rights & is strictly for
the exclusive use of the intended recipient. It is strictly prohibited to
copy, alter or disclose this message or its contents to any other person
without Elia's prior consent. If you are not the intended recipient of this
message, please inform the person who sent it and delete the message from
your system. Elia is not liable for any direct or indirect damage arising
from errors, inaccuracies or any loss in the message, from unauthorized use,
disclosure, copying or alteration of it or as a result of any virus being
passed on. This message does not constitute any commitment from Elia except
when expressly otherwise agreed between the intended recipient and Elia.
U vindt de Nederlandse versie van deze disclaimer op onze internetsite
www.elia.be
Vous pouvez découvrir la version française de ce disclaimer sur notre site
internet www.elia.be
 --

Re: Axis 2 v1.1.1: disabling auto generated WSDL file

2007-03-22 Thread D P


Sorry everyone, I discovered I made a mistake with the services.xml file.
Please consider my question resolved.

On 3/22/07, D P <[EMAIL PROTECTED]> wrote:


Thanks for all your replies.

Krishna:  I followed your directions, and changed the case of the
parameter. However, I'm still observing the items I noted in #2 of my
original email.  Also, I noticed that Axis2 has also removed the "parts"
attribute in my soap12:body and soap:body elements.

Amila:  I'm sorry, but I don't quite follow your response.  Are you saying
that the issue in general is known, or the specific observations I made in
#2 of my email is known?


On 3/22/07, Amila Suriarachchi <[EMAIL PROTECTED]> wrote:
>
>
>
> On 3/21/07, D P < [EMAIL PROTECTED]> wrote:
> >
> > Hello all,
> > When a client queries the service wsdl at
> > http://../../serviceName?wsdl, I would like the service to return the wsdl
> > which I packaged in the .aar file, _not_ an auto generated wsdl.  I came
> > across a possible solution here:
> > http://www.mail-archive.com/axis-user@ws.apache.org/msg25033.html.
> > 1.  It appears though there are some issues with the solution.  Does
> > anyone know if this works for sure?
> >
> > 2.  After implementing the solution in my services.xml file, i noticed
> > 2 things:
> > a.) i've refactored out some schema into an xsd file, and import it to
> > multiple wsdls.  A copy of the xsd file is packaged with each wsdl and the
> > code to import the xsd uses schemaLocation=" foo.xsd".  But when I
> > look at the wsdl file at http://../../serviceName?wsdl, the schemaLocation
> > element value is now schemaLocation="serviceName?xsd=xsd0".  Why is this
> > happening?
> >
> > b) When I look at the wsdl file at http://../../serviceName?wsdl, i
> > notice that wsdl:portType/wsdl:operation/wsdl:input and
> > wsdl:portType/wsdl:operation/wsdl:output have a wsaw:Action, whereas the
> > original wsdl I packaged with the .aar does not. Why is this happening?
>
>
> I think this is a known issue.
> In Axis2 we use the  WSDL11ToAxisServiceBuilder to build the Axis
> Service from the wsdl file. The first step it does is it process the
> imports.
> i.e . It iterates through all the imported wsdls and  put all the
> imports  to the service wsdl.  Then when serializing the wsdl4jDefinition it
> serializes this changed wsdl4j object. So it contains both original imports
> (I removed this recently) and the imported elements.
> please log a jira.
>
> Any feedback would be appreciated.
> >
>
>
>
> --
> Amila Suriarachchi,
> WSO2 Inc.

Re: [Axis2] Generated client stub causes Null Pointer Exception in UTF8OutputStreamWriter.write

2007-03-22 Thread D


Hi Davanum,

Once registered with jira, I searched and found what looks (to my untrained
eye) like the same issue, already logged:

AXIS2-1964 Null Pointer Exception in Service STUB class at
_operationClient.execute(true); line for AXIS2 1.1.1

Best Regards,
Darren

P.S. Recommendation in the last comment: adding
elementFormDefault="qualified" did not fix the issue in my case :-(


On 22/03/07, Davanum Srinivas <[EMAIL PROTECTED]> wrote:


nope. please log a jira bug with enough code for us to recreate the
problem.

thanks,
dims

On 3/22/07, D <[EMAIL PROTECTED]> wrote:
> Thanks Davanum,
>
> That resolved the issue on the request side, but unfortunately what
looks
> (to me?!) like a similar error now occurs when the server is serializing
its
> response.
>
> (This is the same client and server, generated successfully using
> wsdl2java).
>
> org.apache.axis2.AxisFault: unknown
> at
> org.apache.axis2.description.OutInAxisOperationClient.send(
OutInAxisOperation.java:271)
> at
> org.apache.axis2.description.OutInAxisOperationClient.execute
> (OutInAxisOperation.java:202)
> at
> com.xyz.generated.wsmms.send.MmsSendServiceStub.SendMms(
MmsSendServiceStub.java:184)
> at
> com.xyz.wsmms.test.MMSSend.execute(MMSSend.java:161)
> at com.xyz.wsmms.test.MMSSend.main (MMSSend.java:283)
> Caused by: java.lang.Exception: java.lang.NullPointerException
> at
> com.ctc.wstx.sw.BaseNsStreamWriter.doWriteDefaultNs(
BaseNsStreamWriter.java:528)
> at
> com.ctc.wstx.sw.SimpleNsStreamWriter.writeDefaultNamespace
> (SimpleNsStreamWriter.java:111)
> at
> com.ctc.wstx.sw.SimpleNsStreamWriter.writeNamespace(
SimpleNsStreamWriter.java:119)
> at
> org.apache.axiom.om.impl.MTOMXMLStreamWriter.writeNamespace(
MTOMXMLStreamWriter.java
> :146)
> at
>
org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serializeElement(
StreamingOMSerializer.java:243)
> at
> org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serializeNode(
StreamingOMSerializer.java
> :76)
> at
> org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serialize(
StreamingOMSerializer.java:59)
> at
> org.apache.axiom.om.impl.util.OMSerializerUtil.serializeByPullStream(
OMSerializerUtil.java
> :473)
> at
> org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(
OMElementImpl.java:823)
> at
> org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(
OMElementImpl.java:848)
> at
> org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(
OMElementImpl.java:819)
> at
> org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize(
SOAPEnvelopeImpl.java:180)
> at
> org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume
> (OMElementImpl.java:848)
> at
> org.apache.axiom.om.impl.llom.OMNodeImpl.serializeAndConsume(
OMNodeImpl.java:429)
> at
>
org.apache.axis2.transport.http.CommonsHTTPTransportSender.sendUsingOutputStream
(CommonsHTTPTransportSender.java
> :272)
> at
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(
CommonsHTTPTransportSender.java:208)
> at
> org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:674)
> at
> org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive
> (AbstractInOutSyncMessageReceiver.java:48)
> at
> org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:497)
> at
>
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(
HTTPTransportUtils.java
> :328)
> at
> org.apache.axis2.transport.http.HTTPWorker.service(HTTPWorker.java:230)
> at
>
org.apache.axis2.transport.http.server.DefaultHttpServiceProcessor.doService
(DefaultHttpServiceProcessor.java:189)
>  at
> org.apache.http.protocol.HttpService.handleRequest(HttpService.java:123)
> at
> org.apache.axis2.transport.http.server.DefaultHttpServiceProcessor.run(
DefaultHttpServiceProcessor.java:261)
> at
>
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask
(ThreadPoolExecutor.java:665)
> at
>
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run
(ThreadPoolExecutor.java
> :690)
> at java.lang.Thread.run(Thread.java:619)
>
> at org.apache.axis2.AxisFault.(AxisFault.java:159)
> ... 5 more
>
> This happens if my implementation of the service skeleton interface sets
ANY
> of the fields in the abcType object (which is itself a member of the
> abcElementDocument object returned by the service method).
>
>
> Have you seen this before?
>
>
> Many Thanks,
> Darren
>
>

Re: Axis 2 v1.1.1: disabling auto generated WSDL file

2007-03-22 Thread D P

Thanks for all your replies.

Krishna:  I followed your directions, and changed the case of the parameter.
However, I'm still observing the items I noted in #2 of my original email.
Also, I noticed that Axis2 has also removed the "parts" attribute in my
soap12:body and soap:body elements.

Amila:  I'm sorry, but I don't quite follow your response.  Are you saying
that the issue in general is known, or the specific observations I made in
#2 of my email is known?

On 3/22/07, Amila Suriarachchi <[EMAIL PROTECTED]> wrote:

On 3/21/07, D P <[EMAIL PROTECTED]> wrote:
>
> Hello all,
> When a client queries the service wsdl at http://../../serviceName?wsdl,
> I would like the service to return the wsdl which I packaged in the .aar
> file, _not_ an auto generated wsdl.  I came across a possible solution here:
> http://www.mail-archive.com/axis-user@ws.apache.org/msg25033.html.
> 1.  It appears though there are some issues with the solution.  Does
> anyone know if this works for sure?
>
> 2.  After implementing the solution in my services.xml file, i noticed 2
> things:
> a.) i've refactored out some schema into an xsd file, and import it to
> multiple wsdls.  A copy of the xsd file is packaged with each wsdl and the
> code to import the xsd uses schemaLocation=" foo.xsd".  But when I look
> at the wsdl file at http://../../serviceName?wsdl, the schemaLocation
> element value is now schemaLocation="serviceName?xsd=xsd0".  Why is this
> happening?
>
> b) When I look at the wsdl file at http://../../serviceName?wsdl, i
> notice that wsdl:portType/wsdl:operation/wsdl:input and
> wsdl:portType/wsdl:operation/wsdl:output have a wsaw:Action, whereas the
> original wsdl I packaged with the .aar does not. Why is this happening?

I think this is a known issue.
In Axis2 we use the  WSDL11ToAxisServiceBuilder to build the Axis Service
from the wsdl file. The first step it does is it process the imports.
i.e. It iterates through all the imported wsdls and  put all the imports
to the service wsdl.  Then when serializing the wsdl4jDefinition it
serializes this changed wsdl4j object. So it contains both original imports
(I removed this recently) and the imported elements.
please log a jira.

Any feedback would be appreciated.
>

--
Amila Suriarachchi,
WSO2 Inc.

Re: [Axis2] Generated client stub causes Null Pointer Exception in UTF8OutputStreamWriter.write

2007-03-22 Thread D


Thanks Davanum,

That resolved the issue on the request side, but unfortunately what looks
(to me?!) like a similar error now occurs when the server is serializing its
response.

(This is the same client and server, generated successfully using
wsdl2java).

org.apache.axis2.AxisFault: unknown
   at org.apache.axis2.description.OutInAxisOperationClient.send(
OutInAxisOperation.java:271)
   at org.apache.axis2.description.OutInAxisOperationClient.execute(
OutInAxisOperation.java:202)
   at com.xyz.generated.wsmms.send.MmsSendServiceStub.SendMms(
MmsSendServiceStub.java:184)
   at com.xyz.wsmms.test.MMSSend.execute(MMSSend.java:161)
   at com.xyz.wsmms.test.MMSSend.main(MMSSend.java:283)
Caused by: java.lang.Exception: java.lang.NullPointerException
   at com.ctc.wstx.sw.BaseNsStreamWriter.doWriteDefaultNs(
BaseNsStreamWriter.java:528)
   at com.ctc.wstx.sw.SimpleNsStreamWriter.writeDefaultNamespace(
SimpleNsStreamWriter.java:111)
   at com.ctc.wstx.sw.SimpleNsStreamWriter.writeNamespace(
SimpleNsStreamWriter.java:119)
   at org.apache.axiom.om.impl.MTOMXMLStreamWriter.writeNamespace(
MTOMXMLStreamWriter.java:146)
   at
org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serializeElement(
StreamingOMSerializer.java:243)
   at
org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serializeNode(
StreamingOMSerializer.java:76)
   at
org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serialize(
StreamingOMSerializer.java:59)
   at
org.apache.axiom.om.impl.util.OMSerializerUtil.serializeByPullStream(
OMSerializerUtil.java:473)
   at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(
OMElementImpl.java:823)
   at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(
OMElementImpl.java:848)
   at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(
OMElementImpl.java:819)
   at
org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize(
SOAPEnvelopeImpl.java:180)
   at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(
OMElementImpl.java:848)
   at org.apache.axiom.om.impl.llom.OMNodeImpl.serializeAndConsume(
OMNodeImpl.java:429)
   at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.sendUsingOutputStream
(CommonsHTTPTransportSender.java:272)
   at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke
(CommonsHTTPTransportSender.java:208)
   at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:674)
   at
org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(
AbstractInOutSyncMessageReceiver.java:48)
   at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:497)
   at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(
HTTPTransportUtils.java:328)
   at org.apache.axis2.transport.http.HTTPWorker.service(
HTTPWorker.java:230)
   at
org.apache.axis2.transport.http.server.DefaultHttpServiceProcessor.doService
(DefaultHttpServiceProcessor.java:189)
   at org.apache.http.protocol.HttpService.handleRequest(
HttpService.java:123)
   at
org.apache.axis2.transport.http.server.DefaultHttpServiceProcessor.run(
DefaultHttpServiceProcessor.java:261)
   at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask
(ThreadPoolExecutor.java:665)
   at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run
(ThreadPoolExecutor.java:690)
   at java.lang.Thread.run(Thread.java:619)

   at org.apache.axis2.AxisFault.(AxisFault.java:159)
   ... 5 more

This happens if my implementation of the service skeleton interface sets ANY
of the fields in the abcType object (which is itself a member of the
abcElementDocument object returned by the service method).


Have you seen this before?


Many Thanks,
Darren



On 3/16/07, Davanum Srinivas <[EMAIL PROTECTED]> wrote:


Please don't use sun's stax parser, please use the one in axis2 dist
which is the woodstox parser.

thanks,
dims

On 3/16/07, D <[EMAIL PROTECTED]> wrote:
> Hi Folks,
>
> Please can you helpI have generated a webservice client from a wsdl
> using wsdl2java.
>
> When the stub is used to invoke the webservice the following exception
> occurs:
>
> java.lang.NullPointerException
> at
> com.sun.xml.stream.writers.UTF8OutputStreamWriter.write(
UTF8OutputStreamWriter.java:128)
> at
> com.sun.xml.stream.writers.XMLStreamWriterImpl.writeDefaultNamespace(
XMLStreamWriterImpl.java:728)
> at
> com.sun.xml.stream.writers.XMLStreamWriterImpl.writeNamespace(
XMLStreamWriterImpl.java:914)
> at
> org.apache.axiom.om.impl.MTOMXMLStreamWriter.writeNamespace(
MTOMXMLStreamWriter.java:146)
> at
>
org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serializeElement
> (StreamingOMSerializer.java:243)
> at
> org.apache.ax

Axis 2 v1.1.1: disabling auto generated WSDL file

2007-03-21 Thread D P


Hello all,
When a client queries the service wsdl at http://../../serviceName?wsdl, I
would like the service to return the wsdl which I packaged in the .aar file,
_not_ an auto generated wsdl.  I came across a possible solution here:
http://www.mail-archive.com/axis-user@ws.apache.org/msg25033.html.
1.  It appears though there are some issues with the solution.  Does anyone
know if this works for sure?

2.  After implementing the solution in my services.xml file, i noticed 2
things:
a.) i've refactored out some schema into an xsd file, and import it to
multiple wsdls.  A copy of the xsd file is packaged with each wsdl and the
code to import the xsd uses schemaLocation="foo.xsd".  But when I look at
the wsdl file at http://../../serviceName?wsdl, the schemaLocation element
value is now schemaLocation="serviceName?xsd=xsd0".  Why is this happening?

b) When I look at the wsdl file at http://../../serviceName?wsdl, i notice
that wsdl:portType/wsdl:operation/wsdl:input and
wsdl:portType/wsdl:operation/wsdl:output have a wsaw:Action, whereas the
original wsdl I packaged with the .aar does not. Why is this happening?

Any feedback would be appreciated.

[Axis2] Generated client stub causes Null Pointer Exception in UTF8OutputStreamWriter.write

2007-03-16 Thread D


Hi Folks,

Please can you helpI have generated a webservice client from a wsdl
using wsdl2java.

When the stub is used to invoke the webservice the following exception
occurs:

java.lang.NullPointerException
   at com.sun.xml.stream.writers.UTF8OutputStreamWriter.write(
UTF8OutputStreamWriter.java:128)
   at
com.sun.xml.stream.writers.XMLStreamWriterImpl.writeDefaultNamespace(
XMLStreamWriterImpl.java:728)
   at com.sun.xml.stream.writers.XMLStreamWriterImpl.writeNamespace(
XMLStreamWriterImpl.java:914)
   at org.apache.axiom.om.impl.MTOMXMLStreamWriter.writeNamespace(
MTOMXMLStreamWriter.java:146)
   at
org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serializeElement(
StreamingOMSerializer.java:243)
   at
org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serializeNode(
StreamingOMSerializer.java:76)
   at
org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serialize(
StreamingOMSerializer.java:59)
   at
org.apache.axiom.om.impl.util.OMSerializerUtil.serializeByPullStream(
OMSerializerUtil.java:473)
   at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(
OMElementImpl.java:823)
   at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(
OMElementImpl.java:848)
   at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(
OMElementImpl.java:819)
   at
org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize(
SOAPEnvelopeImpl.java:180)
   at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(
OMElementImpl.java:848)
   at org.apache.axiom.om.impl.llom.OMNodeImpl.serializeAndConsume(
OMNodeImpl.java:419)
   at
org.apache.axis2.transport.http.SOAPOverHTTPSender$AxisSOAPRequestEntity.handleOMOutput
(SOAPOverHTTPSender.java:190)
   at
org.apache.axis2.transport.http.SOAPOverHTTPSender$AxisSOAPRequestEntity.writeRequest
(SOAPOverHTTPSender.java:232)
   at
org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeRequestBody
(EntityEnclosingMethod.java:495)
   at org.apache.commons.httpclient.HttpMethodBase.writeRequest(
HttpMethodBase.java:1973)
   at org.apache.commons.httpclient.HttpMethodBase.execute(
HttpMethodBase.java:993)
   at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry
(HttpMethodDirector.java:397)
   at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(
HttpMethodDirector.java:170)
   at org.apache.commons.httpclient.HttpClient.executeMethod(
HttpClient.java:396)
   at org.apache.commons.httpclient.HttpClient.executeMethod(
HttpClient.java:346)
   at org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(
AbstractHTTPSender.java:541)
   at org.apache.axis2.transport.http.SOAPOverHTTPSender.send(
SOAPOverHTTPSender.java:119)
   at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons
(CommonsHTTPTransportSender.java:335)
   at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke
(CommonsHTTPTransportSender.java:204)
   at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:674)
   at org.apache.axis2.description.OutInAxisOperationClient.send(
OutInAxisOperation.java:237)
   at org.apache.axis2.description.OutInAxisOperationClient.execute(
OutInAxisOperation.java:202)
   at
com.madeupnamexyz.appproviders.generated.wssms.send.SmsSendServiceStub.SendSms
(SmsSendServiceStub.java:171)

However, if I modify the stub by adding

   System.out.println("ENVELOPESTARTS:");
   try
   {
   env.serialize(System.out);
   }
   catch(javax.xml.stream.XMLStreamException ex)
   {
   System.out.println(ex.toString());
   }

   System.out.println(":ENVELOPEENDS:");

(i.e. I serialize the envelope to stdout) before the OperationClient
execute method is called by the stub, the operation completes successfully.


The WSDL and associated XSDs validate and wsdl2java gives no errors, so it
looks like env.serialize() is fixing something in the envelope!

The code using the client stub does not set anything to null and the output
from env.serialize() shows a valid soap envelope with all the expected
fields populated with valid values.


Has anyone else experienced this?

Is this a known issue?


Many Thanks,
Darren

Re: SWA in WSDL2Java generated client using xmlbeans binding

2007-03-12 Thread D


Thanks Thilina, I really appreciate your response!

The solution in the blog entry seems workable on the client side, I'm now
attempting something similar on the server side.

Best Regards,
Darren

On 3/9/07, Thilina Gunarathne <[EMAIL PROTECTED]> wrote:


>
> type="tns:MmsSendServicePortType">
>  transport="http://schemas.xmlsoap.org/soap/http "/>
> 
>   
>   
> 
> 
>   
> 
>   
>   
> 
>   
> 
>   
>   
> 
>   
>   
> 
>   
> 
>   
Axis2 does not support the above binding yet.. :(
If possible you can try using MTOM...[1]

>
> ...and with this change WSDL2Java completes successfully and the stub
method
> has the expected parameters.
>
> Please note the only difference: an additional 
> inside the , but outside the 
>
>
> My question: Can anyone please tell me if this is a proper fix?
>
> Another related questionI don't see anywhere in the resulting client
> stub class where I can set the MessageContext, or use any other
technique to
> add attachments to the requesthave I missed something?
It's not possible.. It's available only through the OperationClient API..

Have a look at the blog entry titled "Use XMLBean generated objects
with Axis2" in here [2] to figure out how to data bound only to
schemas and to use operationClient respectively...

Thilina
[1] http://ws.apache.org/axis2/1_1_1/mtom-guide.html#25
[2] http://www.bloglines.com/blog/hemapani/2006_10

>
>
> Many Thanks,
> Darren
>
> (P.S. I can provide the full WSDL and xsd files if that helps...I didn't
> include them in this post as they're pretty big)
>


--
Thilina Gunarathne
WSO2, Inc.; http://www.wso2.com/
Home page: http://webservices.apache.org/~thilina/
Blog: http://thilinag.blogspot.com/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

SWA in WSDL2Java generated client using xmlbeans binding

2007-03-08 Thread D


Hi folks,

I'm no expert in webservices, so I hope I'm not doing something really
stupid.

I'm using axis2-1.1.1 and generating a webservice client using WSDL2Java
with the following parameters:

   


When I use the following binding in my WSDL

 
   http://schemas.xmlsoap.org/soap/http"/>
   
 
 
   
 
   
 
 
   
 
   
 
 
   
 
 
   
 
   
 

...WSDL2Java completes successfully but the generated client stub method has
no parameters.

After scouring the web and finding lots of ws tutorials which describe an
identically structured binding for using Soap With Attachments,
I finally found an IBM ws tutorial showing the following binding:

 
   http://schemas.xmlsoap.org/soap/http"/>
   
 
 
   
   
 
   
 
 
   
 
   
 
 
   
 
 
   
 
   
 

...and with this change WSDL2Java completes successfully and the stub method
has the expected parameters.

Please note the only difference: an additional 
inside the , but outside the 


My question: Can anyone please tell me if this is a proper fix?

Another related questionI don't see anywhere in the resulting client
stub class where I can set the MessageContext, or use any other technique to
add attachments to the requesthave I missed something?


Many Thanks,
Darren

(P.S. I can provide the full WSDL and xsd files if that helps...I didn't
include them in this post as they're pretty big)

axis 2 v1.1.1: Obtaining SOAP response headers from Axis2 client stub

2007-03-02 Thread D P


How do I get custom SOAP headers in a response using the WSDL2Java generated
client stub?  I've researched the issue, and discovered some custom
solutions, but nothing that would appear to be auto generated via
WSDL2Java.  In addition, I checked the newsgroup archive, and ran across a
couple of posts that suggested bindings for custom headers weren't created
via WSDL2Java, but wasn't completely sure.

TIA.

RE: Set Read Timeout Programatically

2007-03-01 Thread Johnson, Larry D \(LJOHNSON\)

Great! That did the job.  Thanks!

 

Regards,

Larry Johnson

 



From: Ryan Nelsestuen [mailto:[EMAIL PROTECTED] 
Sent: Thursday, March 01, 2007 1:19 PM
To: axis-user@ws.apache.org
Subject: RE: Set Read Timeout Programatically

 

There is a setTimeOutInMilliSeconds method on the Options class if you
are using the ServiceClient...

 



From: Johnson, Larry D (LJOHNSON) [mailto:[EMAIL PROTECTED] 
Sent: Thursday, March 01, 2007 12:08 PM
To: axis-user@ws.apache.org
Subject: Set Read Timeout Programatically

 

All,

 

Is there anyway to set a requests read timeout programmatically?  I know
it can be set within the axis2.xml file; however, the value there is
fine for most requests.  I need to extend this value for only one or two
request types.

 

Regards,

Larry Johnson

Set Read Timeout Programatically

2007-03-01 Thread Johnson, Larry D \(LJOHNSON\)

All,

 

Is there anyway to set a requests read timeout programmatically?  I know
it can be set within the axis2.xml file; however, the value there is
fine for most requests.  I need to extend this value for only one or two
request types.

 

Regards,

Larry Johnson

RE: TimeZone Not Handled Properly In java.util.Date Conversions

2007-02-28 Thread Johnson, Larry D \(LJOHNSON\)

Jorge,

 

Thanks, I'll watch that JIRA... :-)

 

Regards,

Larry Johnson

 



From: Jorge Fernandez [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, February 28, 2007 9:47 AM
To: axis-user@ws.apache.org
Subject: RE: TimeZone Not Handled Properly In java.util.Date Conversions

 

Hi Larry,

I had the same problem. And I was asked to open a JIRA few days ago: AXIS2-2239

regards,

Jorge Fernandez

"Johnson, Larry D (LJOHNSON)" <[EMAIL PROTECTED]> escribió:

Amila,

 

I finally got some time to test the java.util.Data issue.  The SNAPSHOT that I 
downloaded seems to take care of the TimeZone issue I originally reported; 
however, I have found one additional issue.  The generated WSDL for the Date 
object is as follows:

 

  

 

Notice there is no 'nillable' attribute on this definition.  There are times 
when this value may be null and the SOAP message sent has that value set to 
null.  Here is a snippet from the SOAP message returned:

 

  http://www.w3.org/2001/XMLSchema-instance"; 
nil:nil="true" />

 

As stated earlier, we are deploying POJOs and generate the stubs using the 
Axis2 supplied WSDL2Java processor.

 

Any thoughts on why the auto-generated WSDL is not including the 
nillable="true" attribute for this element?

 

 

Regards,

Larry Johnson



From: Johnson, Larry D (LJOHNSON) [mailto:[EMAIL PROTECTED] 
Sent: Thursday, February 22, 2007 11:50 AM
To: axis-user@ws.apache.org
Subject: RE: TimeZone Not Handled Properly In java.util.Date Conversions

 

Amiila,

 

We are deploying our service via POJOs.  I copied a version of saaj into the 
axis2 lib directory and the problem was corrected.  I just wanted to let you 
know that the SNAPSHOT was not a complete distribution since the team moved to 
providing the SOAPEnvelope impl class.

 

I am still trying to get some time to test the Date issue and hopefully will 
get that time today.  I will let you know the results.

 

Regards,

Larry Johnson

 



From: Amila Suriarachchi [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, February 21, 2007 10:54 PM
To: axis-user@ws.apache.org
Subject: Re: TimeZone Not Handled Properly In java.util.Date Conversions

 

 

On 2/21/07, Johnson, Larry D (LJOHNSON) <[EMAIL PROTECTED]> wrote:

Amila,

 

I downloaded the axis2-SNAPSHOT.zip distribution and tried to rerun the test.  
When the server tries to return the SOAP message, I now receive the following 
exception:

 

Caused by: java.lang.NoClassDefFoundError: javax/xml/soap/SOAPEnvelope

   at 
com.arinc.afd.clfengine.processor.CommandProcessor.sendCommandToJAGS(Unknown 
Source)

   at 
com.arinc.afd.clfengine.processor.jl.GetSeatAvailabilityProcessorJL.processHostRequest

  (Unknown Source)

 

Digging into a little shows that in this SNAPSHOT, the axis2-saaj-SNAPSHOT.jar 
file no longer contains a SOAPEvelope class; however, it does contain a 
SOAPEnvelopeImpl class.  This impl class references the 
javax.xml.soap.SOAPEvelope class from the standard saaj distribution; however, 
saaj was not provided within the distribution.

 

I deployed the SNAPSHOT by downloading the archive and then exploding it.  Once 
expanded, I build the WAR file by going into the 
{path.to.axis2}/axis2-SNAPSHOT/webapp and issuing the following command: 'ant'. 
 The resulting axis2.war was built without error and was found residing in the 
'dist' directory.  The WAR file was then moved into the Tomcat 'webapps' 
directory (after removing the prior distribution).

 

Can you explain how you create your service as well. I hope you creating it 
with a POJO class. Then that 
Caused by: java.lang.NoClassDefFoundError: javax/xml/soap/SOAPEnvelope is not 
most probably relates to saaj. but it may be an OM problem. Can you please send 
your wsdl or POJO then I can have a try.


-- 
Amila Suriarachchi,
WSO2 Inc. 

 

  




LLama Gratis a cualquier PC del Mundo.
Llamadas a fijos y móviles desde 1 céntimo por minuto.
http://es.voice.yahoo.com 
<http://us.rd.yahoo.com/mail/es/tagline/messenger/*http:/es.voice.yahoo.com/>

RE: TimeZone Not Handled Properly In java.util.Date Conversions

2007-02-28 Thread Johnson, Larry D \(LJOHNSON\)

Amila,

 

I finally got some time to test the java.util.Data issue.  The SNAPSHOT
that I downloaded seems to take care of the TimeZone issue I originally
reported; however, I have found one additional issue.  The generated
WSDL for the Date object is as follows:

 

  

 

Notice there is no 'nillable' attribute on this definition.  There are
times when this value may be null and the SOAP message sent has that
value set to null.  Here is a snippet from the SOAP message returned:

 

  http://www.w3.org/2001/XMLSchema-instance";
nil:nil="true" />

 

As stated earlier, we are deploying POJOs and generate the stubs using
the Axis2 supplied WSDL2Java processor.

 

Any thoughts on why the auto-generated WSDL is not including the
nillable="true" attribute for this element?

 

 

Regards,

Larry Johnson

____

From: Johnson, Larry D (LJOHNSON) [mailto:[EMAIL PROTECTED] 
Sent: Thursday, February 22, 2007 11:50 AM
To: axis-user@ws.apache.org
Subject: RE: TimeZone Not Handled Properly In java.util.Date Conversions

 

Amiila,

 

We are deploying our service via POJOs.  I copied a version of saaj into
the axis2 lib directory and the problem was corrected.  I just wanted to
let you know that the SNAPSHOT was not a complete distribution since the
team moved to providing the SOAPEnvelope impl class.

 

I am still trying to get some time to test the Date issue and hopefully
will get that time today.  I will let you know the results.

 

Regards,

Larry Johnson

 



From: Amila Suriarachchi [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, February 21, 2007 10:54 PM
To: axis-user@ws.apache.org
Subject: Re: TimeZone Not Handled Properly In java.util.Date Conversions

 

 

On 2/21/07, Johnson, Larry D (LJOHNSON) <[EMAIL PROTECTED]> wrote:

Amila,

 

I downloaded the axis2-SNAPSHOT.zip distribution and tried to rerun the
test.  When the server tries to return the SOAP message, I now receive
the following exception:

 

Caused by: java.lang.NoClassDefFoundError: javax/xml/soap/SOAPEnvelope

   at
com.arinc.afd.clfengine.processor.CommandProcessor.sendCommandToJAGS(Unk
nown Source)

   at
com.arinc.afd.clfengine.processor.jl.GetSeatAvailabilityProcessorJL.proc
essHostRequest

  (Unknown Source)

 

Digging into a little shows that in this SNAPSHOT, the
axis2-saaj-SNAPSHOT.jar file no longer contains a SOAPEvelope class;
however, it does contain a SOAPEnvelopeImpl class.  This impl class
references the javax.xml.soap.SOAPEvelope class from the standard saaj
distribution; however, saaj was not provided within the distribution.

 

I deployed the SNAPSHOT by downloading the archive and then exploding
it.  Once expanded, I build the WAR file by going into the
{path.to.axis2}/axis2-SNAPSHOT/webapp and issuing the following command:
'ant'.  The resulting axis2.war was built without error and was found
residing in the 'dist' directory.  The WAR file was then moved into the
Tomcat 'webapps' directory (after removing the prior distribution).

 

Can you explain how you create your service as well. I hope you creating
it with a POJO class. Then that 
Caused by: java.lang.NoClassDefFoundError: javax/xml/soap/SOAPEnvelope
is not most probably relates to saaj. but it may be an OM problem. Can
you please send your wsdl or POJO then I can have a try.


-- 
Amila Suriarachchi,
WSO2 Inc.

RE: TimeZone Not Handled Properly In java.util.Date Conversions

2007-02-22 Thread Johnson, Larry D \(LJOHNSON\)

Amiila,

 

We are deploying our service via POJOs.  I copied a version of saaj into
the axis2 lib directory and the problem was corrected.  I just wanted to
let you know that the SNAPSHOT was not a complete distribution since the
team moved to providing the SOAPEnvelope impl class.

 

I am still trying to get some time to test the Date issue and hopefully
will get that time today.  I will let you know the results.

 

Regards,

Larry Johnson

 



From: Amila Suriarachchi [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, February 21, 2007 10:54 PM
To: axis-user@ws.apache.org
Subject: Re: TimeZone Not Handled Properly In java.util.Date Conversions

 

 

On 2/21/07, Johnson, Larry D (LJOHNSON) <[EMAIL PROTECTED]> wrote:

Amila,

 

I downloaded the axis2-SNAPSHOT.zip distribution and tried to rerun the
test.  When the server tries to return the SOAP message, I now receive
the following exception:

 

Caused by: java.lang.NoClassDefFoundError: javax/xml/soap/SOAPEnvelope

   at
com.arinc.afd.clfengine.processor.CommandProcessor.sendCommandToJAGS(Unk
nown Source)

   at
com.arinc.afd.clfengine.processor.jl.GetSeatAvailabilityProcessorJL.proc
essHostRequest

  (Unknown Source)

 

Digging into a little shows that in this SNAPSHOT, the
axis2-saaj-SNAPSHOT.jar file no longer contains a SOAPEvelope class;
however, it does contain a SOAPEnvelopeImpl class.  This impl class
references the javax.xml.soap.SOAPEvelope class from the standard saaj
distribution; however, saaj was not provided within the distribution.

 

I deployed the SNAPSHOT by downloading the archive and then exploding
it.  Once expanded, I build the WAR file by going into the
{path.to.axis2}/axis2-SNAPSHOT/webapp and issuing the following command:
'ant'.  The resulting axis2.war was built without error and was found
residing in the 'dist' directory.  The WAR file was then moved into the
Tomcat 'webapps' directory (after removing the prior distribution).

 

Can you explain how you create your service as well. I hope you creating
it with a POJO class. Then that 
Caused by: java.lang.NoClassDefFoundError: javax/xml/soap/SOAPEnvelope
is not most probably relates to saaj. but it may be an OM problem. Can
you please send your wsdl or POJO then I can have a try.


-- 
Amila Suriarachchi,
WSO2 Inc.

RE: TimeZone Not Handled Properly In java.util.Date Conversions

2007-02-21 Thread Johnson, Larry D \(LJOHNSON\)

Amila,

 

I downloaded the axis2-SNAPSHOT.zip distribution and tried to rerun the
test.  When the server tries to return the SOAP message, I now receive
the following exception:

 

Caused by: java.lang.NoClassDefFoundError: javax/xml/soap/SOAPEnvelope

   at
com.arinc.afd.clfengine.processor.CommandProcessor.sendCommandToJAGS(Unk
nown Source)

   at
com.arinc.afd.clfengine.processor.jl.GetSeatAvailabilityProcessorJL.proc
essHostRequest

  (Unknown Source)

 

Digging into a little shows that in this SNAPSHOT, the
axis2-saaj-SNAPSHOT.jar file no longer contains a SOAPEvelope class;
however, it does contain a SOAPEnvelopeImpl class.  This impl class
references the javax.xml.soap.SOAPEvelope class from the standard saaj
distribution; however, saaj was not provided within the distribution.

 

I deployed the SNAPSHOT by downloading the archive and then exploding
it.  Once expanded, I build the WAR file by going into the
{path.to.axis2}/axis2-SNAPSHOT/webapp and issuing the following command:
'ant'.  The resulting axis2.war was built without error and was found
residing in the 'dist' directory.  The WAR file was then moved into the
Tomcat 'webapps' directory (after removing the prior distribution).

 

Do I need to add my version of saaj into the axis2/WEB-INF/lib
directory?  Will the SNAPSHOT be updated to include the version of saaj
you are expecting to use?  Shouldn't the WAR file be self-contained so
that deployment is simply dropping it into Tomcat?

 

Regards,

Larry Johnson



From: Amila Suriarachchi [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 20, 2007 12:32 AM
To: axis-user@ws.apache.org
Subject: Re: TimeZone Not Handled Properly In java.util.Date Conversions

 

 

On 2/20/07, Johnson, Larry D (LJOHNSON) <[EMAIL PROTECTED]> wrote:

Amila,

 

How do I set the nillable true on automatically generated WSDL from a
deployed POJO?


this should be automatically set. try with the latest nightly build.

 

Regards,

Larry Johnson








-- 
Amila Suriarachchi,
WSO2 Inc.

RE: TimeZone Not Handled Properly In java.util.Date Conversions

2007-02-19 Thread Johnson, Larry D \(LJOHNSON\)

Amila,

I have just downloaded the Axis2 v1.1.1-SNAPSHOT version and installed
it.  This version has the same issue.

Regards,

Larry Johnson

From: Amila Suriarachchi [mailto:[EMAIL PROTECTED] 
Sent: Thursday, February 15, 2007 11:48 PM
To: axis-user@ws.apache.org
Subject: Re: TimeZone Not Handled Properly In java.util.Date Conversions

I recently fix this issue with adb. please check with a nightly build.
there i used the SimpleDateFormatter to pares the date values correctly
with the time zones.

On 2/16/07, Dennis Sosnoski <[EMAIL PROTECTED]> wrote:

Hi Larry,

You're correct on your assumptions, that if a Calendar is being returned
it should have a consistent time value and time zone. In this case the
time zone of the Calendar should be set to UTC. That said, there are 
some seriously warped issues involved - Calendar *always* works with
time zones, while xsd:dateTimes either use UTC times or times with no
zone information (where the latter have basically a half-day uncertainty

factor). 

 Can you pleas explain this bit? in xml spec the lexical representation
of the datetime is
'-'?  '-' mm '-' dd 'T' hh ':' mm ':' ss ('.' s+)? (zz)? and
this (z)? part is either be Z (means GMT) or the actual time zone
(eg +0530) 

xsd:dateTimes do not support time zones in the Java sense at
all.

Can't we use the simpleDateFormatter to parse the dates correctly with
timezones? 
Dennis can you please check the logic I have used in convertToDateTime
method in org.apache.axis2.databinding.utils.ConverterUtil to parse the
date? 

The inappropriate use of Calendar for XML dateTime values in
Java is a 
long-standing issue that goes back to JAX-RPC days. Calendar
just
doesn't work for dateTimes, which is why recent versions of Java
have an
added javax.xml.datatype.XMLGregorianCalendar class. Ironically,
the 
java.util.Date class *is* a direct representation of standard
dateTime
values, as long as you don't need sub-millisecond precision -
but
because everyone got brainwashed into working with Calendar in
Java
that's also what XML code generally uses.

The JiBX data binding support uses java.util.Date as the
standard
xsd:dateTime representation, so one solution would be to switch
to using
JiBX. I believe the JiBX linkage code generated by WSDL2Java
also 
handles the xsi:nillable issue properly, only generating this
when
allowed by the schema and throwing an exception if a required
value is null.

Aside from that, I suggest you enter bug reports in the Axis2
Jira on 
these issues.

- Dennis

Dennis M. Sosnoski
SOA and Web Services in Java
Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117

Johnson, Larry D (LJOHNSON) wrote:
>
> I did not specify what platform we are using. We are currently
using 
> Axis2 v1.1, Java v1.5 and Tomcat 5.5.20.
>
> I have also run a similar test using the .NET framework. The
client
> receives a DateTime object from the stubs. On .NET, the value
returned
> to the client is correct for the current timezone. This
appears to be 
> an issue in the generated Java stub classes.
>
> Also, I saw one additional oddity. As reported below, the WSDL
> generated element for the java.util.Date element is as
follows:
>
>  
>
> Even though I have not specified that this should be a
required field,
> it does not have an attribute of nillable="true"; however the
SOAP
> message being returned to the client has the form: 
>
> http://www.w3.org/2001/XMLSchema-instance";
> nil:nil="true" />
>
> The nillable attribute is set true here. On the client side,
the 
> following exception is received:
>
> _java.lang.RuntimeException_:
_java.lang.NumberFormatException_
>
> at
>
com.arinc.afd.clfengine.client.jl.JLCommandProcessorServiceStub.fromOM(U
nknown 
> Source)
>
> at
>
com.arinc.afd.clfengine.client.jl.JLCommandProcessorServiceStub.processL
ocateBooking(Unknown
> Source)
>
> at
> com.arinc.afd.jal.webapp.CLFTestClient.jlLocateBooking
(_CLFTestClient.java:101_)
>
> at
com.arinc.afd.jal.webapp.CLFTestClient.main(_CLFTestClient.java:315_)
>
> Caused by: _java.la

RE: TimeZone Not Handled Properly In java.util.Date Conversions

2007-02-19 Thread Johnson, Larry D \(LJOHNSON\)

Amila,

 

How do I set the nillable true on automatically generated WSDL from a
deployed POJO?

 

Regards,

Larry Johnson



From: Amila Suriarachchi [mailto:[EMAIL PROTECTED] 
Sent: Thursday, February 15, 2007 11:59 PM
To: axis-user@ws.apache.org
Subject: Re: TimeZone Not Handled Properly In java.util.Date Conversions

 

 

On 2/16/07, Johnson, Larry D (LJOHNSON) <[EMAIL PROTECTED]> wrote:

I did not specify what platform we are using.  We are currently using
Axis2 v1.1, Java v1.5 and Tomcat 5.5.20.

 

I have also run a similar test using the .NET framework.  The client
receives a DateTime object from the stubs.  On .NET, the value returned
to the client is correct for the current timezone.  This appears to be
an issue in the generated Java stub classes.

 

Also, I saw one additional oddity. As reported below, the WSDL generated
element for the java.util.Date element is as follows:

 

   

 

Even though I have not specified that this should be a required field,
it does not have an attribute of nillable="true"; however the SOAP
message being returned to the client has the form:

 

http://www.w3.org/2001/XMLSchema-instance";
nil:nil="true" />

 

The nillable attribute is set true here.  On the client side, the
following exception is received:

 

java.lang.RuntimeException : java.lang.NumberFormatException 

   at
com.arinc.afd.clfengine.client.jl.JLCommandProcessorServiceStub.fromOM(U
nknown Source)

   at
com.arinc.afd.clfengine.client.jl.JLCommandProcessorServiceStub.processL
ocateBooking(Unknown Source)

   at
com.arinc.afd.jal.webapp.CLFTestClient.jlLocateBooking(CLFTestClient.jav
a:101 )

   at
com.arinc.afd.jal.webapp.CLFTestClient.main(CLFTestClient.java:315 )

Caused by: java.lang.NumberFormatException

   at
org.apache.axis2.databinding.utils.ConverterUtil.convertToDateTime(Conve
rterUtil.java:499 )

   at
com.arinc.afd.clfengine.client.jl.JLCommandProcessorServiceStub$Flight$F
actory.parse(Unknown Source)

 

Any thoughts?


ADB  supports nillable attribute .  can you please send your wsdl (set
the nillable true) and the soap request you got from the .NET server? 

 

Regards,

Larry Johnson

 

 


____


From: Johnson, Larry D (LJOHNSON) [mailto:[EMAIL PROTECTED] 
Sent: Thursday, February 15, 2007 11:59 AM
To: axis-user@ws.apache.org
Subject: TimeZone Not Handled Properly In java.util.Date
Conversions

 

It seems the conversions of the java.util.Date class are not
being handled properly.  I have defined a server return value of a
java.util.Date.  The WSDL automatically generated for that value is as
follows:

 

  

 

The client stub is generated using the provided WSDL2Java.  The
client stub returns a java.util.Calendar object for this value.  So far
all is well.  The problem comes in when you start looking into the
handling of the TimeZone from server to client.  Lets say both client
and server are within the "Central Standard Time" zone.  When the server
provides the Date object to the POJO interface, the time is
"1970-01-01T23:55:00.000".  Axis2 then converts that time to a GMT time.
The SOAP message contains "1970-01-02T05:55:00.000Z".  Again all is
well.  When the client gets the Calendar object from the stub classes,
the value is: 01/02/1970 11:55:00 Greenwich Mean Time.  The time value
is incorrect for the TimeZone indicate; however, it is correct for the
local TimeZone.

 

The client simply performs the following:

 

responeData.getDepartureTime();

 

Am I missing something here?  Should the returned Calendar
either keep the time consistent with GMT or convert the time to local
time while changing the TimeZone to indicate the local TimeZone?

 

Regards,

Larry Johnson




-- 
Amila Suriarachchi,
WSO2 Inc.

RE: TimeZone Not Handled Properly In java.util.Date Conversions

I did not specify what platform we are using.  We are currently using
Axis2 v1.1, Java v1.5 and Tomcat 5.5.20.

 

I have also run a similar test using the .NET framework.  The client
receives a DateTime object from the stubs.  On .NET, the value returned
to the client is correct for the current timezone.  This appears to be
an issue in the generated Java stub classes.

 

Also, I saw one additional oddity. As reported below, the WSDL generated
element for the java.util.Date element is as follows:

 

   

 

Even though I have not specified that this should be a required field,
it does not have an attribute of nillable="true"; however the SOAP
message being returned to the client has the form:

 

http://www.w3.org/2001/XMLSchema-instance";
nil:nil="true" />

 

The nillable attribute is set true here.  On the client side, the
following exception is received:

 

java.lang.RuntimeException: java.lang.NumberFormatException

   at
com.arinc.afd.clfengine.client.jl.JLCommandProcessorServiceStub.fromOM(U
nknown Source)

   at
com.arinc.afd.clfengine.client.jl.JLCommandProcessorServiceStub.processL
ocateBooking(Unknown Source)

   at
com.arinc.afd.jal.webapp.CLFTestClient.jlLocateBooking(CLFTestClient.jav
a:101)

   at
com.arinc.afd.jal.webapp.CLFTestClient.main(CLFTestClient.java:315)

Caused by: java.lang.NumberFormatException

   at
org.apache.axis2.databinding.utils.ConverterUtil.convertToDateTime(Conve
rterUtil.java:499)

   at
com.arinc.afd.clfengine.client.jl.JLCommandProcessorServiceStub$Flight$F
actory.parse(Unknown Source)

 

Any thoughts?

 

Regards,

Larry Johnson

 

 

____

From: Johnson, Larry D (LJOHNSON) [mailto:[EMAIL PROTECTED] 
Sent: Thursday, February 15, 2007 11:59 AM
To: axis-user@ws.apache.org
Subject: TimeZone Not Handled Properly In java.util.Date Conversions

 

It seems the conversions of the java.util.Date class are not being
handled properly.  I have defined a server return value of a
java.util.Date.  The WSDL automatically generated for that value is as
follows:

 

  

 

The client stub is generated using the provided WSDL2Java.  The client
stub returns a java.util.Calendar object for this value.  So far all is
well.  The problem comes in when you start looking into the handling of
the TimeZone from server to client.  Lets say both client and server are
within the "Central Standard Time" zone.  When the server provides the
Date object to the POJO interface, the time is
"1970-01-01T23:55:00.000".  Axis2 then converts that time to a GMT time.
The SOAP message contains "1970-01-02T05:55:00.000Z".  Again all is
well.  When the client gets the Calendar object from the stub classes,
the value is: 01/02/1970 11:55:00 Greenwich Mean Time.  The time value
is incorrect for the TimeZone indicate; however, it is correct for the
local TimeZone.

 

The client simply performs the following:

 

responeData.getDepartureTime();

 

Am I missing something here?  Should the returned Calendar either keep
the time consistent with GMT or convert the time to local time while
changing the TimeZone to indicate the local TimeZone?

 

Regards,

Larry Johnson

TimeZone Not Handled Properly In java.util.Date Conversions

It seems the conversions of the java.util.Date class are not being
handled properly.  I have defined a server return value of a
java.util.Date.  The WSDL automatically generated for that value is as
follows:

 

  

 

The client stub is generated using the provided WSDL2Java.  The client
stub returns a java.util.Calendar object for this value.  So far all is
well.  The problem comes in when you start looking into the handling of
the TimeZone from server to client.  Lets say both client and server are
within the "Central Standard Time" zone.  When the server provides the
Date object to the POJO interface, the time is
"1970-01-01T23:55:00.000".  Axis2 then converts that time to a GMT time.
The SOAP message contains "1970-01-02T05:55:00.000Z".  Again all is
well.  When the client gets the Calendar object from the stub classes,
the value is: 01/02/1970 11:55:00 Greenwich Mean Time.  The time value
is incorrect for the TimeZone indicate; however, it is correct for the
local TimeZone.

 

The client simply performs the following:

 

responeData.getDepartureTime();

 

Am I missing something here?  Should the returned Calendar either keep
the time consistent with GMT or convert the time to local time while
changing the TimeZone to indicate the local TimeZone?

 

Regards,

Larry Johnson

RE: Incorrect Mapping For java.sql.Date

Done:

https://issues.apache.org/jira/browse/AXIS2-2189

Thanks,
Larry

-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED] 
Sent: Thursday, February 15, 2007 7:39 AM
To: axis-user@ws.apache.org
Subject: Re: Incorrect Mapping For java.sql.Date

Here - https://issues.apache.org/jira/browse/AXIS2 (You'll need to
create an id for yourself first).

thanks,
dims

On 2/15/07, Johnson, Larry D (LJOHNSON) <[EMAIL PROTECTED]> wrote:
> Deepal,
>
> I am new to Axis2, so could you guide me on where to create the JIRA?
> Also, I assume since the java.sql.Date class is not supported
> java.sql.Time is also not supported?
>
> Thanks,
> Larry
>
> -Original Message-
> From: Deepal Jayasinghe [mailto:[EMAIL PROTECTED]
> Sent: Thursday, February 15, 2007 12:30 AM
> To: axis-user@ws.apache.org
> Subject: Re: Incorrect Mapping For java.sql.Date
>
> Hi Johnson;
>
> JIRA please , we handle java.util.Date but not java.sql.Date at the
> moment.
>
> Thanks
> Deepal
>
> > It seems the WSDL java.sql.Date object is not being generated
properly
> > within Axis2 v1.1. The generate WSDL, viewed from the deployment of
> > the service, shows a date definition as follows:
> >
> >  > elementFormDefault="qualified"
targetNamespace="http://sql.java/xsd";>
> >
> > http://calendar.util.sun/xsd"/>
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> >  > type="ax27:BaseCalendar$Date"/>
> >
> > 
> >
> > 
> >
> > 
> >
> >  > type="ax27:BaseCalendar"/>
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> > Seems reasonable and note the type attribute "ax23:Date". Now the
> > definition of the complex type that uses the Date object is as
> follows:
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> > Also looks reasonable except for one thing. The type specified for
the
> > Date object is defined as "ax28:Date". There is no match within the
> > generated WSDL for this type.
> >
> > When populating the complex type, I use the Date object provided as
> > part of the generated stub for the dateOfBirth value. When this is
> > deserialized into the java.sql.Data object on the server side (keep
in
> > mind the java.sql.Date object was used to generate the WSDL) I
receive
> > the following error on the server side:
> >
> > org.apache.axis2.AxisFault: java.sql.Date; nested exception is:
> >
> > _java.lang.InstantiationException_: java.sql.Date
> >
> > at
> >
>
org.apache.axis2.engine.DefaultObjectSupplier.getObject(_DefaultObjectSu
> pplier.java:28_)
> >
> > at
> >
>
org.apache.axis2.databinding.utils.BeanUtil.deserialize(_BeanUtil.java:2
> 61_)
> >
> > at
> >
>
org.apache.axis2.databinding.utils.BeanUtil.deserialize(_BeanUtil.java:2
> 91_)
> >
> > at
> >
>
org.apache.axis2.databinding.utils.BeanUtil.processObject(_BeanUtil.java
> :549_)
> >
> > at
> >
>
org.apache.axis2.databinding.utils.BeanUtil.ProcessElement(_BeanUtil.jav
> a:499_)
> >
> > at
> >
>
org.apache.axis2.databinding.utils.BeanUtil.deserialize(_BeanUtil.java:4
> 38_)
> >
> > at
> >
>
org.apache.axis2.rpc.receivers.RPCUtil.processRequest(_RPCUtil.java:109_
> )
> >
> > at
> >
>
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(_R
> PCMessageReceiver.java:116_)
> >
> > at
> >
>
org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(_Abs
> tractInOutSyncMessageReceiver.java:39_)
> >
> > at org.apache.axis2.engine.AxisEngine.receive(_AxisEngine.java:493_)
> >
> > at
> >
>
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostReques
> t(_HTTPTransportUtils.java:319_)
> >
> > at
> >
>
org.apache.axis2.transport.http.AxisServlet.doPost(_AxisServlet.java:247
> _)
> >
> > at javax.servlet.http.HttpServlet.service(_HttpServlet.java:709_)
> >
> > at javax.servlet.http.HttpServlet.service(_HttpServlet.java:802_)
> >
> > at
> >

RE: Incorrect Mapping For java.sql.Date

Deepal,

I am new to Axis2, so could you guide me on where to create the JIRA?
Also, I assume since the java.sql.Date class is not supported
java.sql.Time is also not supported?

Thanks,
Larry

-Original Message-
From: Deepal Jayasinghe [mailto:[EMAIL PROTECTED] 
Sent: Thursday, February 15, 2007 12:30 AM
To: axis-user@ws.apache.org
Subject: Re: Incorrect Mapping For java.sql.Date

Hi Johnson;

JIRA please , we handle java.util.Date but not java.sql.Date at the
moment.

Thanks
Deepal

> It seems the WSDL java.sql.Date object is not being generated properly
> within Axis2 v1.1. The generate WSDL, viewed from the deployment of
> the service, shows a date definition as follows:
>
>  elementFormDefault="qualified" targetNamespace="http://sql.java/xsd";>
>
> http://calendar.util.sun/xsd"/>
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
>  type="ax27:BaseCalendar$Date"/>
>
> 
>
> 
>
> 
>
>  type="ax27:BaseCalendar"/>
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
> Seems reasonable and note the type attribute "ax23:Date". Now the
> definition of the complex type that uses the Date object is as
follows:
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
> Also looks reasonable except for one thing. The type specified for the
> Date object is defined as "ax28:Date". There is no match within the
> generated WSDL for this type.
>
> When populating the complex type, I use the Date object provided as
> part of the generated stub for the dateOfBirth value. When this is
> deserialized into the java.sql.Data object on the server side (keep in
> mind the java.sql.Date object was used to generate the WSDL) I receive
> the following error on the server side:
>
> org.apache.axis2.AxisFault: java.sql.Date; nested exception is:
>
> _java.lang.InstantiationException_: java.sql.Date
>
> at
>
org.apache.axis2.engine.DefaultObjectSupplier.getObject(_DefaultObjectSu
pplier.java:28_)
>
> at
>
org.apache.axis2.databinding.utils.BeanUtil.deserialize(_BeanUtil.java:2
61_)
>
> at
>
org.apache.axis2.databinding.utils.BeanUtil.deserialize(_BeanUtil.java:2
91_)
>
> at
>
org.apache.axis2.databinding.utils.BeanUtil.processObject(_BeanUtil.java
:549_)
>
> at
>
org.apache.axis2.databinding.utils.BeanUtil.ProcessElement(_BeanUtil.jav
a:499_)
>
> at
>
org.apache.axis2.databinding.utils.BeanUtil.deserialize(_BeanUtil.java:4
38_)
>
> at
>
org.apache.axis2.rpc.receivers.RPCUtil.processRequest(_RPCUtil.java:109_
)
>
> at
>
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(_R
PCMessageReceiver.java:116_)
>
> at
>
org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(_Abs
tractInOutSyncMessageReceiver.java:39_)
>
> at org.apache.axis2.engine.AxisEngine.receive(_AxisEngine.java:493_)
>
> at
>
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostReques
t(_HTTPTransportUtils.java:319_)
>
> at
>
org.apache.axis2.transport.http.AxisServlet.doPost(_AxisServlet.java:247
_)
>
> at javax.servlet.http.HttpServlet.service(_HttpServlet.java:709_)
>
> at javax.servlet.http.HttpServlet.service(_HttpServlet.java:802_)
>
> at
>
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(_Applic
ationFilterChain.java:252_)
>
> at
>
org.apache.catalina.core.ApplicationFilterChain.doFilter(_ApplicationFil
terChain.java:173_)
>
> at
>
org.apache.catalina.core.StandardWrapperValve.invoke(_StandardWrapperVal
ve.java:213_)
>
> at
>
org.apache.catalina.core.StandardContextValve.invoke(_StandardContextVal
ve.java:178_)
>
> at
>
org.apache.catalina.core.StandardHostValve.invoke(_StandardHostValve.jav
a:126_)
>
> at
>
org.apache.catalina.valves.ErrorReportValve.invoke(_ErrorReportValve.jav
a:105_)
>
> 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:8
69_)
>
> at
>
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.proc
essConnection(_Http11BaseProtocol.java:664_)
>
> at
>
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(_PoolTcpEndpoin
t.java:527_)
>
> at
>
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(_LeaderFollo
werWorkerThread.java:80_)
>
> at
>
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(_ThreadPoo
l.java:684_)
>
> at java.lang.Thread.run(Unknown Source)
>
> Is the above correct? Am I doing something wrong? Is there a trick
> that I am not seeing?
>
> Regards,
>
> Larry Johnson
>

-- 
Thanks,
Deepal

"The highest tower is built one brick at a time"



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTEC

Incorrect Mapping For java.sql.Date

2007-02-14 Thread Johnson, Larry D \(LJOHNSON\)

It seems the WSDL java.sql.Date object is not being generated properly
within Axis2 v1.1.  The generate WSDL, viewed from the deployment of the
service, shows a date definition as follows:

 

http://sql.java/xsd";>

  http://calendar.util.sun/xsd"/>

  



  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  



  



 

Seems reasonable and note the type attribute "ax23:Date".  Now the
definition of the complex type that uses the Date object is as follows:

 



  























  



 

Also looks reasonable except for one thing.  The type specified for the
Date object is defined as "ax28:Date".  There is no match within the
generated WSDL for this type.

 

When populating the complex type, I use the Date object provided as part
of the generated stub for the dateOfBirth value.  When this is
deserialized into the java.sql.Data object on the server side (keep in
mind the java.sql.Date object was used to generate the WSDL) I receive
the following error on the server side:

 

org.apache.axis2.AxisFault: java.sql.Date; nested exception is: 

   java.lang.InstantiationException: java.sql.Date

   at
org.apache.axis2.engine.DefaultObjectSupplier.getObject(DefaultObjectSup
plier.java:28)

   at
org.apache.axis2.databinding.utils.BeanUtil.deserialize(BeanUtil.java:26
1)

   at
org.apache.axis2.databinding.utils.BeanUtil.deserialize(BeanUtil.java:29
1)

   at
org.apache.axis2.databinding.utils.BeanUtil.processObject(BeanUtil.java:
549)

   at
org.apache.axis2.databinding.utils.BeanUtil.ProcessElement(BeanUtil.java
:499)

   at
org.apache.axis2.databinding.utils.BeanUtil.deserialize(BeanUtil.java:43
8)

   at
org.apache.axis2.rpc.receivers.RPCUtil.processRequest(RPCUtil.java:109)

   at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RP
CMessageReceiver.java:116)

   at
org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(Abst
ractInOutSyncMessageReceiver.java:39)

   at
org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:493)

   at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostReques
t(HTTPTransportUtils.java:319)

   at
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:247)

   at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)

   at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)

   at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
tionFilterChain.java:252)

   at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
erChain.java:173)

   at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv
e.java:213)

   at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv
e.java:178)

   at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java
:126)

   at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java
:105)

   at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.
java:107)

   at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:1
48)

   at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:86
9)

   at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.proc
essConnection(Http11BaseProtocol.java:664)

   at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint
.java:527)

   at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollow
erWorkerThread.java:80)

   at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool
.java:684)

   at java.lang.Thread.run(Unknown Source)

 

Is the above correct?  Am I doing something wrong?  Is there a trick
that I am not seeing?

 

Regards,

Larry Johnson

RE: Axis2 1.1.1 - Unexpected subelement and heritage

2007-02-14 Thread Johnson, Larry D \(LJOHNSON\)

I know all must be busy with continued development; however, this IMOHO
is a big issue.  Inheritance on the outbound side of the server is much
needed for all the obvious reasons.  Is there any timeline on when this
issue may be resolved?  We are specifically using ADB and see the same
sort of behavior.  I have not posted anything about it since it is a
known issue.  Again, just wondering about he time line for a fix.

BTW: Keep up the good work.

Thanks,
Larry

-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, February 14, 2007 7:41 AM
To: axis-user@ws.apache.org
Subject: Re: Axis2 1.1.1 - Unexpected subelement and heritage

Oliver,

This is a known issue. But i'd like you to open a new JIRA issue with
your sample code and the soap messages traces (if any). So that we can
make sure it is fixed when we fix the known issue.

thanks,
dims

On 2/14/07, Olivier DUGAST <[EMAIL PROTECTED]> wrote:
>
> Hi all,
>
> I try to use Axis2 with my service. One of my methods return a tab of
> BeanB class which extend an other BeanA class. But the SOAP response
> return only the attribute of BeanB without the attribute of BeanA as
you
> can see below :
>
>  extract of wsdl -
> 
>   name="BeanB">   nillable="true" type="xs:string" />  nillable="true" type="xs:string" />  
> ...
> 
> 
> 
>  type="ns0:BeanB" />   
> ...
> --
>
>
>  SOAP response of getBeanBTab webmethod  without attribute A -
>   xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";>
>   
>   
> http://server.me.com/xsd";>
>   
> http://bean.service.server.me.com/xsd";>attrB
> BeanB
>   
> 
>   
> 
> --
>
> When i try to invoke the method "getBeanBTab" as you can see above, no
> attributeA return , i catch this Exception :
> --- stack trace ---
> Exception in thread "main" java.lang.RuntimeException:
> java.lang.RuntimeException: Unexpected subelement attributeB
> at
> com.me.client.ServiceTestStub.fromOM(ServiceTestStub.java:3720)
> at
> com.me.client.ServiceTestStub.getBeanBTab(ServiceTestStub.java:365)
> at
> com.me.client.ServiceTestClient.getBeanBTab(ServiceTestClient.java:61)
> at
>
com.me.client.ServiceTestClientMain.main(ServiceTestClientMain.java:11)
> Caused by: java.lang.RuntimeException: Unexpected subelement
attributeB
> at
>
com.me.client.ServiceTestStub$BeanB$Factory.parse(ServiceTestStub.java:1
> 304)
> at
>
com.me.client.ServiceTestStub$GetBeanBTabResponse$Factory.parse(ServiceT
> estStub.java:3592)
> at
> com.me.client.ServiceTestStub.fromOM(ServiceTestStub.java:3714)
> ... 3 more
> --
>
>
>
> Any idea?
>
> Please let me know how to solve this issue?
>
> Thanks,
> Olivier.
>
>
>
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services
Developers

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

java2wsdl and optional (nillable) method arguments

2006-12-07 Thread D . Kreft


Using Axis 1.4 here...

I'd like my WSDL (generated with Java2WSDL) to represent some of the
arguments to some of my methods as optional (nillable). Is this
possible, or is this only something one can do by going the other
direction--WSDL-to-Java?

-dan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Java 5 Enum Support

2006-12-07 Thread Johnson, Larry D \(LJOHNSON\)

Can anyone give me guidance on this question?

 

Does Axis2 support the Java 1.5 'enum' keyword?

If not, what is the recommended Axis2 "best practices" for enumerated
types?

  Is it the use of the "type safe enum" pattern, or something else?

 

Any help would be appreciated.

Again, thanks for any response.

 

____

From: Johnson, Larry D (LJOHNSON) [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, December 06, 2006 9:40 AM
To: axis-user@ws.apache.org
Subject: Java 5 Enum Support

 

I am new to Axis2 and am trying to develop a web service using Axis 2
v1.1, Java 1.5 and the POJO approach.  The service POJO that I developed
uses the keyword "enum" for many different attribute "types".  I am able
to successfully generate WSDL from the POJO; however, when I try to
create the client, via "wsdl2java" I receive the following errors:

 

Exception in thread "main"
org.apache.axis2.wsdl.codegen.CodeGenerationException:
java.lang.RuntimeException: java.lang.reflect.InvocationTargetException

[snip]

Caused by: java.lang.RuntimeException: org.apache.xmlbeans.XmlException:
error: Invalid QName value: Localname not a valid NCName in
'ax241:CLFService$CLFCommandType'

[snip]

 

I have tried several tricks to make the enum more visible to the
service; however, in all cases I continue to receive the above error
(only the name of the invalid NCName changes).

 

My question is; does Axis2 v1.1 support the Java 1.5 "enum" keyword?  If
so, how do I make the WSDL generator recognize it?  I have seen several
posts in the mailing-list archives about Axis v1.3; however, none since
Axis2 was released.  Most of the Axis1 posts were requesting this
feature.  Has this been introduced?  Also, if "enum" is not supported,
do you recommend using the "type safe enum pattern" to solve this
problem?  I have also seen posts where people were having problems with
that pattern as well.  What is the recommended Axis2 "best practices"
approach to solve this?

 

Many thanks for the response.

Java 5 Enum Support

2006-12-06 Thread Johnson, Larry D \(LJOHNSON\)

I am new to Axis2 and am trying to develop a web service using Axis 2
v1.1, Java 1.5 and the POJO approach.  The service POJO that I developed
uses the keyword "enum" for many different attribute "types".  I am able
to successfully generate WSDL from the POJO; however, when I try to
create the client, via "wsdl2java" I receive the following errors:

 

Exception in thread "main"
org.apache.axis2.wsdl.codegen.CodeGenerationException:
java.lang.RuntimeException: java.lang.reflect.InvocationTargetException

[snip]

Caused by: java.lang.RuntimeException: org.apache.xmlbeans.XmlException:
error: Invalid QName value: Localname not a valid NCName in
'ax241:CLFService$CLFCommandType'

[snip]

 

I have tried several tricks to make the enum more visible to the
service; however, in all cases I continue to receive the above error
(only the name of the invalid NCName changes).

 

My question is; does Axis2 v1.1 support the Java 1.5 "enum" keyword?  If
so, how do I make the WSDL generator recognize it?  I have seen several
posts in the mailing-list archives about Axis v1.3; however, none since
Axis2 was released.  Most of the Axis1 posts were requesting this
feature.  Has this been introduced?  Also, if "enum" is not supported,
do you recommend using the "type safe enum pattern" to solve this
problem?  I have also seen posts where people were having problems with
that pattern as well.  What is the recommended Axis2 "best practices"
approach to solve this?

 

Many thanks for the response.

Re: Best way to log service method accesses?

2006-12-05 Thread D . Kreft

Ne'er mind...I got this figured out based upon a response to another question.

The solution is to create a handler that inherits from BasicHandler. :-)

-dan

On 12/5/06, D. Kreft <[EMAIL PROTECTED]> wrote:

On 12/5/06, David Illsley <[EMAIL PROTECTED]> wrote:

> If this is in Axis2 I'd suggest a handler inserted after the dispatch
> phase in which case you can get the operation name from the
> AxisOperation which in turn you can obtain from the MessageContext. In
> general the SOAPAction can't and shouldn't be relied upon.

Sorry, should have mentioned in my original e-mail that this is under
Axis 1.4. Is there a sexy way to do what I need in that version of
Axis?

-dan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Best way to log service method accesses?

2006-12-05 Thread D . Kreft


On 12/5/06, David Illsley <[EMAIL PROTECTED]> wrote:


If this is in Axis2 I'd suggest a handler inserted after the dispatch
phase in which case you can get the operation name from the
AxisOperation which in turn you can obtain from the MessageContext. In
general the SOAPAction can't and shouldn't be relied upon.


Sorry, should have mentioned in my original e-mail that this is under
Axis 1.4. Is there a sexy way to do what I need in that version of
Axis?

-dan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Best way to log service method accesses?

2006-12-05 Thread D . Kreft


I'm setting up a table in my database to log accesses to my service.
I'm grabbing the username, client host and script name from the SOAP
header, but I'd also like to log the name of the method called. What's
the best way to do this? Can the SOAPAction HTTP header be reliably
counted on for this task, or must I pick apart the SOAP body?

Or better yet, is there a pre-fabricated solution I could drop into my
service to take care of this for me? Surely this has been done before.
:-)

-dan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Header info in Axis 1.x

2006-11-27 Thread D . Kreft


Is it possible to retrieve header SOAP header information under Axis1?
There's only one e-mail in the archives that seems appropriate, but it
was never answered
(http://marc.theaimsgroup.com/?l=axis-user&m=116072386027359&w=2). I
know this can be done under Axis2, but I'm not in a position at
present to make that switch. Pointers to example source code or
existing documentation would be much appreciated.

Another question I should probably ask, just as a sanity-checking
measure, is whether it's appropriate to do what I'm thinking about
doing. My primary web service needs to talk to one or more "helper"
web services, and from time to time it might be useful or even
necessary to force my primary service to consult a non-default
"helper" service when debugging problems or testing new features. My
thought was to pass along an override URL for the "helper" service in
the SOAP header. Does this make sense? It sure seems better than
adding additional override arguments to all of my service methods!

-dan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Invoking java classes with a Perl client

2006-10-24 Thread D . Kreft


On 10/24/06, Anne Thomas Manes <[EMAIL PROTECTED]> wrote:


We need the WSDL to help you.


Thanks, Anne. Please find he WSDL attached.

-dan

http://pkgbuild.company.com/PBQS"; xmlns="http://schemas.xmlsoap.org/wsdl/"; xmlns:apachesoap="http://xml.apache.org/xml-soap"; xmlns:impl="http://pkgbuild.company.com/PBQS"; xmlns:intf="http://pkgbuild.company.com/PBQS"; xmlns:tns2="http://request.packagebuilder.company.com"; xmlns:tns3="http://event.packagebuilder.company.com"; xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema";>


http://pkgbuild.company.com/PBQS"; xmlns="http://www.w3.org/2001/XMLSchema";>
http://event.packagebuilder.company.com"/>
http://request.packagebuilder.company.com"/>
http://xml.apache.org/xml-soap"/>



























































































































































































http://xml.apache.org/xml-soap"; xmlns="http://www.w3.org/2001/XMLSchema";>
http://event.packagebuilder.company.com"/>
http://request.packagebuilder.company.com"/>
http://pkgbuild.company.com/PBQS"/>












http://event.packagebuilder.company.com"; xmlns="http://www.w3.org/2001/XMLSchema";>
http://request.packagebuilder.company.com"/>
http://xml.apache.org/xml-soap"/>
http://pkgbuild.company.com/PBQS"/>

Invoking java classes with a Perl client

2006-10-23 Thread D . Kreft


I'm stuck and endless googling is leading me to no success.

I'm trying to use Perl's SOAP::Lite to talk to an Axis web service.
I've got a new method that I want to add to my service implementation
that accepts an object as its sole argument, and what I need to do is
instantiate that object on the client, but I can't figure out how to
make it all happen.

Here's the relevant service method:

   public void testTakeRequest(Request request) {
   System.out.println("Request: " + request);
   }

And the snippet from the deploy.wsdd:

   

Here's the entirety of the Perl client:

   use strict;
   use warnings;

   use Data::Dumper qw(Dumper);

   use SOAP::Lite (dispatch_from => 'Request',
   uri   => 'urn:Request',
   proxy => $ENV{'PBQS_PROXY_URL'},
   trace => 'debug');

   my $r = Request->new();

   $r->isApproved(1);

   print Dumper($r);

But the problem is that I'm getting "No such operation 'new'" errors.
I can't figure out if I've got problems
with my namespace or what.

Here's how my request gets serialized:

   Accept: text/xml
   Accept: multipart/*
   Accept: application/soap
   Content-Length: 436
   Content-Type: text/xml; charset=utf-8
   SOAPAction: "http://packagebuild.company.com/Request#new";

   http://www.w3.org/2001/XMLSchema-instance";
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";>http://packagebuild.company.com/Request"; xsi:nil="true"
/>

I'm not sure if including the full body of my Axis-generated WSDL is
going to help, so I'll refrain from
posting that here until/unless someone asks for it.

BTW, if you're wondering why I don't e-mail the SOAP::Lite developer's
list, it's because that list appears to be pretty
much dead for all intents and purposes, so I'm hoping that one of you
might have a clue what I'm doing wrong
(other than using Perl--can't do anything about that given the huge
mass of legacy code with which I'm trying
to integrate).

-dan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Documentation for Java2WSDLTask

2006-10-13 Thread D . Kreft


It's kinda hard to read--your Content-type header is coming across as
"text/plain" even though it's an .html document.

-dan

On 10/12/06, Thilina Gunarathne <[EMAIL PROTECTED]> wrote:

There is a ongoing doc effort for these things... Just see whether it
matches your expectations...  Feedback is welcome :)

http://svn.apache.org/repos/asf/webservices/axis2/branches/java/1_1/xdocs/1_1/reference.html

Thnaks,
~Thilina

On 10/13/06, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
> classpathURI - That's the one that needs fixin'. there's a pending
> patch as well that changes several of the options. So hang in there.
>
> -- dims
>
> On 10/12/06, D. Kreft <[EMAIL PROTECTED]> wrote:
> > On 10/12/06, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
> >
> > > Troublemakers! :) Started a JIRA bug. The options for the ant task is
> > > almost one to one with the command line.
> >
> > Ooookay...
> >
> > So, I tried using the Ant task based upon an example that someone had
> > pasted in response to a similar question to this list, but the part
> > that is baffling me is that it can't find my class (I know"Newbie
> > classpath issues! Throw him to the sharks!").
> >
> > Unfortunately, Java2WSDLTask does not support a nested 
> > element like many other Ant tasks seem to do (hint hint), instead
> > there seems to be this 'classpathURI' attribute. What is *that*? Is it
> > a classpath or a URI?
> >
> > -dan
> >
> > >
> > > http://issues.apache.org/jira/browse/AXIS2-1360
> > >
> > > -- dims
> > >
> > > On 10/12/06, D. Kreft <[EMAIL PROTECTED]> wrote:
> > > > I should clarify thisI'm trying to use the Ant task, not the 
command line.
> > > >
> > > > -dan
> > > >
> > > > On 10/12/06, D. Kreft <[EMAIL PROTECTED]> wrote:
> > > > > Is there any documentation yet on how to use Java2WSDLTask? There are
> > > > > a bunch of new attributes to this task that I'm not familiar with. The
> > > > > javadocs for the class of the same name are, of course, no help--they
> > > > > assume I know what I'm doing. :-)
> > > > >
> > > > > -dan
> > > > >
> > > >
> > > > -
> > > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > For additional commands, e-mail: [EMAIL PROTECTED]
> > > >
> > > >
> > >
> > >
> > > --
> > > Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)
> > >
> > > -
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> >
>
>
> --
> Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
http://webservices.apache.org/~thilina/
http://thilinag.blogspot.com/



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Documentation for Java2WSDLTask

2006-10-12 Thread D . Kreft

On 10/12/06, Davanum Srinivas <[EMAIL PROTECTED]> wrote:

Troublemakers! :) Started a JIRA bug. The options for the ant task is
almost one to one with the command line.

Ooookay...

So, I tried using the Ant task based upon an example that someone had
pasted in response to a similar question to this list, but the part
that is baffling me is that it can't find my class (I know"Newbie
classpath issues! Throw him to the sharks!").

Unfortunately, Java2WSDLTask does not support a nested 
element like many other Ant tasks seem to do (hint hint), instead
there seems to be this 'classpathURI' attribute. What is *that*? Is it
a classpath or a URI?

-dan

http://issues.apache.org/jira/browse/AXIS2-1360

-- dims

On 10/12/06, D. Kreft <[EMAIL PROTECTED]> wrote:
> I should clarify thisI'm trying to use the Ant task, not the command line.
>
> -dan
>
> On 10/12/06, D. Kreft <[EMAIL PROTECTED]> wrote:
> > Is there any documentation yet on how to use Java2WSDLTask? There are
> > a bunch of new attributes to this task that I'm not familiar with. The
> > javadocs for the class of the same name are, of course, no help--they
> > assume I know what I'm doing. :-)
> >
> > -dan
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Documentation for Java2WSDLTask

2006-10-12 Thread D . Kreft


I should clarify thisI'm trying to use the Ant task, not the command line.

-dan

On 10/12/06, D. Kreft <[EMAIL PROTECTED]> wrote:

Is there any documentation yet on how to use Java2WSDLTask? There are
a bunch of new attributes to this task that I'm not familiar with. The
javadocs for the class of the same name are, of course, no help--they
assume I know what I'm doing. :-)

-dan



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Documentation for Java2WSDLTask

2006-10-12 Thread D . Kreft


Is there any documentation yet on how to use Java2WSDLTask? There are
a bunch of new attributes to this task that I'm not familiar with. The
javadocs for the class of the same name are, of course, no help--they
assume I know what I'm doing. :-)

-dan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Support for polymorphism in a service

2006-10-11 Thread D . Kreft


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


No, that's WSDL 2.0, where it is replaced by "Interface"...

www.w3.org/2002/ws/desc/wsdl20-primer


Sorry, yes...that's what Sanjiva was talking about. :-)

I'm hoping that a O(1) question will save me an O(n) scouring of that
document...does WSDL 2.0 support operator overloading?

-dan





-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of D.Kreft
Sent: Wednesday, October 11, 2006 1:40 PM
To: axis-user@ws.apache.org; [EMAIL PROTECTED]
Subject: Re: Support for polymorphism in a service

But wasn't the notion of portType supposed to be nixed in WSDL 1.1?

-dan

On 10/11/06, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
> Please see:
>
http://www.ws-i.org/Profiles/BasicProfile-1.1-2004-08-24.html#Distinctive_Ope
rations
>
> thanks,
> -- dims
>
> On 10/11/06, D. Kreft <[EMAIL PROTECTED]> wrote:
> > I'm writing a service that I'm trying to integrate into a legacy
> > system bit by bit. In the old system, a "request ID" is a String of
> > the format "rqMMDDHHMMSSXXX", but in the new system, a request ID
> > is simply a row identifier (a Long).
> >
> > What I'd like to do is use the power of polymorphism to keep my
> > service API clean and sane:
> >
> > public Request getRequestByID(String legacyRequestID) {
> > // ...
> > }
> >
> > public Request getRequestByID(Long requestID) {
> > // ...
> > }
> >
> > But when I try this, java2wsdl (Axis1) pukes with the following fault:
> >
> > Attempted to write duplicate schema element :
> > {http://pkgbuild.amazon.com/PBQS}getRequestByID
> >
> > ...which makes me sad. :-(   <-- See?
> >
> > Is this a WSDL 1.0 restriction or a deficiency in java2wsdl? Will such
> > use of polymorphism be possible under Axis2?
> >
> > -dan
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> --
> Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Support for polymorphism in a service

2006-10-11 Thread D . Kreft


But wasn't the notion of portType supposed to be nixed in WSDL 1.1?

-dan

On 10/11/06, Davanum Srinivas <[EMAIL PROTECTED]> wrote:

Please see:
http://www.ws-i.org/Profiles/BasicProfile-1.1-2004-08-24.html#Distinctive_Operations

thanks,
-- dims

On 10/11/06, D. Kreft <[EMAIL PROTECTED]> wrote:
> I'm writing a service that I'm trying to integrate into a legacy
> system bit by bit. In the old system, a "request ID" is a String of
> the format "rqMMDDHHMMSSXXX", but in the new system, a request ID
> is simply a row identifier (a Long).
>
> What I'd like to do is use the power of polymorphism to keep my
> service API clean and sane:
>
> public Request getRequestByID(String legacyRequestID) {
> // ...
> }
>
> public Request getRequestByID(Long requestID) {
> // ...
> }
>
> But when I try this, java2wsdl (Axis1) pukes with the following fault:
>
> Attempted to write duplicate schema element :
> {http://pkgbuild.amazon.com/PBQS}getRequestByID
>
> ...which makes me sad. :-(   <-- See?
>
> Is this a WSDL 1.0 restriction or a deficiency in java2wsdl? Will such
> use of polymorphism be possible under Axis2?
>
> -dan
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Support for polymorphism in a service

2006-10-11 Thread D . Kreft


I'm writing a service that I'm trying to integrate into a legacy
system bit by bit. In the old system, a "request ID" is a String of
the format "rqMMDDHHMMSSXXX", but in the new system, a request ID
is simply a row identifier (a Long).

What I'd like to do is use the power of polymorphism to keep my
service API clean and sane:

   public Request getRequestByID(String legacyRequestID) {
   // ...
   }

   public Request getRequestByID(Long requestID) {
   // ...
   }

But when I try this, java2wsdl (Axis1) pukes with the following fault:

   Attempted to write duplicate schema element :
{http://pkgbuild.amazon.com/PBQS}getRequestByID

...which makes me sad. :-(   <-- See?

Is this a WSDL 1.0 restriction or a deficiency in java2wsdl? Will such
use of polymorphism be possible under Axis2?

-dan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Axis2: simple service fails to work


On 9/25/06, Davanum Srinivas <[EMAIL PROTECTED]> wrote:

FWIW, your test case works fine with latest nightly when accessing via

http://localhost:7070/axis2/rest/test/getInt

and using "/services" should give you a warning to enable REST.

http://localhost:7070/axis2/services/test/getInt


What I would really like to understand is, what is so out of the
ordinary about my test case that it would have been missed during the
course of unit/functional tests? I can see if I were trying to do
something really complicated, but this is about as simple as it gets,
no? Such oversights in a major release make me a bit nervous, if you
know what I mean.

-dan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Axis2: simple service fails to work


On 9/25/06, Spies, Brennan <[EMAIL PROTECTED]> wrote:


What Dims and Robert forgot to mention is that Axis 2.0 is really a major
rewrite of the SOAP stack (hence the split of URLs, one for Axis 1 and one
for Axis 2). So the same growing pains apply here as with any new project.
Not that I don't feel your pain--I have been there many times before, trust
me--but I can also remember a time when free software was not in such
abundance. Given the excellent price of the software, it may be worthwhile to
stick it out with the nightlies until version 1.1 is released (which I
believe is at the end of this month, more or less).


The benefits you mention are not lost on me--the price is definitely
right when taken at its face. However, the poor messaging regarding
the stability/completeness of Axis2 1.0 has resulted in a net *loss*
for my employer as I went down a week-long rabbit trail. I can handle
incomplete/instable software--when I'm warned ahead of time that is
what I'm using.

-dan





-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of D.Kreft
Sent: Monday, September 25, 2006 1:37 PM
To: axis-user@ws.apache.org; [EMAIL PROTECTED]
Subject: Re: Axis2: simple service fails to work

On 9/25/06, Davanum Srinivas <[EMAIL PROTECTED]> wrote:

> JIRA Please. Can i assume you are trying the nightly?

No, I'm not using the nightly. I'm using the last "good" release--1.0
because I'm trying to develop a *production* application for my
employer, and the thought of having core business functionality
running on a nightly release of third-party software quite frankly is
not a sane development practice--there is too much money on the line
here.

I think at this point, I'm going to have to complete give up on using Axis2.

I and another developer I work with have had a number of difficulties
with Axis 1.4, none of which I'll bother to go into here, but suffice
to say that when we saw that Axis2 had finally reached version 1.0
("out of Beta" we thought), we were optimistic that the revised Axis
would obviate the need for some of the hacks we have in place to
overcome some of Axis's quirks. So I got my manager's blessing to see
what it takes to take the humble beginnings of my new service (already
mostly functional in Axis 1.4) and make it work in Axis2. I was hoping
it'd be a fairly straightforward deal, but after working on it for
five solid days, I have nothing more to show for my hard work than a
handful e-mails to this list, three subsequent requests for me to file
JIRAs, and a crippled service.

Did I misinterpret the major-number version bump? Is Axis2 really not
out of Beta yet? Because if it *is* supposed to be out of Beta at this
stage, then I cannot help but be profoundly disappointedthe
documentation is very sparse, often times irrelevant, sometimes
contradictory, counter-intuitive, and not terribly clear when it can
be found (I actually found more information in artciles *about* Axis2
than I did from the actual Axis2 website).  If it's still
considered "Beta" then that needs to be *clearly* and prominently
documented on the Axis2 website.

But documentation woes aside, what really disappoints me is that it
doesn't look as if anyone tested the seemingly simple case where the
developer writes a service implementation class, let Axis2 divine its
own WSDL from it, and have at least one of the methods return a simple
object. Axis2 seems to have no problems returning simple data types
(ints, Strings, primitive arrays of strings, etc.), but as soon as an
object is returned, all Hades breaks loose. And now, writing a
brain-dead simple service fails and I have to file a bug report for
that!

So now I've lost a full week of productivity (and a few handfuls of
hair)...all because I naively thought that version 1.0 meant "Okay,
we're ready for the real world."  It obviously isn't, and I can't help
but think that someone got a little trigger-happy in promoting Axis2
to version 1.0. In my humble estimation, it could have used a bit more
time "baking" in Beta (i.e. with a 0.x version number). If I had any
idea that Axis was still so raw, I wouldn't have wasted a 40-hour work
week on trying to get it to work...or the couple of hours I've spent
this morning trying to come up with a "simple" example of Axis2 puking
when an object is returned from a service method.

I don't doubt that the Axis2 developers are working very hard to get
all these issues resolved, but for goodness sake...you can't release a
product as version 1.0--which implies a non-Beta, stable release--when
the new product lacks much of the basic functionality that people are
going to need and that they are used to having provided for them by
the previous release (Axis 1.x).

-dan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsub

Re: Axis2: simple service fails to work


On 9/25/06, Davanum Srinivas <[EMAIL PROTECTED]> wrote:


JIRA Please. Can i assume you are trying the nightly?


No, I'm not using the nightly. I'm using the last "good" release--1.0
because I'm trying to develop a *production* application for my
employer, and the thought of having core business functionality
running on a nightly release of third-party software quite frankly is
not a sane development practice--there is too much money on the line
here.

I think at this point, I'm going to have to complete give up on using Axis2.

I and another developer I work with have had a number of difficulties
with Axis 1.4, none of which I'll bother to go into here, but suffice
to say that when we saw that Axis2 had finally reached version 1.0
("out of Beta" we thought), we were optimistic that the revised Axis
would obviate the need for some of the hacks we have in place to
overcome some of Axis's quirks. So I got my manager's blessing to see
what it takes to take the humble beginnings of my new service (already
mostly functional in Axis 1.4) and make it work in Axis2. I was hoping
it'd be a fairly straightforward deal, but after working on it for
five solid days, I have nothing more to show for my hard work than a
handful e-mails to this list, three subsequent requests for me to file
JIRAs, and a crippled service.

Did I misinterpret the major-number version bump? Is Axis2 really not
out of Beta yet? Because if it *is* supposed to be out of Beta at this
stage, then I cannot help but be profoundly disappointedthe
documentation is very sparse, often times irrelevant, sometimes
contradictory, counter-intuitive, and not terribly clear when it can
be found (I actually found more information in artciles *about* Axis2
than I did from the actual Axis2 website).  If it's still
considered "Beta" then that needs to be *clearly* and prominently
documented on the Axis2 website.

But documentation woes aside, what really disappoints me is that it
doesn't look as if anyone tested the seemingly simple case where the
developer writes a service implementation class, let Axis2 divine its
own WSDL from it, and have at least one of the methods return a simple
object. Axis2 seems to have no problems returning simple data types
(ints, Strings, primitive arrays of strings, etc.), but as soon as an
object is returned, all Hades breaks loose. And now, writing a
brain-dead simple service fails and I have to file a bug report for
that!

So now I've lost a full week of productivity (and a few handfuls of
hair)...all because I naively thought that version 1.0 meant "Okay,
we're ready for the real world."  It obviously isn't, and I can't help
but think that someone got a little trigger-happy in promoting Axis2
to version 1.0. In my humble estimation, it could have used a bit more
time "baking" in Beta (i.e. with a 0.x version number). If I had any
idea that Axis was still so raw, I wouldn't have wasted a 40-hour work
week on trying to get it to work...or the couple of hours I've spent
this morning trying to come up with a "simple" example of Axis2 puking
when an object is returned from a service method.

I don't doubt that the Axis2 developers are working very hard to get
all these issues resolved, but for goodness sake...you can't release a
product as version 1.0--which implies a non-Beta, stable release--when
the new product lacks much of the basic functionality that people are
going to need and that they are used to having provided for them by
the previous release (Axis 1.x).

-dan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Axis2: simple service fails to work


I changed the package to 'test', and still I get no respect.

-dan

On 9/25/06, Bhatra, Junaid <[EMAIL PROTECTED]> wrote:

It looks like your TestService class is in the default package. Try
putting it in some package and see what happens? Don't forget to change
the "ServiceClass" parameter to reflect the package name as well.

- Junaid

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of D.Kreft
Sent: Monday, September 25, 2006 2:18 PM
To: Axis Users
Subject: Axis2: simple service fails to work

I'm trying to whip-up a bare-bones service that will demonstrate
Axis2's inability to cope with complex data types returned by service
methods using RPCMessageReceiver and now I can't even get *that* to
work (what a way to start off the week). Here's the service
implementation:

public class TestService {
public String[] getArrayOfStrings() {
return new String[] {"Hello", "World"};
}

public int getInt() {
return 1;
}

public Object getObject() {
return new Object();
}

public String getString() {
return "Hello World";
}
}

And here's the services.xml:





TestService



















And the listing of my .aar file:

% jar -tf test.aar
META-INF/
META-INF/MANIFEST.MF
META-INF/services.xml
src/
src/TestService.java
TestService.class

I started Tomcat (and thus Axis2) from scratch, with only the default
'version' service and then used the web admin CGI to upload the
service. Immediately, I saw the following in the catalina.out:

- Error in schema generating null
java.lang.NullPointerException
at
org.apache.ws.java2wsdl.Java2WSDLUtils.namespaceFromClassName(Java2WSDLU
tils.java:51)
at
org.apache.ws.java2wsdl.Java2WSDLUtils.schemaNamespaceFromClassName(Java
2WSDLUtils.java:77)
at
org.apache.ws.java2wsdl.SchemaGenerator.(SchemaGenerator.java:77)
at
org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:209)
at
org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilde
r.java:149)
at
org.apache.axis2.deployment.repository.util.ArchiveReader.buildServiceGr
oup(ArchiveReader.java:76)
at
org.apache.axis2.deployment.repository.util.ArchiveReader.processService
Group(ArchiveReader.java:118)
at
org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.j
ava:620)
at
org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList
.java:195)
at
org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener
.java:207)
at
org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryL
istener.java:155)
at
org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryL
istener.java:199)
at
org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepositary(Sche
dulerTask.java:61)
at
org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.ja
va:68)
at
org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask.run(S
cheduler.java:76)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)

But yet Axis2 is still able to generate a WSDL (which I won't bother to
paste).

Calling http://localhost:7070/axis2/services/test/getInt results in a
"resource not found" error, with no accompanying stack trace or error
messaging in my catalina.out.

When I try to call getInt() (or any other method, for that matter) via
a Perl SOAP client, I get the exception pasted below. Can anyone see
what it is that I'm doing wrong?

-dan

org.apache.axis2.AxisFault: null; nested exception is:
java.lang.NullPointerException
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:318)
at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RP
CMessageReceiver.java:136)
at
org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(Abst
ractInOutSyncMessageReceiver.java:37)
at
org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:454)
at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostReques
t(HTTPTransportUtils.java:284)
at
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:136)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
tionFilterChain.java:252)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
erChain.java:173)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv
e.java:213)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv
e.java:178)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.

Re: Axis2: simple service fails to work


On 9/25/06, robert lazarski <[EMAIL PROTECTED]> wrote:


What does  http://localhost:7070/axis2/ show ?


The standard Axis2 Welcome page. Did you mean what does
/axis2/services/listServices show? I've pasted the contents of that
page below.

Interesting thing to note...the url is busted when I click on the name
of the service. Instead of "/axis2/services/?wsdl", the
links point to "/axis2/null/?wsdl"this happens for
all services listed.

-dan

 BEGIN /axis2/services/listServices OUTPUT 

Available services
test
Service EPR : http://dkreft-2.desktop.company.com:7070/axis2/null/test
Service REST epr : http://dkreft-2.desktop.company.com:7070/axis2/rest/test
Service Description : test
Service Status : Active
Available operations

   * getObject
   * getString
   * getArrayOfStrings
   * getInt

version
Service EPR : http://dkreft-2.desktop.company.com:7070/axis2/null/version
Service REST epr : http://dkreft-2.desktop.company.com:7070/axis2/rest/version
Service Description : This service is to get the running Axis version
Service Status : Active
Available operations

   * getVersion

 END /axis2/services/listServices OUTPUT 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Axis2: simple service fails to work


I'm trying to whip-up a bare-bones service that will demonstrate
Axis2's inability to cope with complex data types returned by service
methods using RPCMessageReceiver and now I can't even get *that* to
work (what a way to start off the week). Here's the service
implementation:

public class TestService {
   public String[] getArrayOfStrings() {
   return new String[] {"Hello", "World"};
   }

   public int getInt() {
   return 1;
   }

   public Object getObject() {
   return new Object();
   }

   public String getString() {
   return "Hello World";
   }
}

And here's the services.xml:




   
   TestService
   

   
   
   

   
   
   

   
   
   

   
   
   


And the listing of my .aar file:

% jar -tf test.aar
META-INF/
META-INF/MANIFEST.MF
META-INF/services.xml
src/
src/TestService.java
TestService.class

I started Tomcat (and thus Axis2) from scratch, with only the default
'version' service and then used the web admin CGI to upload the
service. Immediately, I saw the following in the catalina.out:

- Error in schema generating null
java.lang.NullPointerException
   at 
org.apache.ws.java2wsdl.Java2WSDLUtils.namespaceFromClassName(Java2WSDLUtils.java:51)
   at 
org.apache.ws.java2wsdl.Java2WSDLUtils.schemaNamespaceFromClassName(Java2WSDLUtils.java:77)
   at 
org.apache.ws.java2wsdl.SchemaGenerator.(SchemaGenerator.java:77)
   at org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:209)
   at 
org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:149)
   at 
org.apache.axis2.deployment.repository.util.ArchiveReader.buildServiceGroup(ArchiveReader.java:76)
   at 
org.apache.axis2.deployment.repository.util.ArchiveReader.processServiceGroup(ArchiveReader.java:118)
   at 
org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:620)
   at 
org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:195)
   at 
org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:207)
   at 
org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:155)
   at 
org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:199)
   at 
org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepositary(SchedulerTask.java:61)
   at 
org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.java:68)
   at 
org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask.run(Scheduler.java:76)
   at java.util.TimerThread.mainLoop(Timer.java:512)
   at java.util.TimerThread.run(Timer.java:462)

But yet Axis2 is still able to generate a WSDL (which I won't bother to paste).

Calling http://localhost:7070/axis2/services/test/getInt results in a
"resource not found" error, with no accompanying stack trace or error
messaging in my catalina.out.

When I try to call getInt() (or any other method, for that matter) via
a Perl SOAP client, I get the exception pasted below. Can anyone see
what it is that I'm doing wrong?

-dan

org.apache.axis2.AxisFault: null; nested exception is:
   java.lang.NullPointerException
   at org.apache.axis2.AxisFault.makeFault(AxisFault.java:318)
   at 
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:136)
   at 
org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:37)
   at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:454)
   at 
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:284)
   at 
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:136)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
   at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
   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.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
   at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
   at 
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:526)
   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:856)
   at 
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744)
   at 
org.apache.tomca

Re: AxisFault: Reader cannot be null


Additional info...

This only happens when calling methods that return complex data types
(objects, arrays of objects). It works fine if the return type is
something simple (integer, primitive array of strings):

% ./scripts/service  --method ping
Consulting Axis (1.x) Service...
$VAR1 = '1';

% ./scripts/service  --method ping --axis2
Consulting Axis2 Service...
$VAR1 = '1';

% ./scripts/service  --method arrayPing
Consulting Axis (1.x) Service...
$VAR1 = 'Hello';
$VAR2 = 'World';

% ./scripts/service  --method arrayPing --axis2
Consulting Axis2 Service...
$VAR1 = 'Hello';
$VAR2 = 'World';

I'm getting the feeling I'm missing just some tiny bit of metadata foo...

-dan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

AxisFault: Reader cannot be null


I've Googled for this fault meessage as well as searched the
axis-user@ mailing list and couldn't find anything helpful.

I've got a test script that I wrote that can call methods on both my
Axis and Axis2 services (on the same host, FWIW). The Axis 1.x calls
always return results, but the Axis2 call barfs on me with the
exception cited at the bottom of this e-mail. Anyone have any ideas
what's going on here?

Here's the output from Axis 1.4:

$ ./scripts/service  --method getRequestByID --id=2
Consulting Axis (1.x) Service...
$VAR1 = bless( {
'versionSetName' => 'PBTest/test-1',
'priority' => '2',
'isScrubbed' => 0,
'isApproved' => 1,
'addedOn' => '2006-09-05T22:50:05.000Z',
'timeConflict' => undef,
'isOptimized' => 0,
'createdBy' => 'dkreft',
'requestEvents' => {
   'requestEvents' => bless( {

'requestEventID' => '1',

'addedOn' => '2006-09-22T21:57:12.000Z',

'username' => 'dkreft',

'message' => 'foobar'
   }, 'RequestEvent' )
 },
'cleanupOnFailure' => 0,
'lastModified' => '2006-09-05T22:50:06.000Z',
'rebuildDependingTargets' => 0,
'rebuildVersionSet' => 0,
'requestID' => '2'
  }, 'Request' );

[I'm still trying to figure out why 'requestEvents' is coming out as
the wrong structure, but that's
a different issue.]

And here's what Axis2 does to me:

$ ./scripts/service  --axis2 --method getRequestByID --id=2
Consulting Axis2 Service...
Reader cannot be null
$VAR1 = {
 'Exception' => 'org.apache.axis2.AxisFault: Reader cannot be
null; nested exception is:
   java.lang.UnsupportedOperationException: Reader cannot be null
   at org.apache.axis2.AxisFault.makeFault(AxisFault.java:318)
   at 
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:136)
   at 
org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:37)
   at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:454)
   at 
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:284)
   at 
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:136)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
   at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
   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.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
   at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
   at 
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:526)
   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:856)
   at 
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744)
   at 
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
   at 
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
   at 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
   at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.UnsupportedOperationException: Reader cannot be null
   at org.apache.axis2.util.StreamWrapper.(StreamWrapper.java:39)
   at 
org.apache.axis2.rpc.receivers.RPCUtil.processResponse(RPCUtil.java:66)
   at 
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:130)
   ... 21 more
'
   };

Here's the relevant entry from my services.xml:

   
   
   

Any help/clues would be sorely appreciated.

-dan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Axis2 creating empty wsdl:message element


Ne'er mind on this one. I believe this is a bug in the SOAP::Lite
module (document/literal support is experimental at this point)--I've
got a patch for that module that seems like it'll fix the problem.

-dan

On 9/22/06, D. Kreft <[EMAIL PROTECTED]> wrote:

I've got what looks like an aberration in my Axis2-generated WSDL
(from yesterday's nightly, though. I'm not exactly a WSDL guru or
anything, but the following line is causing my Perl client (a
hand-made SOAP::Lite client that works just peachy with the same
service running under Axis1.4) to barf:



   



Note how there's no  for getAllRequestsMessage, unlike a
similar method in the same document:










I'm guessing that it's empty because this method takes no arguments
(see method definition below), and this
*might* be a deficiency with SOAP::Lite, however, the method
(getAllRequests()) is "WSDLed" by Axis1.4 like so:










Here are the relevant lines from my services.xml:








And the method definitions in my service implementation class. This
same class is used by
both Axis and Axis2

@SuppressWarnings("unchecked")
public  Request[] getAllRequests()
throws Exception
{
List allRequests = (List)_requestMethods.getAllRequests();

Request[] array = new Request[allRequests.size()];
allRequests.toArray(array);

return array;
}

@SuppressWarnings("unchecked")
public  Request[] getRequestsByPriority(int priority)
throws Exception
{
List allRequests =
(List)_requestMethods.getRequestsByPriority(priority);

Request[] array = new Request[allRequests.size()];
allRequests.toArray(array);

return array;
}

If you'd like to see the entire wsdl, let me know and I'll send it as
an attachment--I'm not sure
how much info would be needed to debug this and I didn't want to
overwhelm with a bunch
of noise.

-dan



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Axis2 creating empty wsdl:message element