-
1. Re: Problem using complex type in bpel. WS invocation failed java.lang.IllegalArgumentException: Cannot obtain wsdl service error
christy Jul 6, 2010 9:18 AM (in response to christy)Something strange. I created another process that invokes another web-service and works with complex type and everything works fine. Is this a bug of tools? I found the jira with the same problem: https://jira.jboss.org/browse/RIFTSAW-126. But I did not understand is this the problem and did it solved?
Thank you!
-
2. Re: Problem using complex type in bpel. WS invocation failed java.lang.IllegalArgumentException: Cannot obtain wsdl service error
jeff.yuchang Jul 6, 2010 9:21 AM (in response to christy)Hi Christy,
Could you tell me which RiftSaw version did you use, better to let me know the JBoss AS and JBoss ws version as well.
I've tested with current 2.1.0-SNAPSHOT version, with soap ui client testing, it works ok. If you are not using 2.1.0.CR2, could you try to test against this version. (http://jboss.org/riftsaw/downloads.html)
Below is the request and response that I get, let me know if I am doing something wrong below.
request:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:orgs="http://projects/ws/orgs">
<soapenv:Header/>
<soapenv:Body>
<orgs:MainProcessRequest>
<orgs:input>1</orgs:input>
</orgs:MainProcessRequest>
</soapenv:Body>
</soapenv:Envelope>response:
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header/>
<env:Body>
<getOrgDetailsResponse xmlns="http://orgs.ws.esimo/">
<return xmlns="">
<addressId>1</addressId>
<countries>Отечественная страна</countries>
<country>Россия</country>
<countryId>149</countryId>
<dept>Россудостроение</dept>
<deptId>1195</deptId>
<org1></org1>
<org2>АКИН</org2>
<org3>ФГУП</org3>
<orgBirthday>1953-01-01</orgBirthday>
<orgDeathdate/>
<orgId>1</orgId>
<orgId2>1</orgId2>
<orgId3>1</orgId3>
<orgNameEng>N.N.Andreyev Acoustics Institute RosSydoStroenie</orgNameEng>
<orgNameRus>Акустический институт имени академика Н.Н.Андреева</orgNameRus>
<orgOccupation>Основные задачи:
- акустика океана;
- шумы и вибрации;
- нелинейная акустика
- оптоакустика;
- медицинская акустика;
- акустика твердого тела;
- излучение и прием звука;
- акустические преобразователи;
- обработка акустических сигналов;
- техническая акустика;
- биоакустика и физиология слуха.</orgOccupation>
<orgShortNameEng>Acoustics Institute</orgShortNameEng>
<orgShortNameRus>АКИН</orgShortNameRus>
<orgs>2</orgs>
<orgtype>НИИ,конструкторские бюро,научно-производ</orgtype>
<orgtypeId>3</orgtypeId>
</return>
</getOrgDetailsResponse>
</env:Body>
</env:Envelope> -
3. Re: Problem using complex type in bpel. WS invocation failed java.lang.IllegalArgumentException: Cannot obtain wsdl service error
christy Jul 6, 2010 9:30 AM (in response to jeff.yuchang)Hi Jeff!
Thank you very much for your help! I think it will solve the problem because I use RiftSaw 2.0.0
-
4. Re: Problem using complex type in bpel. WS invocation failed java.lang.IllegalArgumentException: Cannot obtain wsdl service error
christy Jul 6, 2010 11:38 AM (in response to christy)I have the same problem... I installed RiftSaw2.1.0-CR2 and tried to invoke this process but I have the same error...
I have JBossAS 5.1.0, java 1.6 and RiftSaw2.1.0-CR2. Any ideas?
-
5. Re: Problem using complex type in bpel. WS invocation failed java.lang.IllegalArgumentException: Cannot obtain wsdl service error
jeff.yuchang Jul 6, 2010 11:26 PM (in response to christy)Hi Christy,
I've just finished testing against 2.1.0.CR2, it works ok... just double check, did you remove the $JBossAS/server/default/data folder, as between RiftSaw 2.0.0.Final and 2.1.0.CR2, the database schema has been changed, so by removing the data folder, you will get a new db schema populated.
Regards
Jeff
-
6. Re: Problem using complex type in bpel. WS invocation failed java.lang.IllegalArgumentException: Cannot obtain wsdl service error
christy Jul 7, 2010 4:54 AM (in response to jeff.yuchang)Hi Jeff,
I still have the same problem.
I removed $JBossAS/server/default/data, drop and create schema in database, then I created new project where I tried again to invoke this web-service and I still have the same error. It is very strange. I created a lot of processes where I call another web-services and they work fine. This problem is strange..
-
7. Re: Problem using complex type in bpel. WS invocation failed java.lang.IllegalArgumentException: Cannot obtain wsdl service error
jeff.yuchang Jul 7, 2010 6:52 AM (in response to christy)Hi Christy,
Are you using the Java client code to do the test? or using soap-ui tool?
Could you please tell me the request message that you used so that I can re-test it under my local box.
Regards
Jeff
-
8. Re: Problem using complex type in bpel. WS invocation failed java.lang.IllegalArgumentException: Cannot obtain wsdl service error
christy Jul 7, 2010 7:24 AM (in response to jeff.yuchang)Jeff, I'm using Oxygen for testing. This is the request:
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header/>
<SOAP-ENV:Body>
<InvokeOrgsProcessRequest xmlns="http://processes/invokes/ws/orgs">
<input>1</input>
</InvokeOrgsProcessRequest>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>Thank you very much for your help! Maybe there is something with libs?
Best regards,
Kristina
-
9. Re: Problem using complex type in bpel. WS invocation failed java.lang.IllegalArgumentException: Cannot obtain wsdl service error
jeff.yuchang Jul 7, 2010 7:52 AM (in response to christy)Hi Christy,
I've used the project that you attached on this thread, but once I deployed this artifact, I don't think your soap request is correct. specifically, this operation is not correct.
I've updated your soap request into following, and then it invokes successfully.
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header/>
<SOAP-ENV:Body>
<MainProcessRequest xmlns="http://projects/ws/orgs">
<input>1</input>
</MainProcessRequest>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>Please noted that both operation name and the namespace.
Am I missing something with regard to this example?
Regards
Jeff
-
10. Re: Problem using complex type in bpel. WS invocation failed java.lang.IllegalArgumentException: Cannot obtain wsdl service error
christy Jul 7, 2010 8:09 AM (in response to jeff.yuchang)Hi Jeff,
I think my request is wright too. Name and namespace are different because I created new process in new namespace with new name (but the functionality of the process is the same). I think the problem is somewhere in my JBoss libs or may by in JBoss caching. I found the jira with the same problem and I understand that it was not solved.
Best regards,
Kristina
-
11. Re: Problem using complex type in bpel. WS invocation failed java.lang.IllegalArgumentException: Cannot obtain wsdl service error
christy Jul 8, 2010 9:21 AM (in response to christy)Now I have one more process with the same error. 6 processes works fine and 2 give this error. May be there is something with my rifrsaw libs..I do not know.
-
12. Re: Problem using complex type in bpel. WS invocation failed java.lang.IllegalArgumentException: Cannot obtain wsdl service error
christy Jul 8, 2010 11:26 AM (in response to christy)Hi Jeff,
could you please give me the list of jars that are in the directory JBOSS AS 5.1.0\client. I think maybe the problem is there? Because now I have 3 processes with the same error and 6 processe work fine.
-
13. Re: Problem using complex type in bpel. WS invocation failed java.lang.IllegalArgumentException: Cannot obtain wsdl service error
jeff.yuchang Jul 9, 2010 3:53 AM (in response to christy)Hi Chris,
here is the list:
--------------------------
activation.jar
antlr.jar
avalon-framework.jar
commons-logging.jar
concurrent.jar
ejb3-persistence.jar
FastInfoset.jar
getopt.jar
hibernate-annotations.jar
jacorb.jar
javassist.jar
jaxb-api.jar
jaxb-impl.jar
jaxb-xjc.jar
jaxws-rt.jar
jaxws-tools.jar
jbossall-client.jar
jboss-aop-client.jar
jboss-appclient.jar
jboss-aspect-jdk50-client.jar
jboss-client.jar
jboss-common-core.jar
jbosscx-client.jar
jboss-deployers-client.jar
jboss-deployers-client-spi.jar
jboss-deployers-core.jar
jboss-deployers-core-spi.jar
jboss-deployers-vfs.jar
jboss-deployers-vfs-spi.jar
jboss-deployment.jar
jboss-ejb3-common-client.jar
jboss-ejb3-core-client.jar
jboss-ejb3-ext-api-impl.jar
jboss-ejb3-ext-api.jar
jboss-ejb3-proxy-clustered-client.jar
jboss-ejb3-proxy-impl-client.jar
jboss-ejb3-proxy-spi-client.jar
jboss-ejb3-security-client.jar
jboss-ha-client.jar
jboss-ha-legacy-client.jar
jboss-iiop-client.jar
jboss-integration.jar
jboss-j2se.jar
jboss-jaspi-api.jar
jboss-javaee.jar
jbossjmx-ant.jar
jboss-jsr77-client.jar
jbossjts-integration.jar
jbossjts.jar
jboss-logging-jdk.jar
jboss-logging-log4j.jar
jboss-logging-spi.jar
jboss-main-client.jar
jboss-mdr.jar
jboss-messaging-client.jar
jboss-metadata.jar
jboss-remoting.jar
jboss-security-spi.jar
jboss-serialization.jar
jboss-srp-client.jar
jbosssx-as-client.jar
jbosssx-client.jar
jboss-system-client.jar
jboss-system-jmx-client.jar
jbossws-common.jar
jbossws-framework.jar
jbossws-jboss50.jar
jbossws-native-client.jar
jbossws-native-core.jar
jbossws-native-jaxrpc.jar
jbossws-native-jaxws-ext.jar
jbossws-native-jaxws.jar
jbossws-native-saaj.jar
jbossws-spi.jar
jboss-xml-binding.jar
jettison.jar
jmx-client.jar
jmx-invoker-adaptor-client.jar
jnp-client.jar
log4j.jar
logkit.jar
mail.jar
policy.jar
scout.jar
slf4j-api.jar
slf4j-jboss-logging.jar
stax-api.jar
stax-ex.jar
streambuffer.jar
trove.jar
wsdl4j.jar
wstx.jar
xmlsec.jar -
14. Re: Problem using complex type in bpel. WS invocation failed java.lang.IllegalArgumentException: Cannot obtain wsdl service error
christy Jul 13, 2010 10:19 AM (in response to jeff.yuchang)Hi Jeff!
Thank you very much for your help. I have exactly the same libs. So the problem is somewhere else. I have every second - third process with this exeption.
Best regards,
Kristina