RE: Web Sevice Auto Deployment

2005-09-01 Thread Feng Xie \(fxie\) 



Raj:
 
I have never used WSAD. I used Tomcat to host Axis. Sorry, 
I can't explain with why this doesn't work with WSAD.
 
-Feng


From: [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] Sent: Thursday, September 01, 
2005 3:53 PMTo: axis-user@ws.apache.orgSubject: RE: Web 
Sevice Auto Deployment
Thanks Feng!   why do I get 
 this error ? AxisFault faultCode: 
{http://xml.apache.org/axis/}Client 
faultSubcode: 
faultString: No such operation 'inquiryRequest' I am 
able to go http://testserver:9080/WSWAR/services/DataInquiry     and 
it says DataInquiry 
Hi there, this is an AXIS service! 

Perhaps there will be a form for 
invoking the service here... 
This means the webservice is available.. but I 
don't know why it gives me No such operation   error.  I deployed the 
same one on my PC it works fine .. but  I need to deploy it in the server 



  
  

"Feng Xie \(fxie\)" 
  <[EMAIL PROTECTED]> 
  09/01/2005 03:21 PM Please respond to axis-user 
                To:     
              cc:     
            
    Subject:        RE: Web Sevice Auto 
  DeploymentRaj:   
I agree with your understanding about the 
deployment based my own experience. Baseline: while the Axis engine is not 
running, direct editting of server-config.wsdd will has the same effect of 
running ClientAdmin while the Axis engine is running.   Feng 

From: [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] Sent: Thursday, September 01, 
2005 3:11 PMTo: axis-user@ws.apache.orgSubject: Web Sevice 
Auto Deployment Hello I created a simple Web Application in WSAD and 
deployed it successfully in my WebSphere Test Environment that comes with WSAD. 
I ran axis AdminClient to deploy the web service and noted that  it created 
server-config.wsdd  under WEB-INF/classes on my workspace     F             
     
    
      
    
    
             
        
        
    
  
    
     http://xml.apache.org/axis/wsdd/  http://xml.apache.org/axis/wsdd/  
     
     
        
             
     
    
 Then 
I created a WAR file  and deployed it in Websphere  Application Server 
.. I notice that my  DataInquiry   Web service is 
listed as one of the service . if I go the   
http://testserver:9080/WSWAR/services.( Remember I did not RUN the admin 
client to deploy the service on the application server)  when I try to 
invoke the service I am getting a RemoteException with an 
AxisFault shown below 
AxisFault faultCode: {http://xml.apache.org/axis/}Client faultSubcode: faultString: No such operation 
'inquiryRequest' My understanding was.. if  I have the service 
defined in the server-config.wsdd  I don't need to run the admin client 
 on the Application Server inorder to deploy the web service on the 
application server.. since it is defined on  server-config.wsdd .. axis 
will auto deploy the service..( I don't know the mechanism behind admin and 
version web servies , how they are auto deployed ) PLEASE correct me if I am wrong ( I hope so)...  I wanted to run 
the AdminClient but I don't have any user-id and password for the server ..I 
have access only to the Web Sphere Admin Console. to deploy EAR or WAR 
files Thanks a lot in advance for your help/Rja

RE: Web Sevice Auto Deployment

2005-09-01 Thread Feng Xie \(fxie\) 



Raj:
 
I agree with your understanding about the deployment based 
my own experience. Baseline: while the Axis engine is not running, direct 
editting of server-config.wsdd will has the same effect of running ClientAdmin 
while the Axis engine is running.
 
Feng


From: [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] Sent: Thursday, September 01, 
2005 3:11 PMTo: axis-user@ws.apache.orgSubject: Web Sevice 
Auto Deployment 
Hello I created a 
simple Web Application in WSAD and deployed it successfully in my WebSphere Test 
Environment that comes with WSAD. I ran axis AdminClient to deploy the web 
service and noted that  it created server-config.wsdd  under 
WEB-INF/classes on my workspace          
   F   
         
      
   
  
       
    
  
         
                
       
 
                 
      
 
             
     
      
http://xml.apache.org/axis/wsdd/ 
  
http://xml.apache.org/axis/wsdd/ 
      
                                                     
     Then I created a WAR file  and deployed it in Websphere 
 Application Server .. I notice that my  DataInquiry   
Web service is listed as one of the service . if I go the   
http://testserver:9080/WSWAR/services.( Remember I did not RUN the admin 
client to deploy the service on the application server)  when I try to 
invoke the service I am getting a 
RemoteException with an AxisFault shown below AxisFault  faultCode: 
{http://xml.apache.org/axis/}Client  faultSubcode:  faultString: No such operation 'inquiryRequest' 
My understanding was.. if  I have the 
service defined in the server-config.wsdd  I don't need to run the admin 
client  on the Application Server inorder to deploy the web service on the 
application server.. since it is defined on  server-config.wsdd .. axis 
will auto deploy the service..( I don't know the mechanism behind admin and 
version web servies , how they are auto deployed )  PLEASE correct me if I am wrong ( I hope so)... 
 I wanted to run the AdminClient but I don't have any user-id and password 
for the server ..I have access only to the Web Sphere Admin Console. to deploy 
EAR or WAR files Thanks a lot in 
advance for your help/Rja

RE: which Handler interface to implement ? in order to write a user defined handler to log SOAP request ?

2005-09-01 Thread Feng Xie \(fxie\) 



Tony:
 
Thanks for your help. I didn't search through my mail 
folder for your previous response before I sent out the 2nd with 
more information I got through debugger.
 
Finally, it works through a class extending 
 org.apache.axis.handlers.JAXRPCHandler. I guess it should work too by 
extending the BasicHandler.
 
Best Regards,
Feng


From: zze-ELSOKHON Tony RD-BIZZ-ISS 
[mailto:[EMAIL PROTECTED] Sent: Wednesday, August 
31, 2005 12:03 PMTo: axis-user@ws.apache.orgSubject: RE: 
which Handler interface to implement ? in order to write a user defined handler 
to log SOAP request ?


Feng,
 
As explained in the 
user guide, and as I told you in my previous post, you should extend 
org.apache.axis.handler.BasicHandler in order to write a user defined 
handler.
 
Best 
regards,
 




De : Feng Xie 
(fxie) [mailto:[EMAIL PROTECTED] Envoyé : mercredi 31 août 2005 
17:48À : 
axis-user@ws.apache.orgObjet : which Handler interface to 
implement ? in order to write a user defined handler to log SOAP request 
?
 

I am using Axis 
1.2RC3.

 

I wrote a simple Handler class which 
extends GenericHandler class, which in turn implements 
java.xml.rpc.handler.Handler. This handler interface provides API to printout 
Soap request. I deployed it into the requestFlow of a service which has 
following attribute  

 

However, when I send a Soap request 
to this server, an configuration exception occurs at 
WSDDDeployableItem.java:302. Using debugger, I found that Axis engine tries to 
cast a java.xml.rpc.handler.Handler instance to 
a org.apache.axis.Handler.

 

Which handler interface should I use 
for this case ? Seems like I could extend 
org.apache.axis.handler.JAXRPCHandler.

 

Thanks in 
advance,

Feng

build from Axis source

2005-08-31 Thread Feng Xie \(fxie\) 



In the build.xml of 
Axis 1.2RC3 source package, there are a few lines like  

 
  &properties;  
&paths;  &taskdefs;  &targets;
 
I couldn't find any 
documentation about what they mean although I guess they are referring to some 
default configuration -- such as property file. 
 
Could anyone help me 
with it ?
 
Thanks,
Feng

which Handler interface to implement ? in order to write a user defined handler to log SOAP request ?

2005-08-31 Thread Feng Xie \(fxie\) 



I am using Axis 
1.2RC3.
 
I wrote a simple 
Handler class which extends GenericHandler class, which in turn implements 
java.xml.rpc.handler.Handler. This handler interface provides API to printout 
Soap request. I deployed it into the requestFlow of a service which has 
following attribute  
 
However, when I send 
a Soap request to this server, an configuration exception occurs at 
WSDDDeployableItem.java:302. Using debugger, I found that Axis engine tries to 
cast a java.xml.rpc.handler.Handler instance to 
a org.apache.axis.Handler.
 
Which handler 
interface should I use for this case ? Seems like I could extend 
org.apache.axis.handler.JAXRPCHandler.
 
Thanks in 
advance,
Feng

classCastError after deploy a customized handler

2005-08-30 Thread Feng Xie \(fxie\) 



I developed a 
customized handler which extends GenericHandler and implemented it to log soap 
request message, its complete code is like :
 
 
public class 
SoapMsgLogHandler extends GenericHandler {  
private Logger soapLogger = null;
 
    
public void init(HandlerInfo config) {  
soapLogger = 
SubscriberDataMgrBindingImpl.baseContext.getCtxLog();    
}
 
    public QName[] getHeaders() 
{    return new 
QName[0];    }
 
    private boolean 
logMessage(MessageContext context, OutputStream out) 
{   if ((soapLogger != null) && 
(soapLogger.getLevel().toInt() <= 
Level.DEBUG.toInt()))   
{ SOAPMessageContext smg = 
(SOAPMessageContext) 
context; try 
{ 
smg.getMessage().writeTo(out); 
soapLogger.debug(out.toString()); 
} catch (Exception e) {}
 
 
return true;   
}   
else   return 
false;    }
 
    public boolean 
handleRequest(MessageContext context) {   
return logMessage(context,System.out);    }
 
    public boolean 
handleResponse(MessageContext context) 
{    return 
logMessage(context,System.out);    }
}
 
I add it into 
the requestFlow of one service, I did deploy it. However, while I was to invoke 
that service, I got SoapFault which indicates following error 

 
 faultString: 
org.apache.axis.ConfigurationException: 
java.lang.ClassCastExceptionjava.lang.ClassCastException at 
org.apache.axis.deployment.wsdd.WSDDDeployableItem.makeNewInstance(WSDDDeployableItem.java:302) at 
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableItem.java:274) at 
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem.java:260) at 
org.apache.axis.deployment.wsdd.WSDDChain.makeNewInstance(WSDDChain.java:125) at 
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableItem.java:274) at 
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem.java:260) at 
org.apache.axis.deployment.wsdd.WSDDService.makeNewInstance(WSDDService.java:422) at 
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableItem.java:274) at 
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem.java:260) at 
org.apache.axis.deployment.wsdd.WSDDDeployment.getService(WSDDDeployment.java:460) at 
org.apache.axis.configuration.FileProvider.getService(FileProvider.java:231) at 
org.apache.axis.AxisEngine.getService(AxisEngine.java:311) at 
org.apache.axis.MessageContext.setTargetService(MessageContext.java:755) at 
org.apache.axis.handlers.http.URLMapper.invoke(URLMapper.java:50) at 
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32) at 
org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118) at 
org.apache.axis.SimpleChain.invoke(SimpleChain.java:83) at 
org.apache.axis.server.AxisServer.invoke(AxisServer.java:239) at 
org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:697) at 
javax.servlet.http.HttpServlet.service(HttpServlet.java:709) at 
org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327) 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:214) at 
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at 
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at 
org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198) at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152) at 
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at 
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137) at 
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118) at 
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102) at 
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at 
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at 
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at 
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929) at 
org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160) at 
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799) at 
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proce

