Re: Axis SOAP issue

hello vladimir,

it works now as expected.
thanx

gabriel

______________________
Mag. Gabriel Gruber
Senior Consultant
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Workflow EDV GmbH, Dannebergplatz 6/23, A-1030 Wien
phone: ++43 - 1 - 7188842 22
fax: ++43 - 1 - 7188842 30
mobile: ++43 - 676 - 3939435
mailto:[email protected]
http://www.workflow.at



Vladimir Puskas <[email protected]> 
13.07.2005 15:52
Please respond to
[email protected]


To
[email protected]
cc

Subject
Re: [shark] Axis SOAP issue






Hello Gabriel

it's my fault: service was down.
Does it work now?

regards
-- 
Vlada


you wrote:
> I tried to contact the public WFXML Service at 
> http://vajat.prozone.co.yu:8080/axis/services/wfxmlRegistryBinding via 
> JaWe 1.4.2 but got the error message "".
> 
> Problems while getting definition list for registry 
> http://vajat.prozone.co.yu:8080/axis/services/wfxmlRegistryBinding !
> 
> 
> 
> any advice?
> 
> thanx
> 
> Gabriel Gruber
> 
> 
> 
> 
> 
> "Bastiaan de Rijber" <[email protected]> 
> 09.07.2005 10:22
> Please respond to
> [email protected]
> 
> 
> To
> <[email protected]>
> cc
> 
> Subject
> Re: [shark] Axis SOAP issue
> 
> 
> 
> 
> 
> 
> I'm sorry Vladimir,
> 
> but to have a SOAP service only so you can connect to Shark via YaWe 
kinda 
> 
> defeats the purpose of having a SOAP service, right?
> 
> What most of us are trying to do is step outside Shark's "box" and use 
it 
> for example in C# without having to resort to the CORBA solution (which 
is 
> 
> not something that works out of the box in a .Net enviroment).
> 
> Bastiaan de Rijber
> 
> 
> ----- Original Message ----- 
> From: "Vladimir Puskas" <[email protected]>
> To: <[email protected]>
> Sent: Wednesday, July 06, 2005 9:43 AM
> Subject: Re: [shark] Axis SOAP issue
> 
> 
> 
>>Hello Luke
>>
>>you wrote:
>>
>>>I have tried asapInstanceBinding and got the same error using 
>>>getProperties
>>>and subscribe methods. For some reason the AdminService tag is not 
>>>correct
>>>and it requires a tag of deployment?
>>
>>Have you tried to connect to this engine with JaWE?
>>Public Shark Wf-XML demo-engine is up and running. It's built from
>>current CVS code. Can you, please, try connecting with JaWE to
>>http://vajat.prozone.co.yu:8080/axis/services/wfxmlRegistryBinding ?
>>
>>tia
>>-- 
>>Vlada
>>
>>
>>
>>>Any light on this matter would be good.
>>>
>>>Kindest Regards
>>>
>>>Luke Trevorrow
>>>-----Original Message-----
>>>From: Vladimir Puskas [mailto:[email protected]]
>>>Sent: 05 July 2005 13:47
>>>To: [email protected]
>>>Subject: Re: [shark] Axis SOAP issue
>>>
>>>Hello Luke
>>>
>>>you wrote:
>>>
>>>
>>>>Hello,
>>>>
>>>>I am having issues with the Axis SOAP implementation. Using tcptrace 
> 
> from
> 
>>>>pocketsoap.com you can see I am passing in the following message:
>>>>
>>>>POST /axis/services/AdminService/services/Version HTTP/1.0
>>>>User-Agent: Mozilla/4.0 (compatible; Cache;)
>>>>Connection: Close
>>>>Host: laptop0074:8080
>>>>SOAPAction:
>>>>Content-Length: 406
>>>>Content-Type: text/xml; charset=UTF-8
>>>>
>>>><?xml version="1.0" encoding="UTF-8" ?>
>>>><SOAP-ENV:Envelope
>>>>xmlns:SOAP-ENV='http://schemas.xmlsoap.org/soap/envelope/'
>>>>xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
>>>>xmlns:s='http://www.w3.org/2001/XMLSchema'
>>>>xmlns:types='http://xml.apache.org/axis/wsdd/'>
>>>> <SOAP-ENV:Body>
>>>>
> 
<types:AdminService><AdminService>getVersion</AdminService></types:AdminServ
> 
>>>>ice>  </SOAP-ENV:Body>
>>>></SOAP-ENV:Envelope>
>>>>
>>>>And getting the following error:
>>>>
>>>>HTTP/1.0 500 Internal server error
>>>>Set-Cookie: 2
>>>>Set-Cookie2: 2
>>>>Content-Type: text/xml; charset=utf-8
>>>>
>>>><soapenv:Envelope
>>>
>>>xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
>>>
>>>
>>>>xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>>>>
>>>
>>>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance
> 
> "><soapenv:Body><soapenv
> 
>>>
> 
:Fault><faultcode>soapenv:Server.userException</faultcode><faultstring>org.a
> 
>>>>pache.axis.deployment.wsdd.WSDDException: Invalid WSDD element
>>>>'AdminService' (wanted 'deployment')
>>>>
>>>>org.apache.axis.deployment.wsdd.WSDDException: Invalid WSDD element
>>>>'AdminService' (wanted 'deployment')
>>>>           at
>>>>
>>>
>>>
> 
org.apache.axis.deployment.wsdd.WSDDElement.validateCandidateElement(WSDDEle
> 
>>>>ment.java:74)
>>>>           at
>>>>
>>>
>>>
> 
org.apache.axis.deployment.wsdd.WSDDElement.&lt;init&gt;(WSDDElement.java:54
> 
>>>>)
>>>>           at
>>>>
>>>
>>>
> 
org.apache.axis.deployment.wsdd.WSDDDeployment.&lt;init&gt;(WSDDDeployment.j
> 
>>>>ava:183)
>>>>           at
>>>>
>>>
>>>
> 
org.apache.axis.deployment.wsdd.WSDDDocument.&lt;init&gt;(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)
>>>>           at sun.reflect.NativeMethodAccessorImpl.invoke0(Native 
>>>>Method)
>>>>           at
>>>>
>>>
>>>
> 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
> 
>>>>)
>>>>           at
>>>>
>>>
>>>
> 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
> 
>>>>.java:25)
>>>>           at java.lang.reflect.Method.invoke(Method.java:324)
>>>>           at
>>>>
>>>
>>>
> 
org.apache.axis.providers.java.MsgProvider.processMessage(MsgProvider.java:1
> 
>>>>26)
>>>>           at
>>>>org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:319)
>>>>           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.handlers.soap.SOAPService.invoke(SOAPService.java:450)
>>>>           at
>>>
>>>org.apache.axis.server.AxisServer.invoke(AxisServer.java:285)
>>>
>>>
>>>>           at
>>>>
>>>
>>>
> 
org.apache.axis.transport.http.SimpleAxisWorker.execute(SimpleAxisWorker.jav
> 
>>>>a:428)
>>>>           at
>>>>
>>>
>>>
> 
org.apache.axis.transport.http.SimpleAxisWorker.run(SimpleAxisWorker.java:15
> 
>>>>5)
>>>>           at
>>>>
>>>
>>>
> 
org.apache.axis.transport.http.SimpleAxisServer.run(SimpleAxisServer.java:24
> 
>>>>5)
>>>>           at
>>>>
>>>
>>>
> 
org.apache.axis.transport.http.SimpleAxisServer.start(SimpleAxisServer.java:
> 
>>>>296)
>>>>           at
>>>>
>>>
>>>
> 
org.apache.axis.transport.http.SimpleAxisServer.start(SimpleAxisServer.java:
> 
>>>>304)
>>>>           at
>>>>
>>>
>>>
> 
org.apache.axis.transport.http.SimpleAxisServer.main(SimpleAxisServer.java:3
> 
>>>>85)
>>>>           at sun.reflect.NativeMethodAccessorImpl.invoke0(Native 
>>>>Method)
>>>>           at
>>>>
>>>
>>>
> 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
> 
>>>>)
>>>>           at
>>>>
>>>
>>>
> 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
> 
>>>>.java:25)
>>>>           at java.lang.reflect.Method.invoke(Method.java:324)
>>>>           at
>>>>org.enhydra.shark.wfxml.SharkServiceImpl.main(SharkServiceImpl.java:84)
>>>>           at sun.reflect.NativeMethodAccessorImpl.invoke0(Native 
>>>>Method)
>>>>           at
>>>>
>>>
>>>
> 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
> 
>>>>)
>>>>           at
>>>>
>>>
>>>
> 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
> 
>>>>.java:25)
>>>>           at java.lang.reflect.Method.invoke(Method.java:324)
>>>>           at
>>>>org.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java:136)
>>>>           at java.lang.Thread.run(Thread.java:534)
>>>></faultstring><detail><ns1:stackTrace
>>>>
>>>
>>>xmlns:ns1="http://xml.apache.org/axis/
> 
> ">org.apache.axis.deployment.wsdd.WSDD
> 
>>>>Exception: Invalid WSDD element 'AdminService' (wanted 'deployment')
>>>>...
>>>
>>>
>>>We saw some problems with Axis, yet choose to ignore them, because they
>>>didn't really interfere with our services (registry, factory, instance
>>>and observer ;-) and Wf-XML interoperability with other vendors.
>>>Do you have same or similar problems with them too?
>>>
>>>You may already noticed that Shark follows >>Omnia mea mecum porto.<<
>>>philosophy. SimpleAxisServer fitted in nicely not enlarging the lot, 
> 
> but
> 
>>>beware - its docs says: "This is a simple implementation of an HTTP
>>>server for processing SOAP requests via Apache's xml-axis. This is not
>>>intended for production use. Its intended uses are for demos, 
> 
> debugging,
> 
>>>and performance profiling."
>>>
>>>Then again, we're still using Axis1.2RC2 while v1.2.1 is available...


--
You receive this message as a subscriber of the [email protected] 
mailing list.
To unsubscribe: mailto:[email protected]
For general help: mailto:[email protected]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

--
You receive this message as a subscriber of the [email protected] mailing list.
To unsubscribe: mailto:[email protected]
For general help: mailto:[email protected]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws