AW: deserializing error

2005-06-28 Thread Ferruh Zamangoer
Can you attach your ProvidentResponse class and your deploy.wsdd. 

 

 

 

  _  

Von: Patrick Quinn [mailto:[EMAIL PROTECTED] 
Gesendet: Montag, 27. Juni 2005 23:47
An: axis-user@ws.apache.org
Betreff: RE: deserializing error

 

Hi

 

I added the lines suggested below to the deploy.wsdd file (actually, I only
needed to add the encoding style URL, the rest was already there).

 

The error remains the same:

 

Exception in thread main AxisFault
 faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
 faultSubcode:
 faultString: org.xml.sax.SAXException: Deserializing parameter
'ProvidentResponse':  could not find deserializer for type
{http://ProvidentConnector.ProvidentResponseToOrch}ProvidentResponse
 faultActor:
 faultNode:
 faultDetail:

 

 

Clearly I'm lacking a deserializer!

 

Does this remain a deployment issue, or is there more than meets the eye
going on here - should I be programatically providing a deserializer?

 

Thanks in advance for any opinions proffered.

 

Pat

 

-Original Message- 
From: Ferruh Zamangoer [mailto:[EMAIL PROTECTED] 
Sent: Mon 27/06/2005 11:13 
To: axis-user@ws.apache.org 
Cc: 
Subject: AW: deserializing error

Yes you have to edit manually your deploy.wsdd with the following lines:

 

typeMapping

xmlns:ns= http://ProvidentConnector.ProvidentResponseToOrch
http://ProvidentConnector.ProvidentResponseToOrch;

qname=ns: ProvidentResponse

type=java:[packagename of your class]. ProvidentResponse

serializer=org.apache.axis.encoding.ser.BeanSerializerFactory

deserializer=org.apache.axis.encoding.ser.BeanDeserializerFactory

encodingStyle=http://schemas.xmlsoap.org/soap/encoding/;

  /

 

Then you must redeploy you service.

 

Hope it works.

 

Regards

Ferruh 

 


  _  


Von: Patrick Quinn [mailto:[EMAIL PROTECTED] 
Gesendet: Sonntag, 26. Juni 2005 19:55
An: axis-user@ws.apache.org
Betreff: RE: deserializing error

 

Just bouncing this one, as the question was fairly generic:

 

 The server-config.wsdd file I notice does not have the bean mapping
described by Mark.

 Should I add this manually myself?

 

Is it common for the wsdl-generated wsdd deployment files to be lacking?

 

I would have expected AXIS to cover everything off, or if not, at least
provide some kind of tutorial/guide on how to modify the deployment files
where they are lacking.

 

Thanks


Pat

 

-Original Message- 
From: Patrick Quinn 
Sent: Sat 25/06/2005 16:25 
To: axis-user@ws.apache.org; axis-user@ws.apache.org 
Cc: 
Subject: RE: deserializing error

Hi Guys

Thanks for your responses, really appreciated.

Yes, the code segment exists as follows:

qName = new
javax.xml.namespace.QName(http://ProvidentConnector.ProvidentResponseToOrch
, ProvidentResponse);
cachedSerQNames.add(qName);
cls =
ProvidentResponseToOrch.ProvidentConnector.ProvidentResponse.class;
cachedSerClasses.add(cls);
cachedSerFactories.add(beansf);
cachedDeserFactories.add(beandf);
}

I think this looks correct.

The server-config.wsdd file I notice does not have the bean mapping
described by Mark. Should I add this manually myself?

I'm new to Axis - I presume the server-config.wsdd is updated when a service
is deployed (using the AdminService command). So my guess is that the
deploy.wsdd generated by WSDL2Java is not generating the type mapping.
Should it be doing so, or is it understood that the user should add this
information separately?

Thanks again for all the help, it is very useful and enlightening.

Patrick



-Original Message-
From: Ferruh Zamangör [mailto:[EMAIL PROTECTED]
Sent: Fri 24/06/2005 18:04
To: axis-user@ws.apache.org
Cc:
Subject: RE: deserializing error
   
   

Hi Patrick,
   
you have a generated stub class. look at your stub class if this
code
segement exists
   
qName = new javax.xml.namespace.QName(urn:[yourpacckagename]
ProvidentResponse);
cachedSerQNames.add(qname);
cls = yourpackagename.ProvidentResponse.class;
cachedSerClasses.add(cls);
cachedSerFactories.add(beansf);
cachedDeserFactories.add(beandf);
   
This is the code which must be in your stub class. Also you must be
sure
that you have deployed the service with the right typeMapping how
it's
described by Mark.
   
Regards
Ferruh
   
   
   
 --- Ursprüngliche Nachricht ---
 Von: Patrick Quinn [EMAIL PROTECTED]
 An: axis-user@ws.apache.org
 Betreff: RE: deserializing error
 Datum: Fri, 24 Jun 2005 17:00:32 +0100

 Thanks for the tip.

 The registerTypeMapping call is already made in the stub, as part
of
 createCall():


 synchronized 

LogConfigurationException on Webapp startup

2005-06-28 Thread Alexandre Touret

I deployed a simple EAR into OC4J.
I had uncommented the search class loader instruction in the 
orion-web.xml and my webapp runs well in tomcat.
But in OC4J 10.1.2 I have the following error on the startup of the 
component and on deployment:

05/06/24 09:16:02 java.lang.ExceptionInInitializerError
05/06/24 09:16:02 at java.lang.Class.forName0(Native Method)
05/06/24 09:16:02 at java.lang.Class.forName(Class.java:219)
05/06/24 09:16:02 at 
com.evermind.server.http.HttpApplication.initDefaultServlets(HttpApplication.java:4948)
05/06/24 09:16:02 at 
com.evermind.server.http.HttpApplication.initDynamic(HttpApplication.java:746)
05/06/24 09:16:02 at 
com.evermind.server.http.HttpApplication.init(HttpApplication.java:542)
05/06/24 09:16:02 at 
com.evermind.server.Application.getHttpApplication(Application.java:889)
05/06/24 09:16:02 at 
com.evermind.server.http.HttpServer.getHttpApplication(HttpServer.java:690)
05/06/24 09:16:02 at 
com.evermind.server.http.HttpSite.initApplications(HttpSite.java:586)
05/06/24 09:16:02 at 
com.evermind.server.http.HttpSite.setConfig(HttpSite.java:263)
05/06/24 09:16:02 at 
com.evermind.server.http.HttpServer.setSites(HttpServer.java:261)
05/06/24 09:16:02 at 
com.evermind.server.http.HttpServer.setConfig(HttpServer.java:162)
05/06/24 09:16:02 at 
com.evermind.server.ApplicationServer.initializeHttp(ApplicationServer.java:2385)
05/06/24 09:16:02 at 
com.evermind.server.ApplicationServer.setConfig(ApplicationServer.java:1542)
05/06/24 09:16:02 at 
com.evermind.server.ApplicationServerLauncher.run(ApplicationServerLauncher.java:92)

05/06/24 09:16:02 at java.lang.Thread.run(Thread.java:534)
05/06/24 09:16:02 Caused by: 
org.apache.commons.logging.LogConfigurationException: 
java.lang.ExceptionInInitializerError (Caused by 
java.lang.ExceptionInInitializerError)
05/06/24 09:16:02 at 
org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:538)
05/06/24 09:16:02 at 
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:235)
05/06/24 09:16:02 at 
org.apache.commons.logging.LogFactory.getLog(LogFactory.java:370)
05/06/24 09:16:02 at 
org.apache.axis.components.logger.LogFactory.getLog(LogFactory.java:37)
05/06/24 09:16:02 at 
org.apache.axis.transport.http.AxisHTTPSessionListener.clinit(AxisHTTPSessionListener.java:33)

05/06/24 09:16:02 ... 15 more
05/06/24 09:16:02 Caused by: java.lang.ExceptionInInitializerError
05/06/24 09:16:02 at org.apache.log4j.Logger.getLogger(Logger.java:85)
05/06/24 09:16:02 at 
org.apache.commons.logging.impl.Log4JLogger.getLogger(Log4JLogger.java:229)
05/06/24 09:16:02 at 
org.apache.commons.logging.impl.Log4JLogger.init(Log4JLogger.java:65)
05/06/24 09:16:02 at 
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
05/06/24 09:16:02 at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
05/06/24 09:16:02 at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
05/06/24 09:16:02 at 
java.lang.reflect.Constructor.newInstance(Constructor.java:274)
05/06/24 09:16:02 at 
org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:529)

05/06/24 09:16:02 ... 19 more
05/06/24 09:16:02 Caused by: java.lang.ClassCastException
05/06/24 09:16:02 at 
javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:29)
05/06/24 09:16:02 at 
org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:644)
05/06/24 09:16:02 at 
org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:616)
05/06/24 09:16:02 at 
org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:602)
05/06/24 09:16:02 at 
org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:460)
05/06/24 09:16:02 at 
org.apache.log4j.LogManager.clinit(LogManager.java:113)