InvocationTargeException while undeploy some service

2005-08-30 Thread Feng Xie \(fxie\) 
 
The web service I deployed with Axis 1.2RC_3 and Tomcat 5.0 has been
ruuning for a few weeks. However, while I was
trying to undeploy those two services, I got back
InvocationTargeException. Interestingly, I am still able to deploy AND
undeploy the SOAPMonitor service from Axis user guide. 

Here is what I did for undeploy :

java -cp $AXISCLASSPATH org.apache.axis.client.AdminClient undeploy.wsdd
.

The undeploy.wsdd is very simple, it looks as below:









http://xml.apache.org/axis/wsdd/";>

  

  
  



Meanwhile, I checked the server-config.wsdd, it does have following
lines :



What could be wrong ?

Any hint would be appreciated.

Feng

RE: question on Axis Client --- sending multiple requests on a same connection before getting back response

2005-08-22 Thread Feng Xie \(fxie\) 
The normal operation of Axis Client is to send one Axis request and
block waiting for the response. It won't send out the next request until
the response is back. By using multi-threading on the client side, you
can send multiple requests simultanously, however, I guess those
requests are sent over different HTTP/HTTPS connections. What I like to
test is to send multiple requests over A SINGLE SAME connection in a
shot before getting back the first response. Basically, I like to test
how Axis behaves under HTTP pipe-lining.  

Thanks,
Feng
-Original Message-
From: Javier Gonzalez [mailto:[EMAIL PROTECTED] 
Sent: Friday, August 19, 2005 2:59 PM
To: axis-user@ws.apache.org
Subject: Re: question on Axis Client --- sending multiple requests on a
same connection before getting back response

m, run multipe threads that call the service? (or maybe I
misunderstand what you want to test?)

On 8/19/05, Feng Xie (fxie) <[EMAIL PROTECTED]> wrote:
>  
> Is there any way to let the Axis Client to send multiple requests 
> before getting back any response ?  In another words, how do I test 
> the "pipe lining" performance of webservice server ?
>   
> Thanks,
> Feng


--
Javier Gonzalez Nicolini

question on Axis Client --- sending multiple requests on a same connection before getting back response

2005-08-19 Thread Feng Xie \(fxie\) 



Is there any way to 
let the Axis Client to send multiple requests before getting back any 
response ?  In another words, how do I test the "pipe lining" 
performance of webservice server ?
 
Thanks,
Feng 

RE: How to add SSL/TLS compabiity into Axis Client

2005-08-15 Thread Feng Xie \(fxie\) 
Chris:

Thanks. 

That sounds too simple to me. :) However, it would be great if it is
really that simple. I am using Axis RC1.2RC3. So you mean the Axis
client will take care of everything else as long as I indicate the
desired service with "https". I guess I still need to configure the
client side's trust keystore.  

