-
1. Re: OperationDesc for a method was not synchronized to a met
thomas.diesler Oct 28, 2005 10:23 AM (in response to tpallavi)The log should tell you why?
Try with the latest, it has better logging in that area
cvs co -r Branch_4_0 jboss-4.0.x -
2. Re: OperationDesc for a method was not synchronized to a met
tpallavi Oct 28, 2005 11:46 AM (in response to tpallavi)Well it seems that jboss 4.0.2 has a bug that does not allow more than one parameter in the bean methods. When I reduced the parameters in the register method to only one, it works just fine. I should have mentioned that I was working on jboss4.0.2.
Thanks -
3. Re: OperationDesc for a method was not synchronized to a met
sudhakaratbits Jan 12, 2006 3:39 AM (in response to tpallavi)We are facing exactly the same problem of passing two parameters to a bean method. Is it a bug in JBoss4.0.2 or a problem with our way of deploying the webservice?
pallavi, can u pls tell me where did u find the documentation to confirm it is a bug in JBoss4.0.2? -
4. Re: OperationDesc for a method was not synchronized to a met
thomas.diesler Jan 20, 2006 12:27 AM (in response to tpallavi)There must be something else wrong. Multiple parameters are of course supported in rpc/literal and document/literal wrapped.
Have a look at the samples attached to the main wiki. -
5. Re: OperationDesc for a method was not synchronized to a met
luan Jan 25, 2006 4:46 PM (in response to tpallavi)I also got the error with 3 parameters in document/literal SOAP operation, two are String, another is a Byte array. If use rpc/literal, wsdl can be accessed successfully.
Is Byte[] array supported as a parameter? Somewhere I read that array is not serializable, do the parameters need to be serializable?
Thanks for your help,
Luan -
6. Re: OperationDesc for a method was not synchronized to a met
tpallavi Jan 25, 2006 5:11 PM (in response to tpallavi)Basically under document literal style and using Jboss 4.0.2, more than one argument cannot be supported. If you put a wrapper class around the multiple arguments and only pass the one wrapper type as the argument, this way multiple arguments are served. This occurs only in Jboss 4.0.2.
-
7. Re: OperationDesc for a method was not synchronized to a met
luan Jan 25, 2006 5:30 PM (in response to tpallavi)Attached is the schema part of the wsdl, is this a non-wrapped style? (I read somewhere wrapped style complex type does not have attribute, but this one has):
<?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace=..............> -
8. Re: OperationDesc for a method was not synchronized to a met
luan Jan 25, 2006 5:32 PM (in response to tpallavi)Sorry the last part did not get sent:
-
9. Re: OperationDesc for a method was not synchronized to a met
luan Jan 25, 2006 5:33 PM (in response to tpallavi) -
10. Re: OperationDesc for a method was not synchronized to a met
luan Jan 25, 2006 5:34 PM (in response to tpallavi) -
11. Re: OperationDesc for a method was not synchronized to a met
luan Jan 25, 2006 5:36 PM (in response to tpallavi)Having problem sending the wsdl contents, it has name="processNPCMsg" attribute in complexType.
-
12. Re: OperationDesc for a method was not synchronized to a met
luan Jan 25, 2006 6:12 PM (in response to tpallavi)Thanks for your info.
I tried another one with 2 String parameters, did not work either.
By the way, do you know how to generate wrapped vs non-wrapped wsdl using jwsdp?
I checked the wscompile help, there is a unwrap feature, the default is disabled. But the generated wsdl in both cases have attibute name in the complexType.
Luan -
13. Re: OperationDesc for a method was not synchronized to a met
tpallavi Jan 25, 2006 6:25 PM (in response to tpallavi)If you have two String parameters, you can create a wrapper class(say StringWrap) whose attributes are these two String objects and then just pass an object of StringWrap as the parameter to your method. This is the only way that I could make my code work and it is what I mean by wrapper classes.
-
14. Re: OperationDesc for a method was not synchronized to a met
luan Jan 31, 2006 6:23 PM (in response to tpallavi)Thank you very much for your reply. As you mentioned, this problem only occurs in JBoss 4.0.2, it is resolved in JBoss 4.0.3.