05/06/24 09:16:02 ... 27 more

Thanks in advance

Alexandre


AW: Problem setting up Axis

2005-06-28 Thread Ferruh Zamangoer
The best way to set up axis is to copy axis-1_2/webapps/axis into your
tomcat \Apache Group\Tomcat 4.1\webapps folders.




-Ursprüngliche Nachricht-
Von: Ferruh Zamangoer [mailto:[EMAIL PROTECTED] 
Gesendet: Dienstag, 28. Juni 2005 08:52
An: axis-user@ws.apache.org
Betreff: AW: Problem setting up Axis

Hi Janet,

if you have downloaded the axis-1_2.zip binaries you can extract this file.
After you have extracted you have a folder structure like:

- axis-1_2
   - docs
   - lib
   - samples
   - webapps
   - xmls

Normally the wsdl4j.jar must be in lib directory, otherwise you can look at
axis-1_2\webapps\axis\WEB-INF\lib. The wsdl4j.jar is used in AXIS to
generate Java code from WSDL and to generate WSDL from Java.

Hope it helps.

Regards
Ferruh




-Ursprüngliche Nachricht-
Von: Miller, Janet [mailto:[EMAIL PROTECTED] 
Gesendet: Dienstag, 28. Juni 2005 01:05
An: axis-user@ws.apache.org
Betreff: RE: Problem setting up Axis

I am also missing a file called wsdl4j.jar which the Axis documentation
says is supposed to be in my CLASSPATH and AXISCLASSPATH.  I've
installed everything and don't have this file on my machine.  Where does
this file come from?  Could someone check to see if this file exists on
your machine?  It is supposed to be in the \webapps\axis\WEB-INF\lib
directory.

I can't get Axis to work.  The happyAxis page is displaying properly
though.

Thanks,

Jan



PLEASE unsubscribe me

2005-06-28 Thread CREMENESCU FLORIN

 Hi, 
 
 Could someone managing the list unsubscribe me ? The automatic unsubscribe
mecanism does not function for me ! At the week I'll be in holiday, and I
have to put an automatic answer to my mailbox : every message I receive from
the axis list will generate a new mail to the list. 
 
Thank you for your understanding. 

 Florin


 -Message d'origine-
 De:   CREMENESCU FLORIN [SMTP:[EMAIL PROTECTED]
 Date: lundi 27 juin 2005 09:42
 À:'axis-user@ws.apache.org'
 Objet:Please unsubscribe me
 
 
  Hi, 
 
  I'm trying to unsubscribe from the axis list, but I found this
 impossible.
 Could someone remove my address [EMAIL PROTECTED] from this list ?  
 Thank you, 
   Florin
 
  PS Here are my subscribe request and the unsubscribe answer from your
 list
 manager program (you can see that it's the same address) : 
 
 SUBSCRIBE MESSAGE : 
 
 Hi! This is the ezmlm program. I'm managing the
 axis-dev@ws.apache.org mailing list.
 
 Acknowledgment: I have added the address
 
[EMAIL PROTECTED]
 
 to the axis-dev mailing list.
 
 Welcome to [EMAIL PROTECTED]
 
 Please save this message so that you know the address you are
 subscribed under, in case you later want to unsubscribe or change your
 subscription address.
 
 To unsubscribe, send a message to:
 
 [EMAIL PROTECTED]
 
 
 --- Administrative commands for the axis-dev list ---
 
 I can handle administrative requests automatically. Please
 do not send them to the list address! Instead, send
 your message to the correct command address:
 
 To subscribe to the list, send a message to:
[EMAIL PROTECTED]
 
 To remove your address from the list, send a message to:
[EMAIL PROTECTED]
 
 Send mail to the following for info and FAQ for this list:
[EMAIL PROTECTED]
[EMAIL PROTECTED]
 
 To get messages 123 through 145 (a maximum of 100 per request), mail:
[EMAIL PROTECTED]
 
 To get an index with subject and author for messages 123-456 , mail:
[EMAIL PROTECTED]
 
 They are always returned as sets of 100, max 2000 per request,
 so you'll actually get 100-499.
 
 To receive all messages with the same subject as message 12345,
 send an empty message to:
[EMAIL PROTECTED]
 
 The messages do not really need to be empty, but I will ignore
 their content. Only the ADDRESS you send to is important.
 
 You can start a subscription for an alternate address,
 for example [EMAIL PROTECTED], just add a hyphen and your
 address (with '=' instead of '@') after the command word:
 [EMAIL PROTECTED]
 
 To stop subscription for this address, mail:
 [EMAIL PROTECTED]
 
 In both cases, I'll send a confirmation message to that address. When
 you receive it, simply reply to it to complete your subscription.
 
 If despite following these instructions, you do not get the
 desired results, please contact my owner at
 [EMAIL PROTECTED] Please be patient, my owner is a
 lot slower than I am ;-)
 
 --- Enclosed is a copy of the request I received.
 
 Return-Path: [EMAIL PROTECTED]
 Received: (qmail 7396 invoked by uid 99); 29 Mar 2005 15:42:23 -
 X-ASF-Spam-Status: No, hits=0.0 required=10.0
   tests=
 X-Spam-Check-By: apache.org
 Received-SPF: pass (hermes.apache.org: local policy)
 Received: from mailhost2.cdn.fr (HELO net191rms002.cdn.fr) (194.2.239.194)
   by apache.org (qpsmtpd/0.28) with ESMTP; Tue, 29 Mar 2005 07:42:21 -0800
 Received: from net188fls002.cdn.fr (unverified) by net191rms002.cdn.fr
  (Content Technologies SMTPRS 4.3.17) with ESMTP id
 [EMAIL PROTECTED] for
 [EMAIL PROTECTED]
 pa
 che.org;
  Tue, 29 Mar 2005 17:40:36 +0200
 Received: from sec014mes052.cdn (unverified) by net188fls002.cdn.fr 
 (Content Technologies SMTPRS 4.3.17) with ESMTP id 
 [EMAIL PROTECTED] for 
  
 [EMAIL PROTECTED]
 pa
 che.org
; Tue, 29 Mar 2005 17:42:18 +0200
 Received: by sec014mes052.cdn with Internet Mail Service (5.5.2657.72) id
   HPN5CKAM; Tue, 29 Mar 2005 17:42:20 +0200
 Message-ID: [EMAIL PROTECTED]
 From: CREMENESCU FLORIN [EMAIL PROTECTED]
 To:
 '[EMAIL PROTECTED]
 ap
 ache.org'
  
 [EMAIL PROTECTED]
 pa
 che.org
 Subject: RE: confirm subscribe to axis-dev@ws.apache.org
 Date: Tue, 29 Mar 2005 17:35:49 +0200
 MIME-Version: 1.0
 X-Mailer: Internet Mail Service (5.5.2657.72)
 Content-Type: text/plain; charset=iso-8859-1
 Content-Transfer-Encoding: quoted-printable
 X-Virus-Checked: Checked
 
 
 
  -Message d'origine-
  De: [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]
  Date:   mardi 29 mars 2005 17:42
  =C0:[EMAIL PROTECTED]
  Objet:  confirm subscribe to axis-dev@ws.apache.org
 =20
  Hi! This is the ezmlm program. I'm managing the
  axis-dev@ws.apache.org mailing list.
 =20
  To confirm that you would like
 =20
 [EMAIL PROTECTED]
 =20
  added to the axis-dev mailing list, please send
  an empty reply to this address:
 =20
  =20
 
 [EMAIL PROTECTED]
 .ap
  ache.org
 =20
  Usually, this happens when you just hit the reply button.
  If this does not work, simply copy the address and paste it into
  

Cannot find any provider supporting DESede/CBC/ISO10126Padding error

2005-06-28 Thread Mfenetre Mfenetre
Hello all,

I'm trying to use WSS4J to secure my web services. I'm trying to use
the digital signatures. My web services work fine and so far I've been
able to use the UsernameToken with WSS4J.

Now I want to sign a message (following the scenario Ping2), and I use
the file wsstest.properties :

org.apache.ws.security.crypto.provider=org.apache.ws.security.components.crypto.Merlin
org.apache.ws.security.crypto.merlin.keystore.type=jks
org.apache.ws.security.crypto.merlin.keystore.password=interop
org.apache.ws.security.crypto.merlin.file=interop/interop.jks

But when I run the example, I get the following error :

WSDoAllSender: Encryption: error during message
processingorg.apache.ws.security.WSSecurityException: An unsupported
signature or encryption algorithm was used; nested exception is:
org.apache.xml.security.encryption.XMLEncryptionException: Cannot
find any provider supporting DESede/CBC/ISO10126Padding

(full trace at the end of the message).
I don't understand why this error is about DES encryption, I'm using a RSA key !

Any help on this topic would be greatly appreciated.

Thank you in advance,
Regards,
Alexis.

-

WSDoAllSender: Encryption: error during message
processingorg.apache.ws.security.WSSecurityException: An unsupported
signature or encryption algorithm was used; nested exception is:
org.apache.xml.security.encryption.XMLEncryptionException: Cannot
find any provider supporting DESede/CBC/ISO10126Padding
Original Exception was java.security.NoSuchAlgorithmException: Cannot
find any provider supporting DESede/CBC/ISO10126Padding

org.apache.ws.axis.security.WSDoAllSender.performENCRAction(WSDoAllSender.java:455)
org.apache.ws.axis.security.WSDoAllSender.invoke(WSDoAllSender.java:316)

org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
org.apache.axis.client.AxisClient.invoke(AxisClient.java:127)
org.apache.axis.client.Call.invokeEngine(Call.java:2765)
org.apache.axis.client.Call.invoke(Call.java:2748)
org.apache.axis.client.Call.invoke(Call.java:2424)
org.apache.axis.client.Call.invoke(Call.java:2347)
org.apache.axis.client.Call.invoke(Call.java:1804)

pneuservice.PneuServiceSoapBindingStub.searchModeleCamion(PneuServiceSoapBindingStub.java:247)

pneuservice.PneuServiceProxy.searchModeleCamion(PneuServiceProxy.java:60)

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

org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java: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)


Re: Wss4j.jar

2005-06-28 Thread Mfenetre Mfenetre
This file is part of an example in wss4j, but I don't know where it is
in the repository. If you check out wss4j (see website how to do
this), you can find some keys in the repository in order to run a few
examples (ex : interop2.jks, this is a java keystore). In order to use
your own key, you have to edit the wsstest.properties (or mayble
crypto.properties and replace keys/x509.PFX.MSFT by the keystore you
want to use). Or you can create them by yourself using openssl.

Regards,
Alexis.

On 6/27/05, Dorner, Thomas [EMAIL PROTECTED] wrote:
 Hi,
 
 I get the following exception with a wss4j.jar downloaded at an tutuorial!
 -- Exception say:  Proxy file (keys/x509.PFX.MSFT) not found.[]
 How can I solve this problem?
 
 Thank you in advance
 Tomi
 
 java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
 Method)
at
 sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAcces
 sorImpl.java:39)
at
 sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstruc
 torAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
at
 org.apache.ws.security.components.crypto.CryptoFactory.loadClass(CryptoFacto
 ry.java:117)
at
 org.apache.ws.security.components.crypto.CryptoFactory.getInstance(CryptoFac
 tory.java:101)
at
 com.tsystems.epdm.pdmwebconnector.webService.handler.WSDoAllSender.loadEncry
 ptionCrypto(WSDoAllSender.java:658)
at
 com.tsystems.epdm.pdmwebconnector.webService.handler.WSDoAllSender.invoke(WS
 DoAllSender.java:296)
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.client.AxisClient.invoke(AxisClient.java:121)
at org.apache.axis.client.Call.invokeEngine(Call.java:2765)
at org.apache.axis.client.Call.invoke(Call.java:2748)
at org.apache.axis.client.Call.invoke(Call.java:2424)
at org.apache.axis.client.Call.invoke(Call.java:2347)
at org.apache.axis.client.Call.invoke(Call.java:1804)
at
 com.tsystems.epdm.pdmwebconnector.client.webservice.soapclient.UniversalStub
 .login(UniversalStub.java:221)
at
 com.tsystems.epdm.pdmwebconnector.client.servlet.Login_Servlet.doPost(Login_
 Servlet.java:140)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
 FilterChain.java:247)
at
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
 ain.java:193)
at
 org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja
 va:256)
at
 org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
 eNext(StandardPipeline.java:643)
at
 org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at
 org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
 org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja
 va:191)
at
 org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
 eNext(StandardPipeline.java:643)
at
 org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at
 org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
 org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415)
at
 org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180
 )
at
 org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
 eNext(StandardPipeline.java:643)
at
 org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.
 java:171)
at
 org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
 eNext(StandardPipeline.java:641)
at
 org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172
 )
at
 org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
 eNext(StandardPipeline.java:641)
at
 org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at
 org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
 org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java
 :174)
at
 org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
 eNext(StandardPipeline.java:643)
at
 org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at
 org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
 

Re: NTLM Authentication (again)

2005-06-28 Thread Martin Woodward
I'm pretty sure that that the Commons HTTPClient implementation (used
by CommonsHTTPSender) has an implementation of NTLM in 3.0-RC3.  If I
take out my credentials from the call then I get the following error
when talking via the proxy

No credentials available for NTLM any realm@mymachine:80

Which would suggest that it is the Commons HTTPClient code that
negotiating, not TCPMon.

I am not creating the HTTP connection directly.  I am using a
WSDL2Java generated stub which I have added a couple of lines to add
my credentials to the _call in the createCall method.  I have then
used the client-config.wsdd to override the default transport
implementaion to the Commons one (which has NTLM support)

Below if the contents of my client-config.msdd file...

?xml version=1.0 encoding=UTF-8?
deployment name=defaultClientConfig
 xmlns=http://xml.apache.org/axis/wsdd/;
 xmlns:java=http://xml.apache.org/axis/wsdd/providers/java;
  globalConfiguration
parameter name=disablePrettyXML value=true/
  /globalConfiguration
  transport name=http
pivot=java:org.apache.axis.transport.http.CommonsHTTPSender/
  !-- transport name=http
pivot=java:org.apache.axis.transport.http.HTTPSender/ --
  transport name=local
pivot=java:org.apache.axis.transport.local.LocalSender/
  transport name=java
pivot=java:org.apache.axis.transport.java.JavaSender/
/deployment

I think it is actually the
org.apache.axis.transport.http.CommonsHTTPSender class that creates
the URL connection - please let me know if I doing something daft or
have mis-understood your point.

Cheers,

Martin.


On 28/06/05, Evgeny Beskrovny [EMAIL PROTECTED] wrote:
 Hi,
 I think the reason it doesn't work for you is because in order to make it
 work you need to have a Sun implementation of HTTPUrlConnection on a
 client, while here as I understand you use HttpClient of Apache that might
 have no implementation of NTLM. When you connect to a proxy it internally
 uses Sun implementation of HTTPUrlConnection so it works.
 When you create a URL on your client you would better use it this way
 
 handler = new sun.net.www.protocol.http.Handler();
 urlToConnect= new URL (null, urlPath.toString(),handler);
 URLConnection connection = urlToConnect.openConnection();
 Try this and see if it works.
 Evgeny
 
 Martin Woodward
 martin.woodward@
 gmail.com To
   axis-user@ws.apache.org
 06/27/2005 08:30   cc
 PM
   Subject
   NTLM Authentication (again)
 Please respond to
 [EMAIL PROTECTED]
  he.org
 
 
 Hi,
 
 I'm trying to talk to a web service that requires NTLM authentication
 for my sins.  The good news is that it works, the bad news is that I
 have to proxy the request through a local instance of TCPmon to get it
 to work.  Does this sound familiar to anyone, I could very possibly be
 me doing something dumb...
 
 I am using axis-1_2_1, commons-httpclient-3.0-rc3, commons-codec-1.3
 on j2sdk1.4.2_08 running in Windows XP Pro SP2.
 
 As I say, everything works fine if I run up TCPMonitor on my machine
 and then include the following lines in my client...
 
 System.setProperty(http.proxyHost, localhost);
 System.setProperty(http.proxyPort, );
 
 I've allready edited my stub to add the username/password and added a
 client-config.wsdd to point to the CommonsHTTPSender.
 
 Below is the stack trace when I don't have the web service call proxied:-
 
 AxisFault
 faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
 faultSubcode:
 faultString: java.net.SocketException: Connection reset
 faultActor:
 faultNode:
 faultDetail:
 
 {http://xml.apache.org/axis/}stackTrace:java.net.SocketException:
 Connection reset
 at java.net.SocketInputStream.read(SocketInputStream.java:168)
 at
 java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
 at
 java.io.BufferedInputStream.read(BufferedInputStream.java:201)
 at
 org.apache.commons.httpclient.HttpParser.readRawLine(HttpParser.java:77)
 at
 org.apache.commons.httpclient.HttpParser.readLine(HttpParser.java:105)
 at
 org.apache.commons.httpclient.HttpConnection.readLine(HttpConnection.java:1110)
 
 at
 org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.readLine(MultiThreadedHttpConnectionManager.java:1391)
 
 at
 org.apache.commons.httpclient.HttpMethodBase.readStatusLine(HttpMethodBase.java:1832)
 
 at
 org.apache.commons.httpclient.HttpMethodBase.readResponse(HttpMethodBase.java:1592)
 
 at
 org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:995)
 
 at
 

Re: NTLM Authentication (again)

2005-06-28 Thread John Baker
JCifs and a Tomcat filter? :)

On Tue, Jun 28, 2005 at 11:30:44AM +0100, Martin Woodward wrote:
 I'm pretty sure that that the Commons HTTPClient implementation (used
 by CommonsHTTPSender) has an implementation of NTLM in 3.0-RC3.  If I
 take out my credentials from the call then I get the following error
 when talking via the proxy
 
 No credentials available for NTLM any realm@mymachine:80
 
 Which would suggest that it is the Commons HTTPClient code that
 negotiating, not TCPMon.
 
 I am not creating the HTTP connection directly.  I am using a
 WSDL2Java generated stub which I have added a couple of lines to add
 my credentials to the _call in the createCall method.  I have then
 used the client-config.wsdd to override the default transport
 implementaion to the Commons one (which has NTLM support)
 
 Below if the contents of my client-config.msdd file...
 
 ?xml version=1.0 encoding=UTF-8?
 deployment name=defaultClientConfig
  xmlns=http://xml.apache.org/axis/wsdd/;
  xmlns:java=http://xml.apache.org/axis/wsdd/providers/java;
   globalConfiguration
 parameter name=disablePrettyXML value=true/
   /globalConfiguration
   transport name=http
 pivot=java:org.apache.axis.transport.http.CommonsHTTPSender/
   !-- transport name=http
 pivot=java:org.apache.axis.transport.http.HTTPSender/ --
   transport name=local
 pivot=java:org.apache.axis.transport.local.LocalSender/
   transport name=java
 pivot=java:org.apache.axis.transport.java.JavaSender/
 /deployment
 
 I think it is actually the
 org.apache.axis.transport.http.CommonsHTTPSender class that creates
 the URL connection - please let me know if I doing something daft or
 have mis-understood your point.
 
 Cheers,
 
 Martin.
 
 
 On 28/06/05, Evgeny Beskrovny [EMAIL PROTECTED] wrote:
  Hi,
  I think the reason it doesn't work for you is because in order to make it
  work you need to have a Sun implementation of HTTPUrlConnection on a
  client, while here as I understand you use HttpClient of Apache that might
  have no implementation of NTLM. When you connect to a proxy it internally
  uses Sun implementation of HTTPUrlConnection so it works.
  When you create a URL on your client you would better use it this way
  
  handler = new sun.net.www.protocol.http.Handler();
  urlToConnect= new URL (null, urlPath.toString(),handler);
  URLConnection connection = urlToConnect.openConnection();
  Try this and see if it works.
  Evgeny
  
  Martin Woodward
  martin.woodward@
  gmail.com To
