Custom Axis Handler

2006-12-05 Thread Hoying, Ken
I am attempting to create a custom client side handler in Axis 1.2.  The
handler is being called and seems to working properly.  However, I am
unable to pass any parameters to it.

 

I am attempting to pass a string to the handler as follows:

Stub._setProperty("MyName", "MyValue");

 

However, when I try to retrieve the value in the Handler, null is
returned:

String myName = getOption("MyName");

 

Am I doing this incorrectly?

 

Thank you,
Ken Hoying



 



**
This message, including any attachments, contains confidential information 
intended for a specific individual and purpose, and is protected by law.  If 
you are not the intended recipient, please contact sender immediately by reply 
e-mail and destroy all copies.  You are hereby notified that any disclosure, 
copying, or distribution of this message, or the taking of any action based on 
it, is strictly prohibited.
TIAA-CREF
**



Programatically Setting the handlers

2006-10-20 Thread Hoying, Ken








I need to be able to programmatically set a handler for an
axis Web Service client.  I have a client that must conditionally be able to
use WS4J to set the appropriate WS Security information.  I have seen an
example on how to use WS4J using the client deployment descriptor (http://ws.apache.org/wss4j/axis.html).
 I was wondering if anyone had an example on how to do this programmatically without
using the deployment descriptor? 

 

Thank you,
Ken Hoying



 





**
This message, including any attachments, contains confidential information intended for a specific individual and purpose, and is protected by law.  If you are not the intended recipient, please contact sender immediately by reply e-mail and destroy all copies.  You are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited.
TIAA-CREF
**






Where to find Schema

2006-10-16 Thread Hoying, Ken








I need the schema for the type apachesoap:Map.  Where can I find this?

 

Thank you,
Ken

 

 





**
This message, including any attachments, contains confidential information intended for a specific individual and purpose, and is protected by law.  If you are not the intended recipient, please contact sender immediately by reply e-mail and destroy all copies.  You are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited.
TIAA-CREF
**






RE: [Axis1.2] Issue with Custom Chain

2006-09-22 Thread Hoying, Ken








After further investigation, it appears
that I was incorrect and you cannot create and configure your own chain classes
in the server-config.wsdd.  For future reference this would seem like a
nice feature.

 

So my question now becomes, can someone
provide me with an example or a solution to being able to dynamically enable
handlers?  

 



Thank you,
Ken Hoying













From: Hoying, Ken 
Sent: Wednesday, September 20,
2006 2:03 PM
To: axis-user@ws.apache.org
Subject: [Axis1.2] Issue with
Custom Chain



 

I am trying to configure a custom chain in the
server-config.wsdd.  However, the chain and its handler does not appear to
be getting called.  I must not have something right but I am not sure
what.  I do not see any error messages in my logs either.

 

 


 


   


 


 

 


   


   
     


 
  

 

   


 
  

 
  

 


 

Thank you,
Ken Hoying

 



**
This message, including any attachments,
contains 'confidential' information intended for a specific individual and
purpose, and is protected by law. If you are not the intended recipient, please
contact sender immediately by reply e-mail and destroy all copies. You are
hereby notified that any disclosure, copying, or distribution of this message,
or the taking of any action based on it, is strictly prohibited.
TIAA-CREF
**








[Axis1.2] Issue with Custom Chain

2006-09-20 Thread Hoying, Ken








I am trying to configure a custom chain in the server-config.wsdd. 
However, the chain and its handler does not appear to be getting called.  I
must not have something right but I am not sure what.  I do not see any error
messages in my logs either.

 

  

  

    

  

 

  

    

          

    

 

    

    

    

  

 

Thank you,
Ken Hoying



 





**
This message, including any attachments, contains 'confidential' information intended for a specific individual and purpose, and is protected by law.  If you are not the intended recipient, please contact sender immediately by reply e-mail and destroy all copies.  You are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited.
TIAA-CREF
**






org.xml.sax.SAXException: SimpleDeserializer encountered a child element

2006-05-25 Thread Hoying, Ken








I am having some difficulty calling a .NET web service from
Axis 1.2.1 client.  I am getting the following error:

 

org.xml.sax.SAXException: SimpleDeserializer encountered a child element, which is NOT expected, in something it was trying to deserialize.    at org.apache.axis.encoding.ser.SimpleDeserializer.onStartChild(SimpleDeserializer.java:145)    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:345)    at org.apache.axis.message.RPCElement.getParams(RPCElement.java:384)    at org.tiaa.dsv.dao.WebServicesDao.formatResults(WebServicesDao.java:337)    at org.tiaa.dsv.dao.WebServicesDao.invokeWithSoapEnvelope(WebServicesDao.java:291)    at org.tiaa.dsv.dao.WebServicesDao.callWebService(WebServicesDao.java:208)    at org.tiaa.dsv.dao.WebServicesDao.retrieveData(WebServicesDao.java:75)    at org.tiaa.dsv.ejb.MessageBean.onMessage(MessageBean.java:242)    at weblogic.ejb20.internal.MDListener.execute(MDListener.java:382)    at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:316)    at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281)    at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596)    at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516)    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)

 

The WSDL for the web service is as follows:

 

                    s:sequence>    s:complexType>  s:element>            s:sequence>  s:complexType>              s:sequence>  s:complexType>              s:sequence>    s:complexType>  s:element>            s:sequence>  s:complexType>            s:complexType>    s:schema>  wsdl:types>        wsdl:message>        wsdl:message>              wsdl:operation>  wsdl:portType>                    wsdl:input>        wsdl:output>    wsdl:operation>  wsdl:binding>                  RE: Error Calling .NET service









Thank you, Anne!

 

That was my suspicion as well.  However, I
wanted to ensure that it was not a known or simple mistake on my side.   I have
already contacted the developer of the .NET web service and will see how he
responds. 

 



Thank you,
Ken Hoying