-Feng
-Original Message-
From: csj [mailto:[EMAIL PROTECTED] 
Sent: Monday, August 15, 2005 10:47 AM
To: axis-user@ws.apache.org
Subject: Re: How to add SSL/TLS compabiity into Axis Client

Change the endpoint to https after the server is properly configured.

..Chris

On Mon, 15 Aug 2005, Feng Xie (fxie) wrote:

>
>
> Hi,
>
> I have been using a simple Axis Client over HTTP, which directly calls

> the auto generated client side stubs ( assuming the web service is 
> called Foo, one the it's operation is called Foo_Operation1 )
>
> FooIF_Service service = new FooIF_ServiceLocator( ); Foo port = 
> service.getFoo(); port.FooOperation1( );
>
> My question, what should I do to add SSL/TLS capability into the above

> steps ?
>
> Thanks in advance,
> Feng
>
>

--
Chris Johnson
[EMAIL PROTECTED]

How to add SSL/TLS compabiity into Axis Client

2005-08-15 Thread Feng Xie \(fxie\) 
 

Hi, 

I have been using a simple Axis Client over HTTP, which directly calls
the auto generated client side stubs ( assuming the web service is
called Foo, one the it's operation is called Foo_Operation1 )

FooIF_Service service = new FooIF_ServiceLocator( );
Foo port = service.getFoo();
port.FooOperation1( );

My question, what should I do to add SSL/TLS capability into the above
steps ?

Thanks in advance,
Feng

RE: Urgent : exception during deployment ( Axis 1_2RC3)

2005-07-23 Thread Feng Xie \(fxie\) 
Please ignore my previous message about deploying axis into a
stand-alone Tomcat server case. I just tried and found the deployment is
OK.

However, I still have problems with deploying axis into an embedded
Tomcat server. In this case, I got almost nothing if I set the
log4j.catatory.org.apache.axis=INFO. And I got tons of log if I set the
log level to DEBUG. In this case, Axis couldn't find a class, but I
don't know exactly which class is missing since the log is really
confusing. ( more tha 15000 lines) here are some lines which I think is
relevant to the problem

typeQName:
{http://provision.dgw.cisco.com/types}removeApplicationSysDataResponseTy
pe
javaType:   null
inHeader:   false
outHeader:  false
@91a4fb(WSDDService.java:225)
at
org.apache.axis.deployment.wsdd.WSDDDeployment.(WSDDDeployment.jav
a:208)
at
org.apache.axis.deployment.wsdd.WSDDDocument.(WSDDDocument.java:78
)
at org.apache.axis.utils.Admin.processWSDD(Admin.java:110)
at org.apache.axis.utils.Admin.process(Admin.java:157)
at org.apache.axis.utils.Admin.AdminService(Admin.java:64)

I am sure there is axis.jar in axis/WEB-INF/lib/, and it has
org.apache.axis.AxisFault.class

I am really confused by the log now.

Could anyone help?

Thanks,

Feng
  

-Original Message-----
From: Feng Xie (fxie) 
Sent: Saturday, July 23, 2005 11:22 PM
To: axis-user@ws.apache.org
Subject: RE: Urgent : exception during deployment ( Axis 1_2RC3)

I believe this problem has something to do with Axis's classloading .

I just found even if I put the axis into standalone Tomcat server, I
mean the directory would be like
$CATALINA_HOME/webapps/axis/WEB-INF/myapp.jar ,  the axis log says "
java.lang.ClassNotFoundException:
com.mycom.myapp.provision.types.MyAppDataExceptionType" . However, I am
sure there is such class in myapp.jar. 

Am I missing anything about axis classloading ? 

Thanks,
Feng

-Original Message-
From: Feng Xie (fxie)
Sent: Saturday, July 23, 2005 7:03 PM
To: axis-user@ws.apache.org
Subject: Urgent : exception during deployment ( Axis 1_2RC3)

 
I am looking for help on a problem with deploying wsdd.

Here is the command and exception I got :
bash-2.05b$ java org.apache.axis.client.AdminClient deploy.wsdd

Processing file deploy.wsdd
Exception: AxisFault
 faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.userException
 faultSubcode:
 faultString: java.lang.reflect.InvocationTargetException
 faultActor:
 faultNode:
 faultDetail:
{http://xml.apache.org/axis/}hostname:tracy.mycompany.com



The axis is happy before I tried this deployment command( found all core
libs). 

I tried the same command against another stand-alone Tomcat server,
which host the Axis engine, it went smoothly without any problme. So I
suspect something missing with the Tomcat server running on
tracy.mycompany.com.

Thanks in advance,
Feng

RE: Urgent : exception during deployment ( Axis 1_2RC3)

2005-07-23 Thread Feng Xie \(fxie\) 
I believe this problem has something to do with Axis's classloading .

I just found even if I put the axis into standalone Tomcat server, I
mean the directory would be like
$CATALINA_HOME/webapps/axis/WEB-INF/myapp.jar ,  the axis log says "
java.lang.ClassNotFoundException:
com.mycom.myapp.provision.types.MyAppDataExceptionType" . However, I am
sure there is such class in myapp.jar. 

Am I missing anything about axis classloading ? 

Thanks,
Feng

-Original Message-----
From: Feng Xie (fxie) 
Sent: Saturday, July 23, 2005 7:03 PM
To: axis-user@ws.apache.org
Subject: Urgent : exception during deployment ( Axis 1_2RC3)

 
I am looking for help on a problem with deploying wsdd.

Here is the command and exception I got :
bash-2.05b$ java org.apache.axis.client.AdminClient deploy.wsdd

Processing file deploy.wsdd
Exception: AxisFault
 faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.userException
 faultSubcode:
 faultString: java.lang.reflect.InvocationTargetException
 faultActor:
 faultNode:
 faultDetail:
{http://xml.apache.org/axis/}hostname:tracy.mycompany.com



The axis is happy before I tried this deployment command( found all core
libs). 

I tried the same command against another stand-alone Tomcat server,
which host the Axis engine, it went smoothly without any problme. So I
suspect something missing with the Tomcat server running on
tracy.mycompany.com.

Thanks in advance,
Feng

Urgent : exception during deployment ( Axis 1_2RC3)

2005-07-23 Thread Feng Xie \(fxie\) 
 
I am looking for help on a problem with deploying wsdd.

Here is the command and exception I got :
bash-2.05b$ java org.apache.axis.client.AdminClient deploy.wsdd

Processing file deploy.wsdd
Exception: AxisFault
 faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.userException
 faultSubcode:
 faultString: java.lang.reflect.InvocationTargetException
 faultActor:
 faultNode:
 faultDetail:
{http://xml.apache.org/axis/}hostname:tracy.mycompany.com



The axis is happy before I tried this deployment command( found all core
libs). 

I tried the same command against another stand-alone Tomcat server,
which host the Axis engine, it went smoothly without any problme. So I
suspect something missing with the Tomcat server running on
tracy.mycompany.com.

Thanks in advance,
Feng

Axis with embedded tomcat :java.util.MissingResourceException: Can't find bundle for base name i18n, locale en_US

2005-07-08 Thread Feng Xie \(fxie\) 
Hi,

I am trying to integrate Axis into an embedded Tomcat5.0 engine running
in one application. 

I put all Axis libraries and resources into
$TOMCAT/webapps/axis/WEB-INF/lib/ and
$TOMCAT/webapps/axis/WEB-INF/classes/ ( like what I did with
Axis/Standalone Tomcat server integration ). However, when I tried
"http://localhost:8080/axis"; from my browser, I got back the following
page then an exception ( I am sure there is i18n_en.properties under
$TOMCAT/webapps/axis/WEB-INF/classes/ ). 
"
Apache-AXIS

We've moved to an internationalized top page. The new URL should be
automatically loaded after 5 seconds.
If you want to visit the new site immediately, please click the
above link. 

Copyright (c) 2005 The Apache Software Foundation. All rights reserved.
"



"type Exception report

message

description The server encountered an internal error () that prevented
it from fulfilling this request.

exception

org.apache.jasper.JasperException: Can't find bundle for base name i18n,
locale en_US

org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.ja
va:372)

org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)

org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)

root cause

java.util.MissingResourceException: Can't find bundle for base name
i18n, locale en_US

java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.ja
va:839)
java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:729)
java.util.ResourceBundle.getBundle(ResourceBundle.java:579)
org.apache.jsp.axis.index_jsp.getRB(index_jsp.java:72)
org.apache.jsp.axis.index_jsp.getMessage(index_jsp.java:168)
org.apache.jsp.axis.index_jsp.getMessage(index_jsp.java:106)
org.apache.jsp.axis.index_jsp.getLocaleChoice(index_jsp.java:82)
org.apache.jsp.axis.index_jsp._jspService(index_jsp.java:312)

org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94)
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)