axis-user@ws.apache.org
  06/27/2005 08:30   cc
  PM
Subject
NTLM Authentication (again)
  Please respond to
  [EMAIL PROTECTED]
   he.org
  
  
  Hi,
  
  I'm trying to talk to a web service that requires NTLM authentication
  for my sins.  The good news is that it works, the bad news is that I
  have to proxy the request through a local instance of TCPmon to get it
  to work.  Does this sound familiar to anyone, I could very possibly be
  me doing something dumb...
  
  I am using axis-1_2_1, commons-httpclient-3.0-rc3, commons-codec-1.3
  on j2sdk1.4.2_08 running in Windows XP Pro SP2.
  
  As I say, everything works fine if I run up TCPMonitor on my machine
  and then include the following lines in my client...
  
  System.setProperty(http.proxyHost, localhost);
  System.setProperty(http.proxyPort, );
  
  I've allready edited my stub to add the username/password and added a
  client-config.wsdd to point to the CommonsHTTPSender.
  
  Below is the stack trace when I don't have the web service call proxied:-
  
  AxisFault
  faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
  faultSubcode:
  faultString: java.net.SocketException: Connection reset
  faultActor:
  faultNode:
  faultDetail:
  
  {http://xml.apache.org/axis/}stackTrace:java.net.SocketException:
  Connection reset
  at java.net.SocketInputStream.read(SocketInputStream.java:168)
  at
  java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
  at
  java.io.BufferedInputStream.read(BufferedInputStream.java:201)
  at
  org.apache.commons.httpclient.HttpParser.readRawLine(HttpParser.java:77)
  at
  org.apache.commons.httpclient.HttpParser.readLine(HttpParser.java:105)
  at
  org.apache.commons.httpclient.HttpConnection.readLine(HttpConnection.java:1110)
  
  at
  org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.readLine(MultiThreadedHttpConnectionManager.java:1391)
  
  at
  org.apache.commons.httpclient.HttpMethodBase.readStatusLine(HttpMethodBase.java:1832)
  
  at
  

Re: NTLM Authentication (again)

2005-06-28 Thread Evgeny Beskrovny
I suggest you to write the code using the classes of Apache that connect to
the NTLM server and see if it works. There is a big chance that it won't
work since as far as I remember they don't support different parameters
that can be set in NTLM for example usage of NTLM2 that server during the
NTLM handshake might prescribe client to do.
Evgeny


   
 Martin Woodward   
 martin.woodward@ 
 gmail.com To 
   axis-user@ws.apache.org 
 06/28/2005 01:30   cc 
 PM
   Subject 
   Re: NTLM Authentication (again) 
 Please respond to 
 [EMAIL PROTECTED] 
  he.org   
   
   
   




I'm pretty sure that that the Commons HTTPClient implementation (used
by CommonsHTTPSender) has an implementation of NTLM in 3.0-RC3.  If I
take out my credentials from the call then I get the following error
when talking via the proxy

No credentials available for NTLM any realm@mymachine:80

Which would suggest that it is the Commons HTTPClient code that
negotiating, not TCPMon.

I am not creating the HTTP connection directly.  I am using a
WSDL2Java generated stub which I have added a couple of lines to add
my credentials to the _call in the createCall method.  I have then
used the client-config.wsdd to override the default transport
implementaion to the Commons one (which has NTLM support)

Below if the contents of my client-config.msdd file...

?xml version=1.0 encoding=UTF-8?
deployment name=defaultClientConfig
 xmlns=http://xml.apache.org/axis/wsdd/;
 xmlns:java=http://xml.apache.org/axis/wsdd/providers/java;
  globalConfiguration
parameter name=disablePrettyXML value=true/
  /globalConfiguration
  transport name=http
pivot=java:org.apache.axis.transport.http.CommonsHTTPSender/
  !-- transport name=http
pivot=java:org.apache.axis.transport.http.HTTPSender/ --
  transport name=local
pivot=java:org.apache.axis.transport.local.LocalSender/
  transport name=java
pivot=java:org.apache.axis.transport.java.JavaSender/
/deployment

I think it is actually the
org.apache.axis.transport.http.CommonsHTTPSender class that creates
the URL connection - please let me know if I doing something daft or
have mis-understood your point.

Cheers,

Martin.


On 28/06/05, Evgeny Beskrovny [EMAIL PROTECTED] wrote:
 Hi,
 I think the reason it doesn't work for you is because in order to make it
 work you need to have a Sun implementation of HTTPUrlConnection on a
 client, while here as I understand you use HttpClient of Apache that
might
 have no implementation of NTLM. When you connect to a proxy it internally
 uses Sun implementation of HTTPUrlConnection so it works.
 When you create a URL on your client you would better use it this way

 handler = new sun.net.www.protocol.http.Handler();
 urlToConnect= new URL (null, urlPath.toString(),handler);
 URLConnection connection = urlToConnect.openConnection();
 Try this and see if it works.
 Evgeny

 Martin Woodward
 martin.woodward@
 gmail.com To
   axis-user@ws.apache.org
 06/27/2005 08:30   cc
 PM
   Subject
   NTLM Authentication (again)
 Please respond to
 [EMAIL PROTECTED]
  he.org


 Hi,

 I'm trying to talk to a web service that requires NTLM authentication
 for my sins.  The good news is that it works, the bad news is that I
 have to proxy the request through a local instance of TCPmon to get it
 to work.  Does this sound familiar to anyone, I could very possibly be
 me doing something dumb...

 I am using axis-1_2_1, commons-httpclient-3.0-rc3, commons-codec-1.3
 on j2sdk1.4.2_08 running in Windows XP Pro SP2.

 As I say, everything works fine if I run up TCPMonitor on my machine
 and then include the following lines in my client...

 System.setProperty(http.proxyHost, localhost);
 System.setProperty(http.proxyPort, );

 I've allready edited my stub to add the username/password 

Re: NoClassDefFoundError when creating service stub

2005-06-28 Thread Anne Thomas Manes
I suspect it's just a typo. 

Shouldn't new clientPackag.PortStub be new clientPackage.PortStub?

Anne

On 6/23/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
  
 I'm an Axis newby, so please pardon any obvious dumb mistakes I'm trying to
 find. 
  
 I'm trying to follow the example in the Axis User Guide for implementing the
 client side bindings.  I've created all the generated Java code from the
 service WSDL (using the Lavadora Eclipse plugin, but the code looks
 correct).  I'll generalize the names of the four interface class files as
 ServiceInterface, ServiceLocator, PortInterface, and PortStub.  This is all
 in one test project, so the client and server components are in different
 packages. 
  
 Using the User Guide example, I'm trying to execute the following code: 
  
 ServiceInterface myService = new ServiceLocator(); 
 PortInterface MyPort = myService.getServerName(); 
  
 The first line works fine.  The second line executes the portion of
 myService.getServerName() which creates the URL and than calls
 myService.getServerName(URL)  However, the line of code which essentially
 says: 
  
 clientPackage.PortStub _stub = new
 clientPackag.PortStub(portAddress, this); 
  
 This line of code generates a  java.lang.NoClassDefFoundError exception, and
 won't tell me what the class is that is not found, and blows up in code that
 I don't have the source for 
  
 If I create my own Call object and use it directly, the service works just
 fine, so the problem is not the client, the service, Tomcat, Axis, or any
 other external items.   
 I seem to have some sort of class definition (classpath?) error in creating
 the PortStub.  Anybody have any idea what this might be? 
  
 JFE.