From: Anne Thomas
Manes [mailto:[EMAIL PROTECTED] 
Sent: Friday, April 07, 2006 2:37
PM
To: axis-user@ws.apache.org
Subject: Re: Error Calling .NET
service



 

It sounds as if your
service isn't configured properly. You might try asking your question on a .NET
discussion list.

Anne



On 4/7/06, Hoying,
Ken <[EMAIL PROTECTED]>
wrote:





I
am trying to call a .NET web service and am running into some issues.  I
am getting the following error:

 Server was unable to process request. ---&gt; Object reference not set to an instance of an object.

 

The
WSDL for the service is as follows:

 

 http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://www.relius.net/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" targetNamespace="http://www.relius.net/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">       "qualified" targetNamespace="http://www.relius.net/">         ="PlansToCheck" type="tns:ArrayOfPlanInfo" />  s:sequence>         >    "true" type="tns:PlanInfo" />    >            name="PlanId" type="s:string" />  <s:element minOccurs="1" maxOccurs="1" name="Year" type="s:int" />         >        maxOccurs="1" name="GetPlanCountsResult" type="tns:ArrayOfNotice" />            name="ArrayOfNotice">       ="Notice" nillable="true" type="tns:Notice" />          <s:attribute name="Type" type="s:string" />       >           name="parameters" element="tns:GetPlanCounts" />     > />          name="GetPlanCounts">  />  />         type="tns:CrefServicesSoap">    http://schemas.xmlsoap.org/soap/http" />    "GetPlanCounts">  http://www.relius.net/GetPlanCounts" style="document" />  <wsdl:input>        <wsdl:output>          wsdl:operation>      http://schemas.xmlsoap.org/soap/http" />      http://www.relius.net/GetPlanCounts" style="document" />  <wsdl:input>        <wsdl:output>          wsdl:operation>         ="CrefServicesSoap" binding="tns:CrefServicesSoap">  <soap:address location="http://chast1reliuswc1/RWCRelius5500/crefservices.asmx" />        http://chast1reliuswc1/RWCRelius5500/crefservices.asmx" />      > 

 

I
am sending the following request to the web service using the Axis client:

POST
/RWCRelius5500/crefservices.asmx?WSDL HTTP/1.0

Content-Type:
text/xml; charset=utf-8

Accept:
application/soap+xml, application/dime, multipart/related, text/*

User-Agent:
Axis/1.2.1

Host:
chast1reliuswc1:9001

Cache-Control:
no-cache

Pragma:
no-cache

SOAPAction:
"http://www.relius.net/GetPlanCounts
"

Content-Length:
679

http://www.w3.org/2003/05/soap-envelope" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance">

   


   
http://www.relius.net/">

   


   


   
Plan1

   
2006

   


   


   
Plan2

   
2005

   


   


   


   




 

 

I
am getting back the following response:

 

HTTP/1.1
500 Internal Server Error

Connection:
close

Date:
Fri, 07 Apr 2006 18:00:29 GMT

Server:
Microsoft-IIS/6.0

X-Powered-By:
ASP.NET

X-AspNet-Version:
2.0.50727

Cache-Control:
private

Content-Type:
application/soap+xml; charset=utf-8

Content-Length:
508

http://www.w3.org/2003/05/soap-envelope"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">soap:ReceiverServer was unable to process request. --->
Object reference not set to an instance of an
object.

 

Any
ideas?  Any help would be gratefully appreciated.

 

Thank you,
Ke

Error Calling .NET service









I am trying to call a .NET web service and am running into
some issues.  I am getting the following error:

 Server was unable to process request. ---> Object reference not set to an instance of an object.

 

The WSDL for the service is as follows:

 

                    s:sequence>    s:complexType>  s:element>            s:sequence>  s:complexType>              s:sequence>  s:complexType>              s:sequence>    s:complexType>  s:element>            s:sequence>  s:complexType>            s:complexType>    s:schema>  wsdl:types>        wsdl:message>        wsdl:message>              wsdl:operation>  wsdl:portType>                    wsdl:input>        wsdl:output>    wsdl:operation>  wsdl:binding>                    wsdl:input>        wsdl:output>    wsdl:operation>  wsdl:binding>            wsdl:port>          wsdl:port>  wsdl:service>wsdl:definitions>

 

I am sending the following request to the web service using
the Axis client:

POST /RWCRelius5500/crefservices.asmx?WSDL HTTP/1.0



Content-Type: text/xml; charset=utf-8

Accept: application/soap+xml, application/dime,
multipart/related, text/*

User-Agent: Axis/1.2.1

Host: chast1reliuswc1:9001

Cache-Control: no-cache

Pragma: no-cache

SOAPAction: "http://www.relius.net/GetPlanCounts"

Content-Length: 679





    

    

   


   


   
Plan1

   
2006

   


   


   
Plan2

   
2005

   


   


   


    



 

 

I am getting back the following response:

 

HTTP/1.1 500 Internal Server Error

Connection: close

Date: Fri, 07 Apr 2006 18:00:29 GMT

Server: Microsoft-IIS/6.0

X-Powered-By: ASP.NET

X-AspNet-Version: 2.0.50727

Cache-Control: private

Content-Type: application/soap+xml; charset=utf-8

Conte

RE: I give up

Not to be a conspiracy theorist, but I cannot help but wonder if the support 
level is not affected by Covalent now selling support for Axis and Covalent's 
close relationship with current and former Axis developers (some of whom work 
for Covalent).  Has commercialism made its way into the open source ranks?

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of
Paul Barry
Sent: Friday, October 28, 2005 12:55 PM
To: axis-user@ws.apache.org
Subject: Re: I give up


I will agree that on this mailing list, so far, the few questions that
I have asked have gone unresponded to (granted I just asked my last
question yesterday).  But in general, I have found open source support
to be superior to commerce support.  I haven't worked with Microsoft
specifically, but other support I get from commercial products is
usually an email address or phone number that goes to a general help
desk.  This people typically have less knowledge about the product
than I do.  They can't conceptualize the problem I am having and they
usually just run through a list of typical problems and solutions. 
Open source projects, when they have a good community surrounding
them, are just the opposite.  You are getting support directly from
the experts.  As long as you do your work to isolate the problem and
report the information about the problem, most of the time you will
get a solution to your problem.

So I guess my point is I can't really speak to this community yet,
because I haven't been participating in it yet for long enough, but
just because you have had a bad experience with this oepn source
project, don't say that commercial support is better than open source.
 If you want to attack the axis community specifically, fine, but
there are a lot of open source projects that have communities that
offer a lot of help.  You are making broad generalizations about M$
vs. open source based on your experience with one open source
community.

On 10/28/05, McPhail, Jeff <[EMAIL PROTECTED]> wrote:
> I must say that I'm also extremely disappointed with Axis and
> this usergroup. I didn't like the fact that you have to sign up to
> receive ALL emails in order to participate -- I've never seen this
> before. So because I was in a jam and needed and answer, I joined and
> asked my question. I posted the question 5 times in different forms over
> a 3 week period and didn't get one response -- nothing.
> So I then tried to unsubscribe and it didn't work. I followed
> the instructions in the auto-reply given for troubleshooting
> unsubscribes and that didn't work. So I emailed the administrator (his
> email was in the autoreply, but of course nowhere to be found on the
> axis site) and got a reply about 3 days later telling me that the reason
> that my unsubscribe didn't work was because my email address was not on
> the list. So I responded assuring him that I am still on the list and am
> getting hundreds of messages a week (to my work email mind you) and I
> added a copy of the email header of one of the list emails I received
> with my email return path etc. -- I got no response. Also since the
> sender in the list emails is not axis-user@ws.apache.org but instead the
> individual senders address, I can't even mark them as spam to filter
> them (not a very smart setup, not to mention the privacy issues). This
> is becoming a real nuisance and it appears that I have no recourse. I've
> tried emailing the general Apache help and got no response, and of
> course there is not a single phone number on the either the apache or
> axis web sites.
> This is bush league support. No wonder so many people prefer to
> use Microsoft products. Maybe not all of their solutions are optimal
> (although I'm not sure how true this is anymore) but everything is much
> easier to implement, and interconnect with different technologies under
> the Microsoft umbrella. And when you have a problem, the support sites
> available are much superior --  I've never posted an issue about a
> microsoft product where I didn't have it solved within a day or two. The
> open source concept is great when you're a student and can't afford to
> fork over a grand or two for software, but when you use it for business
> apps and factor in the time to implement and the extra tens of thousands
> of dollars in man hours per year to fix bugs, Microsoft is a much
> cheaper solution.
>
> I would be extremely grateful to anyone to can tell me how to get off of
> this list. Thank you.
>
> Cheers,
>
> Jeff.
>
> -Original Message-
> From: Paul Grillo [mailto:[EMAIL PROTECTED]
> Sent: Friday, October 28, 2005 10:15 AM
> To: axis-user@ws.apache.org
> Cc: axis-dev@ws.apache.org
> Subject: RE: I give up
>
> I would like to add that, to a large extent, I feel Kurt's pain.  We
> used Axis 1.2 to deploy a single SOAP service that was required of us by
> one of our major partners that dictated a .NET interface complete with
> SOAP element signat

Is this a bug??

I noticed that properties, such as PROP_DOTNET_SOAPENC_FIX, are retrieved from 
the service configuration as such from TypeMappingImpl:

private boolean isDotNetSoapEncFixNeeded() {
MessageContext msgContext = MessageContext.getCurrentContext();
if (msgContext != null) {
SOAPService service = msgContext.getService();
if (service != null) {
String dotNetSoapEncFix = (String) 
service.getOption(AxisEngine.PROP_DOTNET_SOAPENC_FIX);
if (dotNetSoapEncFix != null) {
return JavaUtils.isTrue(dotNetSoapEncFix);
}
}
}
return TypeMappingImpl.dotnet_soapenc_bugfix;
}

However, the property PROP_XML_REUSE_SAX_PARSERS does not appear to be 
retrieved in this manner in XMLUtils:

String value = 
AxisProperties.getProperty(AxisEngine.PROP_XML_REUSE_SAX_PARSERS,
"" + false);
if (value.equalsIgnoreCase("true") ||
value.equals("1") ||
value.equalsIgnoreCase("yes")) {
enableParserReuse = true;
} else {
enableParserReuse = false;
}

This seems confusing an inconsistent, at the very least.  It also makes it very 
challenging to determined where and how to set and manage these properties such 
as PROP_XML_REUSE_SAX_PARSERS.

Thanks,
Ken


-----Original Message-
From: Hoying, Ken 
Sent: Tuesday, October 18, 2005 2:37 PM
To: axis-user@ws.apache.org
Subject: RE: performance



Is there another way to set this property besides on the command line?  I tried 
to set the property using the server-config.wsdd with the globalConfiguration 
setting:



However, when this does not appear to be working.  I get:

AxisProperties.getProperty(AxisEngine.PROP_XML_REUSE_SAX_PARSERS) = null

I also get null for any of the other parameters that I am setting in this 
section.

Am I missing something?  How can I verify the setting is being used?

Thanks,
Ken

-Original Message-
From: Jyrki Saarinen [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 12, 2005 9:00 AM
To: axis-user@ws.apache.org
Subject: Re: performance


On Wednesday 12 October 2005 15:57, Jyrki Saarinen wrote:
> On Saturday 08 October 2005 01:19, Eric Johnson wrote:
> > In Axis 1.2.1, you probably want to set the system property
> > "-Daxis.xml.reuseParsers=true".  In Axis 1.3, I believe the code was
> > changed so this is the default.
>
> In case of someone else is interested on this, it isn't on as default:
>
> String value =
> AxisProperties.getProperty(AxisEngine.PROP_XML_REUSE_SAX_PARSERS,
> "" + true);
> if (value.equalsIgnoreCase("true") ||
> value.equals("1") ||
> value.equalsIgnoreCase("yes")) {
> enableParserReuse = true;
> } else {
> enableParserReuse = false;
> }
>
> Jyrki

Äh, sorry. Of course it is on if the property is not specified, in which case 
AxisProperties.getProperty() returns "true";

Jyrki


**
This message, including any attachments, contains confidential information 
intended for a specific individual and purpose, and is protected by law.  If 
you are not the intended recipient, please contact sender immediately by reply 
e-mail and destroy all copies.  You are hereby notified that any disclosure, 
copying, or distribution of this message, or the taking of any action based on 
it, is strictly prohibited.
TIAA-CREF
**



**
This message, including any attachments, contains confidential information 
intended for a specific individual and purpose, and is protected by law.  If 
you are not the intended recipient, please contact sender immediately by reply 
e-mail and destroy all copies.  You are hereby notified that any disclosure, 
copying, or distribution of this message, or the taking of any action based on 
it, is strictly prohibited.
TIAA-CREF
**



RE: performance


Is there another way to set this property besides on the command line?  I tried 
to set the property using the server-config.wsdd with the globalConfiguration 
setting:



However, when this does not appear to be working.  I get:

AxisProperties.getProperty(AxisEngine.PROP_XML_REUSE_SAX_PARSERS) = null

I also get null for any of the other parameters that I am setting in this 
section.

Am I missing something?  How can I verify the setting is being used?

Thanks,
Ken

-Original Message-
From: Jyrki Saarinen [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 12, 2005 9:00 AM
To: axis-user@ws.apache.org
Subject: Re: performance


On Wednesday 12 October 2005 15:57, Jyrki Saarinen wrote:
> On Saturday 08 October 2005 01:19, Eric Johnson wrote:
> > In Axis 1.2.1, you probably want to set the system property
> > "-Daxis.xml.reuseParsers=true".  In Axis 1.3, I believe the code was
> > changed so this is the default.
>
> In case of someone else is interested on this, it isn't on as default:
>
> String value =
> AxisProperties.getProperty(AxisEngine.PROP_XML_REUSE_SAX_PARSERS,
> "" + true);
> if (value.equalsIgnoreCase("true") ||
> value.equals("1") ||
> value.equalsIgnoreCase("yes")) {
> enableParserReuse = true;
> } else {
> enableParserReuse = false;
> }
>
> Jyrki

Äh, sorry. Of course it is on if the property is not specified, in which case 
AxisProperties.getProperty() returns "true";

Jyrki


**
This message, including any attachments, contains confidential information 
intended for a specific individual and purpose, and is protected by law.  If 
you are not the intended recipient, please contact sender immediately by reply 
e-mail and destroy all copies.  You are hereby notified that any disclosure, 
copying, or distribution of this message, or the taking of any action based on 
it, is strictly prohibited.
TIAA-CREF
**



Axis 1.0 -> 1.2.1 Migration

Title: Axis 1.0 -> 1.2.1 Migration







I am attempting to migrate our application from Axis 1.0 to Axis 1.2.1.  One of the things that I have ran into is that the SOAPHeaderElement.getAttributes() method now returns a org.w3c.dom.NamedNodeMap instead of a org.xml.sax.Attributes.  I made the needed changes to our application and things work fine now when using an Axis 1.0 client to call the Axis 1.2.1 web service.

However, now when I call the Axis 1.2.1 web service with and Axis 1.2.1 client the application does not work.  The SOAPHeaderElement.getAttributes() returns a null.  Attributes are added using SOAPHeaderElement.addAttribute() method.  I suspect that this is no longer the proper way to add attributes to the header in Axis 1.2.1.  Can someone please advise on what is the proper method?

Thank you,

Ken Hoying




**
This message, including any attachments, contains confidential information intended for a specific individual and purpose, and is protected by law.  If you are not the intended recipient, please contact sender immediately by reply e-mail and destroy all copies.  You are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited.
TIAA-CREF
**




RE: Help! Migration from 1.0 to 1.2.1

Title: Help! Migration from 1.0 to 1.2.1



I was 
able to resolve my log4j configuration issue.  Now working on the 
underlying issue which appears to be a classpath problem.
 
Thanks,
Ken

  -Original Message-From: Hoying, Ken Sent: 
  Thursday, September 01, 2005 1:26 PMTo: Axis List 
  (E-mail)Subject: Help! Migration from 1.0 to 
  1.2.1
  I am having a devil of a time with migrating from 
  Axis 1.0 to 1.2.1. 
  I am getting a 
  java.lang.reflect.InvocationTargetException.  Something must also be   wrong with the log4j configuration because I get no stack trace or info at 
  all.  This is making it impossible for me to find the problem.
  Any help would be greatly appreciated!! 
  Thank you, Ken 
  Hoying **This 
  message, including any attachments, contains confidential information intended 
  for a specific individual and purpose, and is protected by law. If you are not 
  the intended recipient, please contact sender immediately by reply e-mail and 
  destroy all copies. You are hereby notified that any disclosure, copying, or 
  distribution of this message, or the taking of any action based on it, is   strictly 
  prohibited.TIAA-CREF**

**
This message, including any attachments, contains confidential information intended for a specific individual and purpose, and is protected by law.  If you are not the intended recipient, please contact sender immediately by reply e-mail and destroy all copies.  You are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited.
TIAA-CREF
**




Help! Migration from 1.0 to 1.2.1

Title: Help! Migration from 1.0 to 1.2.1







I am having a devil of a time with migrating from Axis 1.0 to 1.2.1.


I am getting a java.lang.reflect.InvocationTargetException.  Something must also be wrong with the log4j configuration because I get no stack trace or info at all.  This is making it impossible for me to find the problem.

Any help would be greatly appreciated!!


Thank you,

Ken Hoying




**
This message, including any attachments, contains confidential information intended for a specific individual and purpose, and is protected by law.  If you are not the intended recipient, please contact sender immediately by reply e-mail and destroy all copies.  You are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited.
TIAA-CREF
**




VerifyError???

anager.runAs(SecurityManager.java:118)
  at 
  weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3635)
  at 
  weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
  at 
  weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
  at 
  weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
  > 
  
    -Original Message-From: Hoying, Ken 
Sent: Tuesday, August 30, 2005 9:56 AMTo: Axis List 
(E-mail)Subject: Migration from Axis 1.0 to 
1.2.1
I am attempting to migrate my Axis 1.0 web 
service to Axis 1.2.1.  I am running into a bit of trouble 
though.  When calling the web service I get the following 
response:
HTTP/1.1 500 Internal Server Error Date: Tue, 30 
Aug 2005 13:51:53 GMT Server: WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 
2003 316284  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">soapenv:Server.generalExceptionjava.lang.NoSuchMethodError: 
org.apache.axis.message.MessageElement.getAttributes()Lorg/xml/sax/Attributes;; 
nested exception is: 
    java.lang.NoSuchMethodError: 
org.apache.axis.message.MessageElement.getAttributes()Lorg/xml/sax/Attributes;http://xml.apache.org/axis/">66200-HOYINGK
The web service is being called from a client 
that is still on Axis 1.0.  Must the client be upgraded to 1.2.1 as 
well?  Is there anyway to just upgrade the web service and not the clients?
Thank you, Ken 
Hoying **This 
message, including any attachments, contains confidential information intended for a specific individual and purpose, and is protected by law. If 
you are not the intended recipient, please contact sender immediately by 
reply e-mail and destroy all copies. You are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any 
action based on it, is strictly 
prohibited.TIAA-CREFThis 
  message, including any attachments, contains confidential information intended 
  for a specific individual and purpose, and is protected by law. If you are not 
  the intended recipient, please contact sender immediately by reply e-mail and 
  destroy all copies. You are hereby notified that any disclosure, copying, or 
  distribution of this message, or the taking of any action based on it, is   strictly 
  prohibited.TIAA-CREF**

**
This message, including any attachments, contains confidential information intended for a specific individual and purpose, and is protected by law.  If you are not the intended recipient, please contact sender immediately by reply e-mail and destroy all copies.  You are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited.
TIAA-CREF
**




RE: Migration from Axis 1.0 to 1.2.1

)
at 
weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at 
weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
> 

  -Original Message-From: Hoying, Ken Sent: 
  Tuesday, August 30, 2005 9:56 AMTo: Axis List 
  (E-mail)Subject: Migration from Axis 1.0 to 
  1.2.1
  I am attempting to migrate my Axis 1.0 web service 
  to Axis 1.2.1.  I am running into a bit of trouble though.  When 
  calling the web service I get the following response:
  HTTP/1.1 500 Internal Server Error Date: Tue, 30 
  Aug 2005 13:51:53 GMT Server: WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 
  2003 316284  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">soapenv:Server.generalExceptionjava.lang.NoSuchMethodError: 
  org.apache.axis.message.MessageElement.getAttributes()Lorg/xml/sax/Attributes;; 
  nested exception is: 
      java.lang.NoSuchMethodError: 
  org.apache.axis.message.MessageElement.getAttributes()Lorg/xml/sax/Attributes;http://xml.apache.org/axis/">66200-HOYINGK
  The web service is being called from a client that 
  is still on Axis 1.0.  Must the client be upgraded to 1.2.1 as 
  well?  Is there anyway to just upgrade the web service and not the   clients?
  Thank you, Ken 
  Hoying **This 
  message, including any attachments, contains confidential information intended 
  for a specific individual and purpose, and is protected by law. If you are not 
  the intended recipient, please contact sender immediately by reply e-mail and 
  destroy all copies. You are hereby notified that any disclosure, copying, or 
  distribution of this message, or the taking of any action based on it, is   strictly 
  prohibited.TIAA-CREF**

**
This message, including any attachments, contains confidential information intended for a specific individual and purpose, and is protected by law.  If you are not the intended recipient, please contact sender immediately by reply e-mail and destroy all copies.  You are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited.
TIAA-CREF
**




Migration from Axis 1.0 to 1.2.1

Title: Migration from Axis 1.0 to 1.2.1







I am attempting to migrate my Axis 1.0 web service to Axis 1.2.1.  I am running into a bit of trouble though.  When calling the web service I get the following response:

HTTP/1.1 500 Internal Server Error Date: Tue, 30 Aug 2005 13:51:53 GMT Server: WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284  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">soapenv:Server.generalExceptionjava.lang.NoSuchMethodError: org.apache.axis.message.MessageElement.getAttributes()Lorg/xml/sax/Attributes;; nested exception is: 

    java.lang.NoSuchMethodError: org.apache.axis.message.MessageElement.getAttributes()Lorg/xml/sax/Attributes;http://xml.apache.org/axis/">66200-HOYINGK

The web service is being called from a client that is still on Axis 1.0.  Must the client be upgraded to 1.2.1 as well?  Is there anyway to just upgrade the web service and not the clients?

Thank you,

Ken Hoying





**
This message, including any attachments, contains confidential information intended for a specific individual and purpose, and is protected by law.  If you are not the intended recipient, please contact sender immediately by reply e-mail and destroy all copies.  You are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited.
TIAA-CREF
**




RE: [Axis1] Axis Memory Leak

Name: org/apache/xerces/impl/Version.class
Comment: Xerces-J 2.6.2 
Implementation-Title: org.apache.xerces.impl.Version
Implementation-Version: 2.6.2
Implementation-Vendor: Apache Software Foundation
Implementation-URL: http://xml.apache.org/xerces2-j/

Name: org/xml/sax/
Comment: based on xml-commons external 1.2.01
Specification-Title: Simple API for XML
Specification-Vendor: David Megginson
Specification-Version: 2.0.1
Implementation-Title: org.xml.sax
Implementation-Version: 2.0.1
Implementation-Vendor: David Megginson
Implementation-URL: http://www.saxproject.org/

Name: org/w3c/dom/
Comment: based on xml-commons external 1.2.01
Specification-Title: Document Object Model, Level 2 Core
Specification-Vendor: World Wide Web Consortium
Specification-Version: 1.0
Implementation-Title: org.w3c.dom
Implementation-Version: 1.0
Implementation-Vendor: World Wide Web Consortium
Implementation-URL: http://www.w3c.org/DOM/

Name: javax/xml/parsers/
Comment: based on xml-commons external 1.2.01
Specification-Title: Java API for XML Processing
Specification-Version: 1.2
Specification-Vendor: Sun Microsystems Inc.
Implementation-Title: javax.xml.parsers
Implementation-Version: 1.2.01
Implementation-Vendor: Sun Microsystems Inc.
Implementation-URL: http://java.sun.com/xml/jaxp.html

Name: javax/xml/transform/
Comment: based on xml-commons external 1.2.01
Specification-Title: Java API for XML Processing
Specification-Version: 1.2
Specification-Vendor: Sun Microsystems Inc.
Implementation-Title: javax.xml.transform
Implementation-Version: 1.2.01
Implementation-Vendor: Sun Microsystems Inc.
Implementation-URL: http://java.sun.com/xml/jaxp.html

Name: org/apache/xerces/xni/
Comment: Xerces Native Interface
Specification-Title: Xerces Native Interface
Specification-Version: 1.1
Specification-Vendor: Apache Software Foundation
Implementation-Title: org.apache.xerces.xni
Implementation-Version: 1.1
Implementation-Vendor: Apache Software Foundation
Implementation-URL: http://xml.apache.org/xerces2-j/

Manifest-Version: 1.0
Created-By: 1.3.1 (IBM Corporation)
Main-Class: org.apache.xalan.xslt.Process
Class-Path: xercesImpl.jar xml-apis.jar

Name: org/apache/xalan
Comment: Main Xalan engine implementing TrAX/JAXP
Specification-Title: Java API for XML Processing
Specification-Vendor: Sun Microsystems Inc.
Specification-Version: 1.2
Implementation-Title: org.apache.xalan
Implementation-Version: 2.6.0
Implementation-Vendor: Apache Software Foundation
Implementation-URL: http://xml.apache.org/xalan-j/dist/

Name: org/apache/xpath
Comment: XPath engine
Implementation-Title: org.apache.xpath
Implementation-Version: 2.6.0
Implementation-Vendor: Apache Software Foundation
Implementation-URL: http://xml.apache.org/xalan-j/dist/

Name: org/apache/xml
Comment: DTM implementation and utilities
Implementation-Title: org.apache.xml
Implementation-Version: 2.6.0
Implementation-Vendor: Apache Software Foundation
Implementation-URL: http://xml.apache.org/xalan-j/dist/

Name: org/apache/xalan/xsltc
Comment: Main XSLTC engine implementing TrAX/JAXP
Specification-Title: Java API for XML Processing
Specification-Vendor: Sun Microsystems Inc.
Specification-Version: 1.2
Implementation-Title: org.apache.xalan.xsltc
Implementation-Version: 2.6.0
Implementation-Vendor: Apache Software Foundation
Implementation-URL: http://xml.apache.org/xalan-j/dist/

Name: runtime
Comment: Runtime component of JCup 
Specification-Title: Runtime component of JCup
Specification-Vendor: Princeton University 
Specification-Version: 0.10k 
Implementation-Title: runtime 
Implementation-Version: 2.6.0
Implementation-Vendor: Princeton University  
Implementation-URL: http://www.cs.princeton.edu/~appel/modern/java/CUP/ 

Name: org/apache/bcel
Comment: Byte Code Engineering Library 
Specification-Title: Byte Code Engineering Library 
Specification-Vendor: Markus Dahm 
Specification-Version: 5.0 rc1 
Implementation-Title: org.apache.bcel
Implementation-Version: 2.6.0
Implementation-Vendor: Apache Software Foundation
Implementation-URL: http://jakarta.apache.org/bcel

Name: org/apache/regexp
Comment: Java Regular Expression package 
Specification-Title: Java Regular Expression package 
Specification-Vendor: Apache Software Foundation 
Specification-Version: 1.2
Implementation-Title: org.apache.regexp
Implementation-Version: 2.6.0
Implementation-Vendor: Apache Software Foundation
Implementation-URL: http://jakarta.apache.org/regexp

-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Friday, August 26, 2005 9:35 AM
To: axis-user@ws.apache.org
Subject: Re: [Axis1] Axis Memory Leak


Which version of xerces are u using?

-- dims

On 8/26/05, Hoying, Ken <[EMAIL PROTECTED]> wrote:
> We are currently running out of memory in production after about three days. 
> However, this is not our only memory leak.  We are also working on revolving 
> a leak we seem to be having in XALAN with a transform.  The XALAN leak is 
> definitely the

RE: [Axis1] Axis Memory Leak

We are currently running out of memory in production after about three days. 
However, this is not our only memory leak.  We are also working on revolving a 
leak we seem to be having in XALAN with a transform.  The XALAN leak is 
definitely the larger of the two. Currently, we are avoiding the problem by 
restarting the server daily.  However, this is not an acceptable solution for 
the long term.

-Original Message-
From: Benjamin Marcel Flohr [mailto:[EMAIL PROTECTED]
Sent: Friday, August 26, 2005 9:22 AM
To: axis-user@ws.apache.org; [EMAIL PROTECTED]
Subject: AW: [Axis1] Axis Memory Leak


Hello,
what is the effect of this memory leak. We are using Axis 1.0 in production 
without having any problems.
Can you tell me more ?
thanx, benjamin

-Ursprüngliche Nachricht-
Von: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 26. August 2005 15:18
An: axis-user@ws.apache.org
Betreff: Re: [Axis1] Axis Memory Leak


Please switch to Axis 1.2.1. No you can't replace the jar. you need to
regen the server and client. "Axis 1.0 jar used on a client work with
the Axis 1.2.1 server" may work but it depends if there was a bug in
the exact scenario you are using.

-- dims

On 8/26/05, Hoying, Ken <[EMAIL PROTECTED]> wrote:
>  
>  
> 
> We are having issues with a slow memory leak that is resulting in
> OutOfMemory errors in our production environment after about 3 days time. > 
> We are currently using Axis 1.0.  After profiling the application with
> OptimizeIt, it appears that there is a memory leak that seems to be tied to
> the following: 
>  
> 
> org.apache.axis.Message.getSOAPEnvelope() 
> 
> Can anyone confirm that this was a known memory leak and it is have been
> fixed in a subsequent release of Axis? 
> 
> I am also curious to know what implications would arise from switching to
> Axis 1.2.1.  Can I just replace the jar or do I need to regen class and
> clients? Does the Axis 1.0 jar used on a client work with the Axis 1.2.1 on
> the server? 
> 
> Thank you, 
> Ken Hoying 
>  
> **
>  This message, including any attachments, contains confidential information
> intended for a specific individual and purpose, and is protected by law. If
> you are not the intended recipient, please contact sender immediately by
> reply e-mail and destroy all copies. You are hereby notified that any
> disclosure, copying, or distribution of this message, or the taking of any
> action based on it, is strictly prohibited.
>  TIAA-CREF
> **
>  


-- 
Davanum Srinivas : http://wso2.com/ - Oxygenating The Web Service Platform


**
This message, including any attachments, contains confidential information 
intended for a specific individual and purpose, and is protected by law.  If 
you are not the intended recipient, please contact sender immediately by reply 
e-mail and destroy all copies.  You are hereby notified that any disclosure, 
copying, or distribution of this message, or the taking of any action based on 
it, is strictly prohibited.
TIAA-CREF
**



RE: [Axis1] Axis Memory Leak

Regenerating the clients is going to be very difficult.  We have several spread 
throughout the organization and already in production. I am disappointed to 
hear that the client version is so tightly integrated to the server version.  
Seems like this sort of defeats the goals and benefits of a web service based 
SOA.

I will start taking a look at making the switch, but can someone confirm that 
there was such a bug or leak that was addresses in the 1.2.1 version.  I would 
hate to make this change, especially due to the potentially large impact to the 
organization, if it does not fix the problem.

Thanks,
Ken

-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Friday, August 26, 2005 9:18 AM
To: axis-user@ws.apache.org
Subject: Re: [Axis1] Axis Memory Leak


Please switch to Axis 1.2.1. No you can't replace the jar. you need to
regen the server and client. "Axis 1.0 jar used on a client work with
the Axis 1.2.1 server" may work but it depends if there was a bug in
the exact scenario you are using.

-- dims

On 8/26/05, Hoying, Ken <[EMAIL PROTECTED]> wrote:
>  
>  
> 
> We are having issues with a slow memory leak that is resulting in
> OutOfMemory errors in our production environment after about 3 days time. > 
> We are currently using Axis 1.0.  After profiling the application with
> OptimizeIt, it appears that there is a memory leak that seems to be tied to
> the following: 
>  
> 
> org.apache.axis.Message.getSOAPEnvelope() 
> 
> Can anyone confirm that this was a known memory leak and it is have been
> fixed in a subsequent release of Axis? 
> 
> I am also curious to know what implications would arise from switching to
> Axis 1.2.1.  Can I just replace the jar or do I need to regen class and
> clients? Does the Axis 1.0 jar used on a client work with the Axis 1.2.1 on
> the server? 
> 
> Thank you, 
> Ken Hoying 
>  
> **
>  This message, including any attachments, contains confidential information
> intended for a specific individual and purpose, and is protected by law. If
> you are not the intended recipient, please contact sender immediately by
> reply e-mail and destroy all copies. You are hereby notified that any
> disclosure, copying, or distribution of this message, or the taking of any
> action based on it, is strictly prohibited.
>  TIAA-CREF
> **
>  


-- 
Davanum Srinivas : http://wso2.com/ - Oxygenating The Web Service Platform


**
This message, including any attachments, contains confidential information 
intended for a specific individual and purpose, and is protected by law.  If 
you are not the intended recipient, please contact sender immediately by reply 
e-mail and destroy all copies.  You are hereby notified that any disclosure, 
copying, or distribution of this message, or the taking of any action based on 
it, is strictly prohibited.
TIAA-CREF
**



[Axis1] Axis Memory Leak

Title: [Axis1] Axis Memory Leak







We are having issues with a slow memory leak that is resulting in OutOfMemory errors in our production environment after about 3 days time.  We are currently using Axis 1.0.  After profiling the application with OptimizeIt, it appears that there is a memory leak that seems to be tied to the following:

org.apache.axis.Message.getSOAPEnvelope()


Can anyone confirm that this was a known memory leak and it is have been fixed in a subsequent release of Axis?


I am also curious to know what implications would arise from switching to Axis 1.2.1.  Can I just replace the jar or do I need to regen class and clients? Does the Axis 1.0 jar used on a client work with the Axis 1.2.1 on the server?

Thank you,

Ken Hoying




**
This message, including any attachments, contains confidential information intended for a specific individual and purpose, and is protected by law.  If you are not the intended recipient, please contact sender immediately by reply e-mail and destroy all copies.  You are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited.
TIAA-CREF
**




RE: .NET Client


Anne,

Once again thanks for the help.  You are busy on this board and I for one 
appreciate it!

I am not attempting to do the wrapped doc/literal.  However, I am running into 
more problems.  Must I generate the server side code or can I just use the same 
wrapper class and code that was generated for the client and include it in the 
class path and allow Axis to deploy itself from the server-config.wsdd that I 
created?  

I am trying to include the client code on the Axis server which contains the 
wrapper class (ArrayOfString) that I created. However, Axis seems unable to 
find this class no matter where I put it.  I have put it in my war file under 
WEB-INF\classes and in a jar under WEB-INF\lib.  I have also included it in my 
ear.  How is it possible that Axis is not finding this?  

Thanks,
Ken

-Original Message-
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 10, 2005 5:01 PM
To: axis-user@ws.apache.org
Subject: Re: .NET Client


Regen your service so that it uses "wrapped" doc/literal.

On 8/10/05, Hoying, Ken <[EMAIL PROTECTED]> wrote:
>  
>  
> 
> .NET Developers are reporting the following error when attempting to build a
> .NET client for our Axis service: 
>  
> 
> Custom tool error: Unable to import WebService/Schema. Unable to import
> binding 'DSVNETSoapBinding' from namespace
> 'http://66200-hoyingk.wins.tiaa-cref.org:7072/dsvaxis/services/DSVNET'.
> Unable to import operation 'getNetDocument'. Referenced type
> 'http://schemas.xmlsoap.org/soap/encoding/:Array' is only
> valid for encoded SOAP. 
> 
> I am not a .NET developer and do not even have the environment to work on
> this.  Any direction would be greatfully appreciated. 
> 
> Thank you, 
> Ken Hoying 
>  
>  
> **
>  This message, including any attachments, contains confidential information
> intended for a specific individual and purpose, and is protected by law. If
> you are not the intended recipient, please contact sender immediately by
> reply e-mail and destroy all copies. You are hereby notified that any
> disclosure, copying, or distribution of this message, or the taking of any
> action based on it, is strictly prohibited.
>  TIAA-CREF
> **
>


**
This message, including any attachments, contains confidential information 
intended for a specific individual and purpose, and is protected by law.  If 
you are not the intended recipient, please contact sender immediately by reply 
e-mail and destroy all copies.  You are hereby notified that any disclosure, 
copying, or distribution of this message, or the taking of any action based on 
it, is strictly prohibited.
TIAA-CREF
**



RE: Axis 1.0 Bug with Wrapped Documents??

Thank Anne,

Unfortunately, I am not at a point where I can switch out versions of Axis.  I 
do have a questions though.  When I get to that point, do I have to have all of 
my clients update their axis libraries or will they be backward compatible?

For now, I have been able to get around this bug by updating the WSDL to match 
the Return signature.

Thanks,
Ken

-Original Message-
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 10, 2005 5:14 PM
To: axis-user@ws.apache.org
Subject: Re: Axis 1.0 Bug with Wrapped Documents??


It's a bug in Axis 1.0. It always names the return value Return.
You should upgrade to Axis 1.2 if you want to use doc/literal.

Anne

On 8/9/05, Hoying, Ken <[EMAIL PROTECTED]> wrote:
>  
>  
> 
> I have created a wrapped document literal web service in Axis.  The service
> seems to make the call correctly from the client.  The server is invoked and
> does return data to the client (I know this from the TCPMonitor utility). > 
> However, the call is suppose to return a string but it always returns null. 
> 
> Here is the WSDL: 
> 
>  
> http://dsv.tiaacref.org";
> xmlns="http://schemas.xmlsoap.org/wsdl/";
> xmlns:apachesoap="http://xml.apache.org/xml-soap";
> xmlns:impl="http://dsv.tiaacref.org-impl";
> xmlns:intf="http://dsv.tiaacref.org";
> xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";
> xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
> xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";> 
> 
>  
> http://dsv.tiaacref.org";
> xmlns="http://www.w3.org/2001/XMLSchema";
> xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";> 
> 
>  namespace="http://schemas.xmlsoap.org/soap/encoding/"/> 
>  
>  
>  
>  type="xsd:string" /> 
>  type="intf:ArrayOfString" /> 
>  type="intf:ArrayOfString" /> 
>  
>  
>  
> 
>  
>  
>  
>  type="xsd:string" /> 
>  
>  
>  
> 
>  
>  
>  
>  ref="soapenc:arrayType" wsdl:arrayType="xsd:string[]" /> 
>  
>  
>  
>  
>  
> 
>  
> 
>  
> 
>  
>  element="intf:getNetDocumentResponse"/> 
>  
> 
>  
>  
>  name="getNetDocumentRequest"/> 
>  name="getNetDocumentResponse"/> 
>  
>  
> 
>  name="DSVNetWebServiceImplSoapBinding"
> type="intf:DSVNetWebService"> 
>  transport="http://schemas.xmlsoap.org/soap/http"/> 
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
> 
>  
>  binding="intf:DSVNetWebServiceImplSoapBinding"
> name="DSVNetWebServiceImpl"> 
>  location="http://10.17.9.67:8011/axis/DSVNetWebServiceImpl.jws"/>
>  
>  
> 
>  
> 
> The one thing that is noticed in the response message from the server is
> that it is not wrapped in an  tag which I had expected.  Shouldnt'
> it be?  Here is the response from the server: 
> 
> HTTP/1.1 200 OK Date: Tue, 09 Aug 2005 17:06:48 GMT Server: WebLogic Server
> 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284  Content-Type: text/xml;
> charset=utf-8 Connection: Close   
> 
>  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
> xml

.NET Client

Title: .NET Client







.NET Developers are reporting the following error when attempting to build a .NET client for our Axis service:


Custom tool error: Unable to import WebService/Schema. Unable to import binding 'DSVNETSoapBinding' from namespace 'http://66200-hoyingk.wins.tiaa-cref.org:7072/dsvaxis/services/DSVNET'. Unable to import operation 'getNetDocument'. Referenced type 'http://schemas.xmlsoap.org/soap/encoding/:Array' is only valid for encoded SOAP.

I am not a .NET developer and do not even have the environment to work on this.  Any direction would be greatfully appreciated.

Thank you,

Ken Hoying





**
This message, including any attachments, contains confidential information intended for a specific individual and purpose, and is protected by law.  If you are not the intended recipient, please contact sender immediately by reply e-mail and destroy all copies.  You are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited.
TIAA-CREF
**




RE: Axis 1.0 Bug with Wrapped Documents??

Title: Axis 1.0 Bug with Wrapped Documents??



I 
noticed that the getNetDocumentReturn in the response does 
not have a namespace listed.  Could that be the issue and if so any ideas 
why I am not seeing one?
 
 

  -Original Message-From: Hoying, Ken Sent: 
  Tuesday, August 09, 2005 1:18 PMTo: Axis List 
  (E-mail)Subject: Axis 1.0 Bug with Wrapped 
  Documents??
  I have created a wrapped document literal web 
  service in Axis.  The service seems to make the call correctly from the 
  client.  The server is invoked and does return data to the client (I know 
  this from the TCPMonitor utility).  However, the call is suppose to   return a string but it always returns null.
  Here is the WSDL: 
  xml version="1.0" 
  encoding="UTF-8"?> <wsdl:definitions targetNamespace="http://dsv.tiaacref.org" xmlns="http://schemas.xmlsoap.org/wsdl/" 
  xmlns:apachesoap="http://xml.apache.org/xml-soap" 
  xmlns:impl="http://dsv.tiaacref.org-impl" 
  xmlns:intf="http://dsv.tiaacref.org" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" 
  xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" 
  xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" 
  xmlns:xsd="http://www.w3.org/2001/XMLSchema">
      <wsdl:types>     
      <schema targetNamespace="http://dsv.tiaacref.org" xmlns="http://www.w3.org/2001/XMLSchema" 
  xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
      
      
      <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/> 
      
      
      <element name="getNetDocument"> 
      
      
      
      <complexType>     
      
      
      
      <sequence>     
      
      
      
      
      <element name="document" type="xsd:string" />     
      
      
      
      
      <element name="paramKeys" type="intf:ArrayOfString" />     
      
      
      
      
      <element name="paramVals" type="intf:ArrayOfString" />     
      
      
      
      sequence>     
      
      
      complexType>     
      
      element> 
      
      
      
      
      
      <element name="getNetDocumentResponse"> 
      
      
      
      <complexType>     
      
      
      
      <sequence>     
      
      
      
      
      <element name="xmlVal" type="xsd:string" />     
      
      
      
      sequence>     
      
      
      complexType>     
      
      element> 
  
      
      
      <complexType name="ArrayOfString"> 
      
      
      
      <complexContent>     
      
      
      
      <restriction base="soapenc:Array"> 
      
      
      
      
      
      <attribute ref="soapenc:arrayType" wsdl:arrayType="xsd:string[]" /> 
      
      
      
      
      restriction>     
      
      
      complexContent>     
      
      complexType>     
      schema> 
      wsdl:types> 
      <wsdl:message name="getNetDocumentRequest"> 
      
      <wsdl:part name="parameters" element="intf:getNetDocument"/>     wsdl:message> 
      <wsdl:message name="getNetDocumentResponse"> 
      
      <wsdl:part name="parameters" element="intf:getNetDocumentResponse"/> 
      wsdl:message> 
      <wsdl:portType name="DSVNetWebService"> 
      
      <wsdl:operation name="getNetDocument"> 
      
      
      <wsdl:input message="intf:getNetDocumentRequest" name="getNetDocumentRequest"/>     
      
      <wsdl:output message="intf:getNetDocumentResponse" name="getNetDocumentResponse"/>     
      wsdl:operation>     wsdl:portType> 
      <wsdl:binding name="DSVNetWebServiceImplSoapBinding" type="intf:DSVNetWebService">     
      <wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/> 
      
      <wsdl:operation name="getNetDocument"> 
      
      
      <wsdlsoap:operation soapAction=""/> 

Axis 1.0 Bug with Wrapped Documents??

Title: Axis 1.0 Bug with Wrapped Documents??







I have created a wrapped document literal web service in Axis.  The service seems to make the call correctly from the client.  The server is invoked and does return data to the client (I know this from the TCPMonitor utility).  However, the call is suppose to return a string but it always returns null.

Here is the WSDL:


xml version="1.0" encoding="UTF-8"?>



    

        

            

            

                

                    

                        

                        

                        

                    sequence>

                complexType>

            element>

            

            

                

                    

                        

                    sequence>

                complexType>

            element>


            

                

                    

                        

                    restriction>

                complexContent>

            complexType>

        schema>

    wsdl:types>


    

        

    wsdl:message>


    

        

    wsdl:message>


    

        

            

            

        wsdl:operation>

    wsdl:portType>


    

        

        

            

            

                

            wsdl:input>

            

                

            wsdl:output>

        wsdl:operation>

    wsdl:binding>


    

        

            

        wsdl:port>

    wsdl:service>


wsdl:definitions>


The one thing that is noticed in the response message from the server is that it is not wrapped in an  tag which I had expected.  Shouldnt' it be?  Here is the response from the server:

HTTP/1.1 200 OK Date: Tue, 09 Aug 2005 17:06:48 GMT Server: WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284  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://dsv.tiaacref.org">

   THE RESPONSE DATA

  

 




Is this a bug or have I missed something?


Thank you,

Ken Hoying



RE: WSDL Error

Yep! That was it.  Too many new technologies for me at one time :-)

Thank you!

-Original Message-
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 09, 2005 8:12 AM
To: axis-user@ws.apache.org
Subject: Re: WSDL Error


You have a namespace problem. You've defined your elements in the
apachesoap namespace (http://xml.apache.org/xml-soap), but you're
trying referencing them by the intf namespace
(http://dsv.tiaacref.org).

Anne

On 8/8/05, Hoying, Ken <[EMAIL PROTECTED]> wrote:
>  
> 
> I am getting the following error: 
> 
> [wsdl2java] WSDL2Java dsv.wsdl 
> [wsdl2java] Parsing XML file:  dsv.wsdl 
> [wsdl2java] Running Wsdl2javaAntTask with parameters: 
> [wsdl2java] verbose:true 
> [wsdl2java] server-side:false 
> [wsdl2java] skeletonDeploy:false 
> [wsdl2java] helperGen:false 
> [wsdl2java] factory:null 
> [wsdl2java] testCase:false 
> [wsdl2java] noImports:false 
> [wsdl2java]
> NStoPkg:{http://dsv.tiaacref.org=org.tiaa.j2eeinfra.dsvwrapper.wsdl}
> [wsdl2java]
> output:C:\Projects\DSVWrapper\implementation\temp\src 
> [wsdl2java] deployScope:session 
> [wsdl2java] URL:dsv.wsdl 
> [wsdl2java] all:false 
> [wsdl2java] typeMappingVersion:1.1 
> [wsdl2java] timeout:45000 
> [wsdl2java] failOnNetworkErrors:false 
> [wsdl2java] printStackTraceOnFailure:true 
> [wsdl2java] java.io.IOException: Element
> {http://dsv.tiaacref.org}getNetDocumentResponse is referenced but not
> defined. 
> [wsdl2java] at
> org.apache.axis.wsdl.symbolTable.SymbolTable.checkForUndefined(SymbolTable.java:489)
> [wsdl2java] at
> org.apache.axis.wsdl.symbolTable.SymbolTable.add(SymbolTable.java:384)
> [wsdl2java] at
> org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:371)
> [wsdl2java] at
> org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:358)
> [wsdl2java] at
> org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:243)
> [wsdl2java] at java.lang.Thread.run(Thread.java:536) 
> 
> My WSDL file looks like this: 
> 
> Any ideas? 
>  
> http://dsv.tiaacref.org";
> xmlns="http://schemas.xmlsoap.org/wsdl/";
> xmlns:apachesoap="http://xml.apache.org/xml-soap";
> xmlns:impl="http://dsv.tiaacref.org-impl";
> xmlns:intf="http://dsv.tiaacref.org";
> xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";
> xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
> xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";> 
> 
>  
> http://xml.apache.org/xml-soap";
> xmlns="http://www.w3.org/2001/XMLSchema";
> xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";> 
> 
>  namespace="http://schemas.xmlsoap.org/soap/encoding/"/> 
>  
>  
>  minOccurs="0" name="item"> 
>  
>  
>  name="key" type="xsd:anyType"/> 
>  name="value" type="xsd:anyType"/> 
>  
>  
>  
>  
>  
> 
>  type="apachesoap:Map"/> 
> 
>  
>  
>  
>  type="xsd:string" /> 
>  type="apachesoap:ArrayOfString" /> 
>  type="apachesoap:ArrayOfString" /> 
>  
>  
>  
> 
>  
>  
>  
>  type="xsd:string" /> 
>  
>  
>  
> 
>  
>  
>  
>  ref="soapenc:

RE: server-config.wsdd

Thank you.  That is the approach I will take then.

Thanks,
Ken

-Original Message-
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 09, 2005 8:20 AM
To: axis-user@ws.apache.org
Subject: Re: server-config.wsdd


I believe you need two different service names. You want to use the
java:RPC provider for both services. The java:RPC provider
automatically does the XML to java mapping for you. You only use the
java:MSG provider if you intend to process the SOAP message (as XML)
programmatically.

Anne

On 8/8/05, Hoying, Ken <[EMAIL PROTECTED]> wrote:
>  
>  
> 
> Currently, we have a simple web service that uses RPC/encoded with Java
> clients calling our web service. 
> 
> We now need to also support .NET clients.  Our MS development team has
> requested that we support document/literal. 
> 
> My question is, do I have to have two different service names to now support
> both of these or can I have just one and use the allowed methods to filter
> out which is which.  For example: 
> 
>   
>
>  
>
>   
>
>
>   
> 
>   use="literal"> 
>
>  
>
>   
>
>
>   
> 
> I am very new to all of this.  I am also wondering what the difference in
> the providers java:RPC and java:MSG and which I should be using. 
> 
> Any help would be greatly appreciated. 
> 
> Thank you, 
> Ken Hoying 
>  
> **
>  This message, including any attachments, contains confidential information
> intended for a specific individual and purpose, and is protected by law. If
> you are not the intended recipient, please contact sender immediately by
> reply e-mail and destroy all copies. You are hereby notified that any
> disclosure, copying, or distribution of this message, or the taking of any
> action based on it, is strictly prohibited.
>  TIAA-CREF
> **
>


**
This message, including any attachments, contains confidential information 
intended for a specific individual and purpose, and is protected by law.  If 
you are not the intended recipient, please contact sender immediately by reply 
e-mail and destroy all copies.  You are hereby notified that any disclosure, 
copying, or distribution of this message, or the taking of any action based on 
it, is strictly prohibited.
TIAA-CREF
**



server-config.wsdd

Title: server-config.wsdd







Currently, we have a simple web service that uses RPC/encoded with Java clients calling our web service.


We now need to also support .NET clients.  Our MS development team has requested that we support document/literal.


My question is, do I have to have two different service names to now support both of these or can I have just one and use the allowed methods to filter out which is which.  For example:

 MyService" provider="java:RPC">

  

    myHandler"/>

  

  

  myJavaMethod"/>

  

 


 MyService" provider="java:RPC" style="document" use="literal">

  

    myHandler"/>

  

  

  myNetMethod"/>

  

 


I am very new to all of this.  I am also wondering what the difference in the providers java:RPC and java:MSG and which I should be using.

Any help would be greatly appreciated.


Thank you,

Ken Hoying




**
This message, including any attachments, contains confidential information intended for a specific individual and purpose, and is protected by law.  If you are not the intended recipient, please contact sender immediately by reply e-mail and destroy all copies.  You are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited.
TIAA-CREF
**




[Q] Scope Changes

Title: [Q] Scope Changes






I am new to Axis and web services and am maintaining an existing Axis application.  I noticed that our application currently uses the default scope of Request.  However, I would like to change the scope to Application.  My questions is, does this require the Axis code for the client to the server to be regenerated or can I simply make the change to the config file?

Thank you,

Ken Hoying




**
This message, including any attachments, contains confidential information intended for a specific individual and purpose, and is protected by law.  If you are not the intended recipient, please contact sender immediately by reply e-mail and destroy all copies.  You are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited.
TIAA-CREF
**