org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.ja
va:324)

org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)

org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)

note The full stack trace of the root cause is available in the Apache
Tomcat/5.0 logs.
Apache Tomcat/5."

Why the operation name gets lost for document/literal binding

2005-06-30 Thread Feng Xie \(fxie\) 
 
It's been a puzzle for me since I started working on WSDL/SOAP.

For unwrapped document/literal binding, why the operation name get lost
in the soap messgae, which becomes one of the weak points of
document/literal binding. On the other hand, rpc/encoding binding let
SOAP messages carry the operation name.

I am just wondering the rational behind this decided by WSDL/SOAP
standard body. 

Any hint is appreciated.

Thanks,
Feng

RE: No such operation error - malformed WSDL?

2005-06-17 Thread Feng Xie \(fxie\) 
t;
> >   
> > 
> >   
> >  > name="REQUESTID" type="xsd:string"/>
> >  > type="xsd:string"/>
> >  > type="xsd:string"/>
> >  > type="xsd:string"/>
> >  > type="xsd:string"/>
> >   
> > 
> >   
> >   
> > 
> >   
> >  > type="xsd:string"/>
> >   
> > 
> >   
> > 
> >   
> >   
> >  > element="tns:ProvisioningTaskRequestOperation"/>
> >   
> >   
> > 
> >   
> >   
> > 
> >   
> >   
> > 
> >   
> >> type="tns:ProvisioningTaskRequestPortType">
> >  > transport="http://schemas.xmlsoap.org/soap/http"/>
> > 
> >>
> soapAction="ProvidentProvisioningTNS/ProvisioningTaskRequestOperation"
> />
> >   
> > 
> >   
> >   
> > 
> >   
> > 
> >   
> >   
> > Provident Provisioning Service
> >  > binding="tns:ProvisioningTaskRequestSoapBinding">
> >>
location="http://localhost:8880/axis/services/ProvidentProvisioning"/>
> > 
> >   
> > 
> > 
> > 
> >  
> >
> > On 6/15/05, Anne Thomas Manes <[EMAIL PROTECTED]> wrote:
> > > I just grabbed the WSDL operation name, but perhaps your Java 
> > > method
> 
> > > name is different? The "name" attribute should specify the Java 
> > > method
> >
> > > name.
> > >
> > > Anne
> > >
> > > On 6/15/05, Patrick Quinn <[EMAIL PROTECTED]> wrote:
> > > > Thanks Anne, Feng
> > > >
> > > > You have both given me food for thought and I won't give up.
> > > >
> > > > Anne, I did try adding the operation definition as you 
> > > > suggested. See below:
> > > >
> > > >  > > > xmlns="http://xml.apache.org/axis/wsdd/";
> > > > xmlns:java="http://xml.apache.org/axis/wsdd/providers/java";>
> > > >   
> > > >> value="ProvisioningTaskRequestPort"/>
> > > >> > > value="ProvidentProvisioningTNS.ProvisioningTa
> > > > skRequestSoapBindingSkeleton"/>
> > > >> value="ProvisioningTaskRequestPortType"/>
> > > >   
> > > >> > >  qname="ns:ProvisioningTaskRequest"
> > > >   />
> > > >> > > xmlns:ns="urn:ProvidentProvisioningTNS"
> > > > qname="ns:ProvisioningTaskRequest"
> > > >
> > type="java:ProvidentProvisioningTNS._ProvisioningTaskRequest"
> > > >
> > serializer="org.apache.axis.encoding.ser.BeanSerializerFactory"
> > > >
> > deserializer="org.apache.axis.encoding.ser.BeanDeserializerFactory"
> > > > encodingStyle=""
> > > >   />
> > > >   
> > > > 
> > > >
> > > >
> > > > But I now get the following error:
> > > >
> > > >
> > > > Exception in thread "main" AxisFault
> > > >  faultCode: 
> > > > {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
> > > >  faultSubcode:
> > > >  faultString: org.apache.axis.InternalException:
> > java.lang.Exception: Couldn't find a matching Java operation 
> > for WSDD operation "ProvisioningTaskRequestOperation" (0 
> > args)
> > > >  faultActor:
> > > >  faultNode:
> > > >  faultDetail:
> > > > {http://xml.apache.org/axis/}stackTrace: AxisFault
> > > >  faultCode:
> > {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
> > > >  faultSubcode:
> > > >  faultString: org.apache.axis.InternalException:
> > java.lang.Exception: Couldn&
> > > > ;apos;t find a matching Java operation for WSDD operation
> > &quot;Provisioning
> > > > TaskRequestOperation&quot; (0 args)
> > > >  faultActor:
> > > >  fau

RE: No such operation error - malformed WSDL?

2005-06-16 Thread Feng Xie \(fxie\) 
I have concern about wrapped style -- is it a standard way ?

-Feng 

-Original Message-
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, June 15, 2005 8:14 PM
To: axis-user@ws.apache.org
Subject: Re: No such operation error - malformed WSDL?

I finally allocated to review your WSDL. You have one error -- when
using document/literal, your message  definitions must reference
an element, not a type. And as I said before, it works a lot better if
you use wrapped style rather than document style.

Here's an updated WSDL that fixes the error and uses the wrapped
convention.


http://schemas.xmlsoap.org/wsdl/"; 
  xmlns:impl="urn:xml-soapadapter" 
  xmlns:intf="urn:xml-soapadapter" 
  xmlns:tns="urn:ProvidentProvisioningTNS" 
  xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
  xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; 
  xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; 
  targetNamespace="urn:ProvidentProvisioningTNS" 
  name="urn:ProvidentProvisioning">
  

  

  





  

  
  

  

  

  

  
  

  
  

  
  

  
  

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

  
  

  
  

  

  
  
Provident Provisioning Service

  http://localhost:8880/axis/services/ProvidentProvisioning"/>

  



 

On 6/15/05, Anne Thomas Manes <[EMAIL PROTECTED]> wrote:
> I just grabbed the WSDL operation name, but perhaps your Java method 
> name is different? The "name" attribute should specify the Java method

> name.
> 
> Anne
> 
> On 6/15/05, Patrick Quinn <[EMAIL PROTECTED]> wrote:
> > Thanks Anne, Feng
> >
> > You have both given me food for thought and I won't give up.
> >
> > Anne, I did try adding the operation definition as you suggested.
See below:
> >
> >  > xmlns="http://xml.apache.org/axis/wsdd/";
> > xmlns:java="http://xml.apache.org/axis/wsdd/providers/java";>
> >   
> >   
> >> value="ProvidentProvisioningTNS.ProvisioningTa
> > skRequestSoapBindingSkeleton"/>
> >   
> >   
> >>  qname="ns:ProvisioningTaskRequest"
> >   />
> >> xmlns:ns="urn:ProvidentProvisioningTNS"
> > qname="ns:ProvisioningTaskRequest"
> >
type="java:ProvidentProvisioningTNS._ProvisioningTaskRequest"
> >
serializer="org.apache.axis.encoding.ser.BeanSerializerFactory"
> >
deserializer="org.apache.axis.encoding.ser.BeanDeserializerFactory"
> > encodingStyle=""
> >   />
> >   
> > 
> >
> >
> > But I now get the following error:
> >
> >
> > Exception in thread "main" AxisFault
> >  faultCode: 
> > {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
> >  faultSubcode:
> >  faultString: org.apache.axis.InternalException: 
> > java.lang.Exception: Couldn't find a matching Java operation 
> > for WSDD operation "ProvisioningTaskRequestOperation" (0 
> > args)
> >  faultActor:
> >  faultNode:
> >  faultDetail:
> > {http://xml.apache.org/axis/}stackTrace: AxisFault
> >  faultCode: 
> > {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
> >  faultSubcode:
> >  faultString: org.apache.axis.InternalException: 
> > java.lang.Exception: Couldn& ;apos;t find a matching Java 
> > operation for WSDD operation &quot;Provisioning 
> > TaskRequestOperation&quot; (0 args)
> >  faultActor:
> >  faultNode:
> >  faultDetail:
> > org.apache.axis.InternalException: java.lang.Exception: Couldn't 
> > find a matching  Java operation for WSDD operation 
> > "ProvisioningTaskRequestOperation"
> > (0 args)
> >
> >
> > Is this something obvious, or is it better to take Feng's advice and
build from scratch using Java2WSDL?
> >
> > Thanks again,
> >
> > Pat
> >
> >
> > -Original Message-----
> > From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
> > Sent: Wed 15/06/2005 18:27
> > To: axis-user@ws.apache.org
> > Cc:
> > Subject: Re: No such operation error - malformed WSDL?
> >
> >
> >
> > Pat,
> >
> &g

RE: No such operation error - malformed WSDL?

2005-06-15 Thread Feng Xie \(fxie\) 
Pat:

It's a little strange to me that your deploy.wsdd ( which is generated
from WSDL2java, I assume ) doesn't have operation def.

You not only need add operation , perhaps need to add parameters for
this operation. Here is a snippet from my deploy.wsdd:


  http://provision.xxx.yyy.com/wsdl"/>
  
  
  
  
  
  
http://provision.xxx.yyy.com/types";
type="tns:soapReqHeaderType"
xmlns:tns="http://provision.xxx.yyy.com/types"; inHeader="true"/>
 

One thing I notice about your wsdl is it mixed type definition and
element definition together. You might want to generate a simple wsdl
from your java interface and get to know what does Axis tool like, then
modify your wsdl.

My wsdl has separate type definition and element definition and the
generated deploy.wsdd works fine ( doesn't require any extra touch ).

Hope it helps,
Feng

-Original Message-
From: Patrick Quinn [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, June 15, 2005 3:55 PM
To: axis-user@ws.apache.org
Subject: No such operation error - malformed WSDL?

Thanks Anne, Feng
 
You have both given me food for thought and I won't give up.
 
Anne, I did try adding the operation definition as you suggested. See
below:
 
http://xml.apache.org/axis/wsdd/";
xmlns:java="http://xml.apache.org/axis/wsdd/providers/java";>
  
  
  
  
  
  
  
  

 
 
But I now get the following error:
 
 
Exception in thread "main" AxisFault
 faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.userException
 faultSubcode:
 faultString: org.apache.axis.InternalException: java.lang.Exception:
Couldn't find a matching Java operation for WSDD operation
"ProvisioningTaskRequestOperation" (0 args)
 faultActor:
 faultNode:
 faultDetail:
{http://xml.apache.org/axis/}stackTrace: AxisFault
 faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.userException
 faultSubcode:
 faultString: org.apache.axis.InternalException: java.lang.Exception:
Couldn& ;apos;t find a matching Java operation for WSDD operation
&quot;Provisioning TaskRequestOperation&quot; (0 args)
 faultActor:
 faultNode:
 faultDetail:
org.apache.axis.InternalException: java.lang.Exception: Couldn't find a
matching  Java operation for WSDD operation
"ProvisioningTaskRequestOperation"
(0 args)
 
 
Is this something obvious, or is it better to take Feng's advice and
build from scratch using Java2WSDL?
 
Thanks again,
 
Pat
 

-Original Message- 
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] 
Sent: Wed 15/06/2005 18:27 
To: axis-user@ws.apache.org 
Cc: 
Subject: Re: No such operation error - malformed WSDL?



Pat,

You're correct -- you need to add an  definition to
your
WSDD to help Axis map the  message to
the
ProvisioningTaskRequestOperation method.

The format of the  definition is:

    
    
(If you used wrapped style, you wouldn't have this problem.)

Anne


On 6/15/05, Feng Xie (fxie) <[EMAIL PROTECTED]> wrote:
> 
> Pat:
>  
> Too bad to hear that. Don't give up.
>  
> In my case ( Axis + Tomcat 5 ), the soapAction is always "" in
WSDL. What I
> did is come up a very basic Java interface and let Java2WSDL
to generate a
> base WSDL. I then enhance the WSDL. I noticed that the
soapAction is "" in
> the based WSDL created by Java2WSDL.
>  
> However, the soapAction in your WSDL is not "". Not sure
whether that will
> affect the dispatch process.
>  
> Feng
> 



__
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
__

RE: No such operation error - malformed WSDL?

2005-06-15 Thread Feng Xie \(fxie\) 
Title: Message



Pat:
 
Too bad to hear that. Don't give up. 
 
In my case ( Axis + Tomcat 5 ), the soapAction is always "" 
in WSDL. What I did is come up a very basic Java interface and let 
Java2WSDL to generate a base WSDL. I then enhance the WSDL. I noticed that the 
soapAction is "" in the based WSDL created by Java2WSDL. 
 
However, the soapAction in your WSDL is not "". Not sure 
whether that will affect the dispatch process. 
 
Feng


From: Patrick Quinn 
[mailto:[EMAIL PROTECTED] Sent: Wednesday, June 15, 2005 
12:11 PMTo: axis-user@ws.apache.orgSubject: RE: No such 
operation error - malformed WSDL?

Feng
 
no it 
didn't cure the problem I'm afraid.
 
I've 
seen posts before about the same problem, but there doesn't seem to be an 
obvious remedy.
 
If I 
knew for sure that this is a problem with the WSDL then I would be 
almost happy knowing that, and I could persevere in trying to cure it - but 
at the moment I am wondering whether it is Axis itself, or some configuration 
problem.
 
I have 
heard that there are problems with Axis and 'doc/lit' style, and that it is 
better to use 'wrapped', but I am constrained to what our customer 
wants.
 
At 
this stage I really don't want to ditch Axis and look for another SOAP engine 
... :-/

  
  -Original Message-From: Feng Xie (fxie) 
  [mailto:[EMAIL PROTECTED] Sent: 15 June 2005 17:03To: 
  axis-user@ws.apache.orgSubject: RE: No such operation error - 
  malformed WSDL?
  Did it fix your problem ? 
   
  WSDL2java probable doesn't pay attention onto the 
  location line.
   
  -Feng
  
  
  From: Patrick Quinn 
  [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 15, 2005 
  11:57 AMTo: axis-user@ws.apache.orgSubject: RE: No such 
  operation error - malformed WSDL?
  
  This 
  is the generated deployment file. Maybe it needs a description of the missing 
  operation?
  If 
  so, I wonder why the WSDL2Java did not generate this?
   
   
   
   
      xmlns="http://xml.apache.org/axis/wsdd/"    
  xmlns:java="http://xml.apache.org/axis/wsdd/providers/java">
   
    
   
        
    
    
    
    
  
    
      
  xmlns:ns="urn:ProvidentProvisioningTNS"    
  qname="ns:ProvisioningTaskRequest"    
  type="java:ProvidentProvisioningTNS._ProvisioningTaskRequest"    
  serializer="org.apache.axis.encoding.ser.BeanSerializerFactory"    
  deserializer="org.apache.axis.encoding.ser.BeanDeserializerFactory"    
  encodingStyle=""  />  
  
   
  

-Original Message-From: Feng Xie 
(fxie) [mailto:[EMAIL PROTECTED] Sent: 15 June 2005 
16:22To: axis-user@ws.apache.orgSubject: RE: No such 
operation error - malformed WSDL?
Patrick:
 
Can you replace the location line in your wsdl with the 
following line and regenerate stub and skeleton ? 
 
="http://localhost:8880/axis/services/ProvisioningTaskRequestPort">
 
Feng



From: Patrick Quinn 
[mailto:[EMAIL PROTECTED] Sent: Wednesday, June 15, 
2005 10:37 AMTo: axis-user@ws.apache.orgSubject: No 
such operation error - malformed WSDL?



Hi
 
I have 
received a WSDL from a customer. The style is document/literal. The 
stubs/skeleton are generated fine when WSDL2Java is run, but a 'no such operation' error appears 
when the client code attempts the remote call with the bean.
 

Is there 
something incorrect in the WSDL that has caused the 
generated WSDD deployment file to be 
incomplete?

 
Many 
thanks for any help that can be provided. 
Data is below.
 
Regards
 
Patrick 
Quinn
 
 
error 
text
 
 
Exception in 
thread "main" AxisFault faultCode: 
{http://schemas.xmlsoap.org/soap/envelope/}Server.generalException faultSubcode: 
 faultString: No such operation 
'ProvisioningTaskRequest' faultActor: 
 faultNode:  faultDetail: 
    
{http://xml.apache.org/axis/}stackTrace: AxisFault faultCode: 
{http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
 faultSubcode:  faultString: No such 
operation 
&apos;ProvisioningTaskRequest&apos; faultActor: 
 faultNode:  faultDetail: 
 
No such 
operation 
'ProvisioningTaskRequest'    at 
org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:260)
. . .    at 
org.apache.axis.client.Call.invoke(Call.java:1691)    
at 
ProvidentProvisioningTNS.ProvisioningTaskRequestSoapBindingStub.provisioningTaskRequestOperation(ProvisioningTaskRequestSoapBindingStub.java:140)    
at ProvidentProvisioningTNS.Main2.main(Main2.java:63)
No 
such ope

RE: No such operation error - malformed WSDL?

2005-06-15 Thread Feng Xie \(fxie\) 
Title: Message



Did it fix your problem ? 
 
WSDL2java probable doesn't pay attention onto the location 
line.
 
-Feng


From: Patrick Quinn 
[mailto:[EMAIL PROTECTED] Sent: Wednesday, June 15, 2005 
11:57 AMTo: axis-user@ws.apache.orgSubject: RE: No such 
operation error - malformed WSDL?

This 
is the generated deployment file. Maybe it needs a description of the missing 
operation?
If so, 
I wonder why the WSDL2Java did not generate this?
 
 
 
 
    
xmlns="http://xml.apache.org/axis/wsdd/"    
xmlns:java="http://xml.apache.org/axis/wsdd/providers/java">
 
  
 
      
    
  
  

  
    
xmlns:ns="urn:ProvidentProvisioningTNS"    
qname="ns:ProvisioningTaskRequest"    
type="java:ProvidentProvisioningTNS._ProvisioningTaskRequest"    
serializer="org.apache.axis.encoding.ser.BeanSerializerFactory"    
deserializer="org.apache.axis.encoding.ser.BeanDeserializerFactory"        
encodingStyle=""  />  

 

  
  -Original Message-From: Feng Xie (fxie) 
  [mailto:[EMAIL PROTECTED] Sent: 15 June 2005 16:22To: 
  axis-user@ws.apache.orgSubject: RE: No such operation error - 
  malformed WSDL?
  Patrick:
   
  Can you replace the location line in your wsdl with the 
  following line and regenerate stub and skeleton ? 
   
  ="http://localhost:8880/axis/services/ProvisioningTaskRequestPort">
   
  Feng
  
  
  
  From: Patrick Quinn 
  [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 15, 2005 
  10:37 AMTo: axis-user@ws.apache.orgSubject: No such 
  operation error - malformed WSDL?
  
  
  
  Hi
   
  I have 
  received a WSDL from a customer. The style is document/literal. The 
  stubs/skeleton are generated fine when WSDL2Java is run, but a 'no such operation' error appears when 
  the client code attempts the remote call with the bean.
   
  
  Is there something 
  incorrect in the WSDL that has caused the 
  generated WSDD deployment file to be 
  incomplete?
  
   
  Many thanks 
  for any help that can be provided. Data is 
  below.
   
  Regards
   
  Patrick 
  Quinn
   
   
  error 
text
   
   
  Exception in 
  thread "main" AxisFault faultCode: 
  {http://schemas.xmlsoap.org/soap/envelope/}Server.generalException faultSubcode: 
   faultString: No such operation 
  'ProvisioningTaskRequest' faultActor: 
   faultNode:  faultDetail: 
      
  {http://xml.apache.org/axis/}stackTrace: AxisFault faultCode: 
  {http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
   faultSubcode:  faultString: No such 
  operation 
  &apos;ProvisioningTaskRequest&apos; faultActor: 
   faultNode:  faultDetail: 
   
  No such operation 
  'ProvisioningTaskRequest'    at 
  org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:260)
  . . .    at 
  org.apache.axis.client.Call.invoke(Call.java:1691)    
  at 
  ProvidentProvisioningTNS.ProvisioningTaskRequestSoapBindingStub.provisioningTaskRequestOperation(ProvisioningTaskRequestSoapBindingStub.java:140)    
  at ProvidentProvisioningTNS.Main2.main(Main2.java:63)
  No such 
  operation 
  'ProvisioningTaskRequest'    at 
  org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:260)etc.
  
  
  The WSDL 
  looks like this (I suspect it is based on the example found 
  at www.w3.org/TR/wsdl):
   
   
  http://schemas.xmlsoap.org/wsdl/" 
  xmlns:impl="urn:xml-soapadapter" xmlns:intf="urn:xml-soapadapter" 
  xmlns:tns="urn:ProvidentProvisioningTNS" xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
  xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" targetNamespace="urn:ProvidentProvisioningTNS" 
  name="urn:ProvidentProvisioning">    
      
      
      
      
      
      
      
      
      
      
      
      
      
      
          
      
          
      
          
      
      
      
      
          
  http://schemas.xmlsoap.org/soap/http"/>    
      
      
      
      
      
      
      
      
      
     

RE: No such operation error - malformed WSDL?

2005-06-15 Thread Feng Xie \(fxie\) 
Title: Message



Patrick:
 
Can you replace the location line in your wsdl with the 
following line and regenerate stub and skeleton ? 
 
="http://localhost:8880/axis/services/ProvisioningTaskRequestPort">
 
Feng



From: Patrick Quinn 
[mailto:[EMAIL PROTECTED] Sent: Wednesday, June 15, 2005 
10:37 AMTo: axis-user@ws.apache.orgSubject: No such 
operation error - malformed WSDL?



Hi
 
I have 
received a WSDL from a customer. The 
style is document/literal. The stubs/skeleton are generated fine when 
WSDL2Java is run, but a 'no such 
operation' error appears when the client code attempts the remote 
call with the bean.
 

Is there something 
incorrect in the WSDL that has caused the 
generated WSDD deployment file to be 
incomplete?

 
Many thanks 
for any help that can be provided. Data is 
below.
 
Regards
 
Patrick 
Quinn
 
 
error text
 
 
Exception in thread 
"main" AxisFault faultCode: 
{http://schemas.xmlsoap.org/soap/envelope/}Server.generalException faultSubcode: 
 faultString: No such operation 
'ProvisioningTaskRequest' faultActor: 
 faultNode:  faultDetail: 
    
{http://xml.apache.org/axis/}stackTrace: AxisFault faultCode: 
{http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
 faultSubcode: 
 faultString: No such operation 
'ProvisioningTaskRequest' faultActor: 
 faultNode:  faultDetail: 
 
No such operation 
'ProvisioningTaskRequest'    at 
org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:260)
. . .    at 
org.apache.axis.client.Call.invoke(Call.java:1691)    
at 
ProvidentProvisioningTNS.ProvisioningTaskRequestSoapBindingStub.provisioningTaskRequestOperation(ProvisioningTaskRequestSoapBindingStub.java:140)    
at ProvidentProvisioningTNS.Main2.main(Main2.java:63)
No such 
operation 
'ProvisioningTaskRequest'    at 
org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:260)etc.


The WSDL 
looks like this (I suspect it is based on the example found 
at www.w3.org/TR/wsdl):
 
 
http://schemas.xmlsoap.org/wsdl/" 
xmlns:impl="urn:xml-soapadapter" xmlns:intf="urn:xml-soapadapter" 
xmlns:tns="urn:ProvidentProvisioningTNS" xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" 
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" targetNamespace="urn:ProvidentProvisioningTNS" 
name="urn:ProvidentProvisioning">    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
        
    
        
    
        
    
    
    
    
        
http://schemas.xmlsoap.org/soap/http"/>    
    
    
    
    
    
    
    
    
    
        
Provident Provisioning 
Service    
    
http://localhost:8880/axis/services/ProvidentProvisioning"/>    
    
        
        

 
 
deploy.wsdd file
 

    
xmlns="http://xml.apache.org/axis/wsdd/"    xmlns:java="http://xml.apache.org/axis/wsdd/providers/java">
 
  
 
      
      
    
      
    
    
/>  
  
  
 
  
    
xmlns:ns="urn:ProvidentProvisioningTNS"    
qname="ns:>ProvisioningTaskRequest"    
type="java:ProvidentProvisioningTNS._ProvisioningTaskRequest"    
serializer="org.apache.axis.encoding.ser.BeanSerializerFactory"    
deserializer="org.apache.axis.encoding.ser.BeanDeserializerFactory"    
encodingStyle=""  />  

 


 __This 
email has been scanned by the MessageLabs Email Security System.For more 
information please visit http://www.messagelabs.com/email 
__

using Axis client with HTTP/1.1 and pipeling

2005-06-14 Thread Feng Xie \(fxie\) 



Hi,
 
I heard that it 
requires some extra work to make Axis client work with HTTP/1.1. Let's assume it 
works with HTTP/1.1, how does it take advantage of HTTP/1.1 's pipelinig feature 
? Given the fact that each client call is a synchronized call.  My 
understanding is that even you could have multiple threads to call mulitple stub 
methods "simultaneously", those Soap requests would be sent over multiple 
*different* connections, instead of pipelined into a single connection. 

 
Any hint on this 
will be appreciated.
 
Feng
 
 

RE: AXIS 1.2 / Style Wrapped / array operation arguments

2005-06-14 Thread Feng Xie \(fxie\) 
Ephemeris :

Please let me know if you see any result with document/literal different
from what I described.

Thanks,
-Feng 

-Original Message-
From: Ephemeris Lappis [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 14, 2005 2:22 PM
To: axis-user@ws.apache.org
Subject: RE: AXIS 1.2 / Style Wrapped / array operation arguments

Few weeks ago, all my tests used document/literal style, but i don't
remember how the empty arrays were exchanged, if i tested it. I could
test the same services with document style to compare the results, but i
suppose a confirmation of this behaviour should be a good thing...
--
Ephemeris Lappis

>>> -Original Message-----
>>> From: Feng Xie (fxie) [mailto:[EMAIL PROTECTED]
>>> Sent: Tuesday, June 14, 2005 8:10 PM
>>> To: axis-user@ws.apache.org
>>> Subject: RE: AXIS 1.2 / Style Wrapped / array operation arguments
>>>
>>>
>>> My test on document/literal doesn't show this behaviour. With 
>>> document/literal, I have tried with string, Integer and byte[], all 
>>> worked fine.
>>>
>>> -Feng
>>>
>>> -Original Message-
>>> From: Ephemeris Lappis [mailto:[EMAIL PROTECTED]
>>> Sent: Tuesday, June 14, 2005 1:41 PM
>>> To: Axis-User
>>> Subject: AXIS 1.2 / Style Wrapped / array operation arguments
>>>
>>> Hello.
>>>
>>> Just for a confirmation...
>>>
>>> I'm testing again the wrapped style services, with different kid of 
>>> arguments and return types. It seems, for what my server side class 
>>> receives, that the client call doesn't make difference to marshall 
>>> null and empty array arguments.
>>>
>>> For example, for an operation with the java signature :
>>>
>>> public void testArrayOfInteger(int[] values)
>>>
>>> the two invocations on the service stub :
>>>
>>> testArrayOfInteger(null)
>>> or
>>> testArrayOfInteger(new int[0])
>>>
>>> produce, for the server class invocation a null argument.
>>>
>>> It seems to be the same for arrays of objects, like strings or 
>>> custom types.
>>> For the moment, this doesn't represent a real problem, but i'd like 
>>> to know if this behaviour is natural, or may be a wsdl default or a
bug...
>>>
>>> This tests are all done with wrapped/literal style services. I don't

>>> know if other style/use produce the same...
>>>
>>> Thanks.
>>>
>>> --
>>> Ephemeris Lappis
>>>
>>>
>>>
>>>
>>>
>>> --
>>> Philippe Maseres

RE: AXIS 1.2 / Style Wrapped / array operation arguments

2005-06-14 Thread Feng Xie \(fxie\) 
My test on document/literal doesn't show this behaviour. With
document/literal, I have tried with string, Integer and byte[], all
worked fine.

-Feng 

-Original Message-
From: Ephemeris Lappis [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 14, 2005 1:41 PM
To: Axis-User
Subject: AXIS 1.2 / Style Wrapped / array operation arguments

Hello.

Just for a confirmation...

I'm testing again the wrapped style services, with different kid of
arguments and return types. It seems, for what my server side class
receives, that the client call doesn't make difference to marshall null
and empty array arguments.

For example, for an operation with the java signature :

public void testArrayOfInteger(int[] values)

the two invocations on the service stub :

testArrayOfInteger(null)
or
testArrayOfInteger(new int[0])

produce, for the server class invocation a null argument.

It seems to be the same for arrays of objects, like strings or custom
types.
For the moment, this doesn't represent a real problem, but i'd like to
know if this behaviour is natural, or may be a wsdl default or a bug...

This tests are all done with wrapped/literal style services. I don't
know if other style/use produce the same...

Thanks.

--
Ephemeris Lappis





--
Philippe Maseres

How to carry Soap:header along with Soap:fault

2005-06-13 Thread Feng Xie \(fxie\) 



I hope I can get 
some help on this issue:
 
In my wsdd, I have 
document/literal binding for the following operation ( please see the 
snippet from my wsdl) , if the server return normally for this 
operation, the Soap response carries the Soap:header. However, whenever an 
expection ( either remoteException or data defined exception) is thrown at the 
server side, the Soap response message only carries the Soap:fault element. NO 
Soap:header element.
 
Thanks in 
advance,
 
Feng
 
The snippet from my 
wsdl






input>



output>


fault>
operation>

pls help, how to turn on Axis1.2 RC3's SOAP 1.2 feature

2005-06-10 Thread Feng Xie \(fxie\) 



Hi,
 
I am using Axis1.2 
RC3 for both client and server sides. I found the SOAP message sent by the 
client is SOAP1.1 message. 
 
Is there any way to 
let the client send SOAP1.2 message ? 
 
Thanks,Feng

how to printout SOAP response with soap:fault related to server side exception

2005-06-08 Thread Feng Xie \(fxie\) 



Hi,
 
I could catch Soap 
request and response using Axis soapmonitor service. However, I found that 
whenever my service throws an exception, either remoteException or user defined 
"local" exception, the soapmonitor response window won't show the soap response 
message. I like to check the soap:fault element inside the soap response 
message.
 
Could anyone help me 
with this ? Or do it on the client side ?
 
Thanks,
Feng

RE: happyaxis JAXP implementation found at an unknown location

2005-06-07 Thread Feng Xie \(fxie\) 
Try following cmd to dig out the jar file:
Find . -name *.jar |xargs grep "javax.xml.parsers.SAXParserFactory"

Hope it helps,
Feng

-Original Message-
From: Henry Lu [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 07, 2005 1:53 PM
To: axis-user@ws.apache.org; [EMAIL PROTECTED]
Subject: RE: happyaxis JAXP implementation found at an unknown location

I copied rt.jar file to both tomcat common/lib and axis/WEB-INF/lib, but I 
still got:

Found JAXP implementation ( javax.xml.parsers.SAXParserFactory ) at an unknown 
location

Why?

-Henry

>>> [EMAIL PROTECTED] 6/7/2005 1:24:36 PM >>>
thanks!

you're right, there is a SAXParser class in the rt.jar that came with JDK 5.0!


--- "Ruiz González, Jose de Jesus" <[EMAIL PROTECTED]> wrote:

> Axis is finding that package from Java
> 
> 
> José de Jesús Ruiz Gonzalez
> Departamento de Sistemas
> México Asistencia S.A. de C.V.
> Sistema Internacional de Asistencia Mapfre
> 
> * mailto:[EMAIL PROTECTED]
> *(52) 55 + 54801298
> 
> *Fax(52) 55 + 56112011
> 
> 
> 
> 
> -Mensaje original-
> De: Woodchuck [mailto:[EMAIL PROTECTED] Enviado el: Martes, 07 de 
> Junio de 2005 11:08 a.m.
> Para: axis-user@ws.apache.org
> Asunto: happyaxis JAXP implementation found at an unknown location
> 
> hihi all,
> 
> i'm currently using axis 1.2 in tomcat 5.5.9
> 
> everything is fine but i'm curious to know where axis is finding the 
> JAXP implementation ( javax.xml.parsers.SAXParserFactory ).
> 
> i do not have the jaxp-api.jar anywhere at all.
> 
> has anyone else noticed this as well (who are using Tomcat 5.5 also)?
> 
> i even did a file search for the string "javax.xml" but it is not 
> anywhere within tomcat.
> 
> anyone have any ideas or know the answer to this mystery?
> 
> thanks in advance,
> woodchuck
> 
> 
>   
> __
> Yahoo! Mail Mobile
> Take Yahoo! Mail with you! Check email on your mobile phone. 
> http://mobile.yahoo.com/learn/mail
> 




__ 
Discover Yahoo! 
Find restaurants, movies, travel and more fun for the weekend. Check it out! 
http://discover.yahoo.com/weekend.html 




**
Electronic Mail is not secure, may not be read every day, and should not be 
used for urgent or sensitive issues.

Axis 1.2 's support to Soap/1.1 and Soap/1.2

2005-06-07 Thread Feng Xie \(fxie\) 




Hi,
I have a question on Axis1.2 's behavior regarding 
interaction between
SOAP/1.1 and SOAP/1.2.
According to SOAP1.2 spec regarding the interaction 
between SOAP1.1 and SOAP1.2, it says :
1. A SOAP/1.1 only node receiving a SOAP/1.2 message 
will according to
SOAP/1.1 generate a version mismatch SOAP fault based 
on a SOAP/1.1 message construct.
2. A SOAP/1.2 node receiving a SOAP/1.1 message 
either :
2.1. May process the message as a SOAP/1.1 message ( 
if supported )
or
2.2. Must generate a version mismatch SOAP fault 
based on a SOAP/1.1 message construct following SOAP/1.1 semantics using a 
SOAP/1.1 binding to the underlying protocol. The SOAP fault SHOULD include an 
Upgrade SOAP header block as defined in SOAP/1.2 spec indicating support for 
SOAP/1.2. This allows a receiving SOAP/1.1 node to correctly interpret the SOAP 
fault generated by SOAP/1.2 node.
Axis 1.2 releas notes say it support Soap1.1 and 
Soap/1.2. So what is the behavior when Axis1.2 soap node receives a Soap/1.1 
message ? Will it process this message as a Soap/1.1 message or reject it 
?
Thanks in advance,
Feng