Re: NoClassDefFoundError when creating service stub

2005-06-28 Thread Jack_Emmerichs

Whoops, yes, it's a typo, I was trying
to reduce long local names to understandable but short examples. I
think I've found the problem, but I think we're going to try using the
Web Tools package to drive the Axis environment for us from Eclipse. With
any luck, it will take care of several minor glitches we currently have.

Thanks for your time.

JFE.






Anne Thomas Manes [EMAIL PROTECTED]

06/28/2005 06:10 AM



Please respond to
axis-user@ws.apache.org





To
axis-user@ws.apache.org


cc



Subject
Re: NoClassDefFoundError when creating
service stub








I suspect it's just a typo. 

Shouldn't new clientPackag.PortStub be new clientPackage.PortStub?

Anne

On 6/23/05, [EMAIL PROTECTED] [EMAIL PROTECTED]
wrote:
 
 I'm an Axis newby, so please pardon any obvious dumb mistakes I'm
trying to
 find. 
 
 I'm trying to follow the example in the Axis User Guide for implementing
the
 client side bindings. I've created all the generated Java code
from the
 service WSDL (using the Lavadora Eclipse plugin, but the code looks
 correct). I'll generalize the names of the four interface class
files as
 ServiceInterface, ServiceLocator, PortInterface, and PortStub. This
is all
 in one test project, so the client and server components are in different
 packages. 
 
 Using the User Guide example, I'm trying to execute the following
code: 
 
 ServiceInterface myService = new ServiceLocator();

 PortInterface MyPort = myService.getServerName();

 
 The first line works fine. The second line executes the portion
of
 myService.getServerName() which creates the URL and than calls
 myService.getServerName(URL) However, the line of code which
essentially
 says: 
 
 clientPackage.PortStub _stub = new
 clientPackage.PortStub(portAddress, this); 
 
 This line of code generates a java.lang.NoClassDefFoundError
exception, and
 won't tell me what the class is that is not found, and blows up in
code that
 I don't have the source for 
 
 If I create my own Call object and use it directly, the service works
just
 fine, so the problem is not the client, the service, Tomcat, Axis,
or any
 other external items.  
 I seem to have some sort of class definition (classpath?) error in
creating
 the PortStub. Anybody have any idea what this might be? 
 
 JFE.




Re: REST again

2005-06-28 Thread Anne Thomas Manes
REST works on the assumption that your applications are working
directly with the XML and not attempting to map Java objects to XML.
If your assignment is to provide the same service in REST, then you
should in fact recreate all the functionality, but this time using DOM
in your application rather than mapping everything to objects.

Anne

On 6/22/05, Richard Wallis [EMAIL PROTECTED] wrote:
 Following the 'Start with the WSDL!' principle of web service
 development, I have produced a successful service which works in both
 Axis  .net, greatly helped by the classes produced by wsdl2java.
 
 So far so good.  Now I have a requirement to provide the same service
 via REST.  Being lazy I don't want to recreate all the functionality so
 intend to directly call the service method in the auto-generated
 xxSoapBindingImpl class.  I can easily create the correct Object to pass
 as a parameter.
 
 The problem I next have is to be able to create a response XML Document
 from the Object returned from the method.  Axis must do this when it is
 creating the response SOAP Body.
 
 Does anyone know how I can easily access this functionality.
 
 Richard.
 
 
 Register your interest now
 Insight 2005 : 15th  16th November
 Register your interest now http://www.talis.com/events
 
 
 
 Any views or personal opinions expressed within this email may not be those 
 of Talis Information Ltd. The content of this email message and any files 
 that may be attached are confidential, and for the usage of the intended 
 recipient only. If you are not the intended recipient, then please return 
 this message to the sender and delete it. Any use of this e-mail by an 
 unauthorised recipient is prohibited.



Help needed for TCPMonitor

2005-06-28 Thread Dipty Maybhate








Hi Everyone,



I am trying to view the SOAP request and response using TCPmonitor.
I invoke it using the command line option and give the host address and port mentioned
in the WSDL soap:address location field which is enclosed in the port
tag. When I inovoke this utility it just shows waiting for connection and
nothing happens. Could anyone please help me? Are there some other settings or
am I giving the wrong parameters?

Is there some other way in which I can view the request and
the response?



Thanks a lot!

Dipty



Dipty Maybhate

Austin, TX 78759










Re: Help needed for TCPMonitor

2005-06-28 Thread Jeff



Hi Dipty,

TCPmonitor sits in between a web service client and 
the web service to which the client is intended to connect.

Typically, TCPmonitor is configured (i) to listen 
on a previously unused port and (ii) to forwardclient requeststo the 
web service and web service responses back to the client. It doesn't matter on 
which machine(s) each of the three components is installed, provided 
thatsettings correctly reflect theconfiguration.

One simple scenario would leave the web service 
untouched,would have TCPmonitor calling into the web service as though it 
were the client while listening for connections from the real client and would 
have the client reconfigured to call into TCPmonitor.

Suppose that a web service is installed at 
10.0.0.1:8080. Ordinarily, the client would be configured to call into 
10.0.0.1:8080. To setup TCPmonitor on machine 10.0.0.2, choose an unused port to 
listen on, suppose its , then configure TCPmonitor to connect to 
10.0.0.1:8080 and configure the client to connect to 10.0.0.2:.


Jeff




- Original Message - 

  From: 
  Dipty Maybhate 
  To: axis-user@ws.apache.org 
  Sent: Tuesday, June 28, 2005 11:45 
  AM
  Subject: Help needed for TCPMonitor
  
  
  Hi Everyone,
  
  I am trying to view the SOAP 
  request and response using TCPmonitor. I invoke it using the command line 
  option and give the host address and port mentioned in the WSDL 
  soap:address location field which is enclosed in the port tag. 
  When I inovoke this utility it just shows waiting for connection and nothing 
  happens. Could anyone please help me? Are there some other settings or am I 
  giving the wrong parameters?
  Is there some other way in which I 
  can view the request and the response?
  
  Thanks a lot!
  Dipty
  
  Dipty Maybhate
  Austin, 
  TX 78759
  


Re: NTLM Authentication (again)

2005-06-28 Thread Martin Woodward
Yeah, just been sniffing around this afternoon and switched on all the
logging in IIS.  Still not helping me figure it out yet.  When talking
direct using the commons classes or going via a proxy the sequence of
events is

 POST request
 401
 POST request with some NTLM http header
 401
 POST request with bigger NTLM http header
 100 (which is ignored and a bit wierd)
 200 OK, followed by message.

When going direct using the CommonsHTTPSender I get...

 POST request
 401

I had been thinking that the strange 100 return message could have
been throwing things off, but it doesn't look that way now as it seems
to fall over when reading the first 401 error (it doesn't even read
the return code because the socket has been unexpectedly closed).  I
have also tried forcing authentication in the HttpClient paramaters
(thereby avoiding the 401 error) but that doesn't seem to work either,
the first request still does not have the NTLM header so you still get
the 401...

I'm going to carry on debugging through see if I can figure out the
problem.  If anyone has any other suggestions then let me know !!

Thanks,

Martin.

On 28/06/05, Evgeny Beskrovny [EMAIL PROTECTED] wrote:
 I would suggest you to use Ethereal sniffer to catch the difference between
 using just HttpClient and CommonHttpSender. It may give you a clue of
 what's going on.
 Evgeny
 
 Martin Woodward
 martin.woodward@
 gmail.com To
   axis-user@ws.apache.org
 06/28/2005 05:05   cc
 PM
   Subject
   Re: NTLM Authentication (again)
 Please respond to
 [EMAIL PROTECTED]
  he.org
 
 The latest version (3.0 RC3) of the Commons HttpClient works just fine
 with NTLM.  Which suggests to me that something is going funny in the
 org.apache.axis.transport.http.CommonsHTTPSender class.  I'll dig
 around in the CommonsHTTPSender class, but I was wondering if anyone
 had come across this before or actually got NTLM working...
 
 Below is the code I used that just used the Commons HTTPClient class
 to get an NTLM protected message (changed slightly to protect the
 innocent).  I tried it against the same web service method that my
 WDSL2Java generated call eventually winds up calling...
 
 -
 
 package com.mrwpro.vsts.play;
 
 import java.io.IOException;
 
 import org.apache.commons.httpclient.Credentials;
 import org.apache.commons.httpclient.HttpClient;
 import org.apache.commons.httpclient.HttpException;
 import org.apache.commons.httpclient.HttpMethodBase;
 import org.apache.commons.httpclient.NTCredentials;
 import org.apache.commons.httpclient.auth.AuthScope;
 import org.apache.commons.httpclient.methods.GetMethod;
 
 /**
 * Get a NTLM secured page.
 * @author martinwoodward
 */
 public class NTLMHttpTest {
 
  public static void main(String[] args) {
 
HttpClient httpClient = new HttpClient();
Credentials credentials =  new NTCredentials(username,
 password, remoteMachine, MY_DOMAIN);
httpClient.getState().setCredentials(AuthScope.ANY,credentials);
HttpMethodBase method = new
 GetMethod(http://remoteMachine/WebService/MyService.asmx/WhoAmI;);
 
try {
  int returnCode = httpClient.executeMethod(method);
  String response = method.getResponseBodyAsString();
  System.out.println(Response:  + response);
} catch (HttpException e) {
  e.printStackTrace();
} catch (IOException e) {
  e.printStackTrace();
}
 
  }
 }
 
 -
 
 Thanks,
 
 Martin.
 
 On 28/06/05, Evgeny Beskrovny [EMAIL PROTECTED] wrote:
  I suggest you to write the code using the classes of Apache that connect
 to
  the NTLM server and see if it works. There is a big chance that it won't
  work since as far as I remember they don't support different parameters
  that can be set in NTLM for example usage of NTLM2 that server during the
  NTLM handshake might prescribe client to do.
  Evgeny
 
  Martin Woodward
  martin.woodward@
  gmail.com To
axis-user@ws.apache.org
  06/28/2005 01:30   cc
  PM
Subject
Re: NTLM Authentication (again)
  Please respond to
  [EMAIL PROTECTED]
   he.org
 
  I'm pretty sure that that the Commons HTTPClient implementation (used
  by CommonsHTTPSender) has an implementation of NTLM in 3.0-RC3.  If I
  take out my credentials from the call then I get the following error
  when talking via the proxy
 
  No credentials available for NTLM any realm@mymachine:80
 
  Which would 

wsdl2java and java.util.Set

2005-06-28 Thread Nikita Tovstoles
I'm using wsdl2java to generate client-side ws stubs using JDK 1.5.  One 
of my javabeans contains java.util.Set property (needed for Hibernate). 
The generated binding stub class contains the following related code:


qName = new 
javax.xml.namespace.QName(http://java.sun.com/jax-rpc-ri/internal;, set);

   cachedSerQNames.add(qName);
   cls = com.sun.java.jax_rpc_ri.internal.Set.class;
   cachedSerClasses.add(cls);
   cachedSerFactories.add(beansf);
   cachedDeserFactories.add(beandf);

Problem is, com.sun.java.jax_rpc_ri.internal.* is nowhere to be found. 
Where can I find that package?
I read JAX-RPC documentation, and it states that java.util.Set is a 
supported type. Why the need for this cls at all?


thanks,
-nikita


AW: wsdl2java and java.util.Set

2005-06-28 Thread Ferruh Zamangoer
It seems to be a lib from SUN? I'am not sure but take a look at the API
Package org.apache.axis.encoding.ser. There you can see which serializers
for the collection classes are supported. I had not see a se-/deserializer
for set. Supported are HashMap, Vector... 

AXIS only do not need any se-/deserialzer if it's a simple java base type:
String, int , boolean .. If you are using some Collections classes you
have to define how AXIS must map the from Java==XML and XML==Java.

Hope it helps.
Ferruh


-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Gesendet: Dienstag, 28. Juni 2005 22:41
An: axis-user@ws.apache.org
Betreff: wsdl2java and java.util.Set

I'm using wsdl2java to generate client-side ws stubs using JDK 1.5.  One 
of my javabeans contains java.util.Set property (needed for Hibernate). 
The generated binding stub class contains the following related code:

qName = new 
javax.xml.namespace.QName(http://java.sun.com/jax-rpc-ri/internal;, set);
cachedSerQNames.add(qName);
cls = com.sun.java.jax_rpc_ri.internal.Set.class;
cachedSerClasses.add(cls);
cachedSerFactories.add(beansf);
cachedDeserFactories.add(beandf);

Problem is, com.sun.java.jax_rpc_ri.internal.* is nowhere to be found. 
Where can I find that package?
I read JAX-RPC documentation, and it states that java.util.Set is a 
supported type. Why the need for this cls at all?

thanks,
-nikita



Re: Client insists on sending xsi type

2005-06-28 Thread Anne Thomas Manes
Perhaps the type isn't defined in the WSDL/Schema, therefore Axis must
specify the type.
Supply the WSDL and I'll take a look.

On 6/28/05, Jim Cross [EMAIL PROTECTED] wrote:
  
 
 I'm assessing a server from the client side. I'm not sure what the server is
 written with. I've tried this with 1.1, 1.2, and 1.2.1. 
 
 The generated proxies have this statement before the service request. 
 

 _call.setProperty(org.apache.axis.client.Call.SEND_TYPE_ATTR,
 Boolean.FALSE); 
 
 I can also confirm that 
 
 MessageContext property name=sendXsiTypes value=false 
 
 Nevertheless, with a particular string array, the client insists on
 generating 
 
 xsi:type=xsd:string on the element 
 
 Removing the xsi:type and sending the SOAP XML via a raw post to the server
 works, so it is definite that this is problem. 
 
 As far as I tell from some limited debugging, the code gets deep into its
 serialization and compares the xmlType with an actualType (not sure where or
 how this is created or what purpose it serves). If these are different, it
 seems to generate the xsi:type no matter what the property setting is. 
 
 Any idea how to work around this? 



Re: URI for basic java types

2005-06-28 Thread Nikita Tovstoles

Anne,

Thanks for the explanation. Where can I get this fix (I'm already using 
latest stable axis distro 1.2.1)?


thanks,
-nikita

Anne Thomas Manes wrote:


It's not newer or older URIs -- one refers to xsd:string, the other
refers to soapenc:string. They are different types (soapenc:string is
nillable; xsd:string isn't nillable unless you specifically state that
it is). Per the SOAP spec, RPC/encoded messages should use
soapenc:string, but the interpretation of the spec is less than
perfect. Most systems use xsd:string instead. In this case, Sun
JAX-RPC is expecting xsd:string, but Axis is sending a soapenc:string.

There's a fix for Axis to make it use xsd:string instead. 


Anne

On 6/28/05, Nikita Tovstoles [EMAIL PROTECTED] wrote:
 


I'm getting the following error while executing a wsdl2java-produced
client against a web service with WSDL produced by wscompile (with
netbeans 4.1):

JAXRPCTIE01: caught exception while handling request: deserialization
error: unexpected element type:
expected={http://www.w3.org/2001/XMLSchema}string,
actual={http://schemas.xmlsoap.org/soap/encoding/}string

wscompile-produced WSDL seems to use URI
http://schemas.xmlsoap.org/soap/encoding/  for definition of common
types (int, string etc), while wsdl2java seems to prefer
http://www.w3.org/2001/XMLSchema. Should I somehow wsdl2java to use the
earlier URI? In general, is it a bad idea to generate service WSDL with
wscompile and consume with axis?

thanks
-nikita




   






Re: WSDL2Java problem with simple WSDL

2005-06-28 Thread Anne Thomas Manes
I suggest you file a bug.

Anne

On 6/27/05, Antonio Ruiz Martínez [EMAIL PROTECTED] wrote:
  Hello!
  
  Anne Thomas Manes wrote:
  
  Antonio,
 
 You're not the first person to ask exactly this question. I don't see
 what is unusual about the D-Sig schema that causes Axis to barf.
 
  
  Thanks for your answer.
  
  Would you please try to embed the D-Sig schema inside your WSDL and
 try it again?
  
  Yes I have tried but it doesn't work either with the 1.2.1.
  
  In the wsdl, I have tried both s:import
 namespace=http://www.w3.org/2000/09/xmldsig#/ and
 s:import namespace=http://www.w3.org/2000/09/xmldsig#;
 schemaLocation=http://ea.carm.es/schemas/funcionales/efirma/xmldsig-core-schema.xsd/.
 The result is the different.
  
  - With s:import
 namespace=http://www.w3.org/2000/09/xmldsig#;
 schemaLocation=http://ea.carm.es/schemas/funcionales/efirma/xmldsig-core-schema.xsd/
 the result is:
  C:\Archivos de programa\Apache Software Foundation\Tomcat
 5.5\axis-1_2_1\libjava org.apache.axis.wsdl.WSDL2Java -W -T1.1
 --server-side --skeletonDeploy true
  -t -p signservicerpc simple2.wsdl
  {http://www.w3.org/2000/09/xmldsig#}CryptoBinary already
 exists
  {http://www.w3.org/2000/09/xmldsig#}Signature already
 exists
  {http://www.w3.org/2000/09/xmldsig#}SignatureType already
 exists
  {http://www.w3.org/2000/09/xmldsig#}SignatureValue already
 exists
  {http://www.w3.org/2000/09/xmldsig#}SignatureValueType
 already exists
  {http://www.w3.org/2000/09/xmldsig#}ReferenceType already
 exists
  {http://www.w3.org/2000/09/xmldsig#}Reference already
 exists
  {http://www.w3.org/2000/09/xmldsig#}TransformType already
 exists
  {http://www.w3.org/2000/09/xmldsig#}Transform already
 exists
  {http://www.w3.org/2000/09/xmldsig#}TransformsType already
 exists
  {http://www.w3.org/2000/09/xmldsig#}Transforms already
 exists
  {http://www.w3.org/2000/09/xmldsig#}SignedInfo already
 exists
  {http://www.w3.org/2000/09/xmldsig#}SignedInfoType already
 exists
  {http://www.w3.org/2000/09/xmldsig#}CanonicalizationMethod
 already exists
 {http://www.w3.org/2000/09/xmldsig#}CanonicalizationMethodType
 already exists
  {http://www.w3.org/2000/09/xmldsig#}SignatureMethod
 already exists
  {http://www.w3.org/2000/09/xmldsig#}SignatureMethodType
 already exists
  {http://www.w3.org/2000/09/xmldsig#}DigestMethod already
 exists
  {http://www.w3.org/2000/09/xmldsig#}DigestMethodType
 already exists
  {http://www.w3.org/2000/09/xmldsig#}DigestValue already
 exists
  {http://www.w3.org/2000/09/xmldsig#}DigestValueType
 already exists
  {http://www.w3.org/2000/09/xmldsig#}KeyInfo already exists
  {http://www.w3.org/2000/09/xmldsig#}KeyInfoType already
 exists
  {http://www.w3.org/2000/09/xmldsig#}KeyName already exists
  {http://www.w3.org/2000/09/xmldsig#}MgmtData already
 exists
  {http://www.w3.org/2000/09/xmldsig#}KeyValue already
 exists
  {http://www.w3.org/2000/09/xmldsig#}KeyValueType already
 exists
  {http://www.w3.org/2000/09/xmldsig#}RetrievalMethod
 already exists
  {http://www.w3.org/2000/09/xmldsig#}RetrievalMethodType
 already exists
  {http://www.w3.org/2000/09/xmldsig#}X509Data already
 exists
  {http://www.w3.org/2000/09/xmldsig#}X509DataType already
 exists
  {http://www.w3.org/2000/09/xmldsig#}X509IssuerSerialType
 already exists
  {http://www.w3.org/2000/09/xmldsig#}PGPData already exists
  {http://www.w3.org/2000/09/xmldsig#}PGPDataType already
 exists
  {http://www.w3.org/2000/09/xmldsig#}SPKIData already
 exists
  {http://www.w3.org/2000/09/xmldsig#}SPKIDataType already
 exists
  {http://www.w3.org/2000/09/xmldsig#}Object already exists
  {http://www.w3.org/2000/09/xmldsig#}ObjectType already
 exists
  {http://www.w3.org/2000/09/xmldsig#}Manifest already
 exists
  {http://www.w3.org/2000/09/xmldsig#}ManifestType already
 exists
  {http://www.w3.org/2000/09/xmldsig#}SignaturePropertyType
 already exists
  {http://www.w3.org/2000/09/xmldsig#}SignatureProperty
 already exists
  {http://www.w3.org/2000/09/xmldsig#}SignatureProperties
 already exists
 {http://www.w3.org/2000/09/xmldsig#}SignaturePropertiesType
 already exists
  {http://www.w3.org/2000/09/xmldsig#}HMACOutputLengthType
 already exists
  {http://www.w3.org/2000/09/xmldsig#}DSAKeyValue already
 exists
  {http://www.w3.org/2000/09/xmldsig#}DSAKeyValueType
 already exists
  {http://www.w3.org/2000/09/xmldsig#}RSAKeyValue already
 exists
  {http://www.w3.org/2000/09/xmldsig#}RSAKeyValueType
 already exists
  java.io.IOException: Type
 {http://www.w3.org/2000/09/xmldsig#}Reference is referenced
 but not defined.
  at
 org.apache.axis.wsdl.symbolTable.SymbolTable.checkForUndefined(SymbolTable.java:665)
  at
 org.apache.axis.wsdl.symbolTable.SymbolTable.add(SymbolTable.java:545)
  at
 org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:518)
  at
 org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:495)
  at
 org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:361)