Re: [Axis2] SOAP12 parameter types

[Evgeniy Vyborov]

Yes. I need to obtain details of the operations (parameters and theit types). I 
was trying to use wsdl4j, but the only thing I can get is org.w3c.dom.Element, 
that represents wsdl:types. I'm not sure that this is optimal way to parse 
parameters from the Element by hand. It is really strange when I easily can 
get all necessary data for SOAP1.1 binding, but I can't do the same with 
SOAP1.2 binding.

Gurus, please, help me solve this problem. This is very necessary for me now.

Thanks,
Eugene
 On Nov 20, 2007 7:28 PM, Evgeniy Vyborov  wrote:
 Hi, everyone.

 I worked with Axis1.x and I used the next code to determine  operations and
 parameter types of the concrete port:
 ...
 SymbolTable symbolTable = wsdlParser.getSymbolTable();
 BindingEntry bEntry =
 symbolTable.getBindingEntry(binding.getQName());
 Parameters parameters = null;
 Operation operation = null;
 Iterator i = bEntry.getParameters().keySet().iterator();
 while (i.hasNext()) {
 Operation o = (Operation) i.next();
 if (o.getName().equals(operationName)) {
 operation = o;
 parameters = (Parameters) bEntry.getParameters().get(o);

 break;
 }
 }
 ...
 But this code doesn't work with SOAP12 binding.
 Can someone tell me how to determine operations parameters and their types
 using Axis1 or Axis2?
you mean you want to parse a WSDL file and get the details of the
Operations. Then you can use
wsdl4j. This is what use inside Axis2.

thanks,
Amila.



 And one more...
 Please, tell me the way to convert AXIOM's OMElement to org.w3c.Element and
 backward.
Solved.

 Regards,
 Eugene


  
 Never miss a thing. Make Yahoo your homepage.



-- 
Amila Suriarachchi,
WSO2 Inc.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



   
-
Never miss a thing.   Make Yahoo your homepage.

Re: [Axis2] SOAP12 parameter types

[Amila Suriarachchi]

On Nov 20, 2007 7:28 PM, Evgeniy Vyborov [EMAIL PROTECTED] wrote:
 Hi, everyone.

 I worked with Axis1.x and I used the next code to determine  operations and
 parameter types of the concrete port:
 ...
 SymbolTable symbolTable = wsdlParser.getSymbolTable();
 BindingEntry bEntry =
 symbolTable.getBindingEntry(binding.getQName());
 Parameters parameters = null;
 Operation operation = null;
 Iterator i = bEntry.getParameters().keySet().iterator();
 while (i.hasNext()) {
 Operation o = (Operation) i.next();
 if (o.getName().equals(operationName)) {
 operation = o;
 parameters = (Parameters) bEntry.getParameters().get(o);

 break;
 }
 }
 ...
 But this code doesn't work with SOAP12 binding.
 Can someone tell me how to determine operations parameters and their types
 using Axis1 or Axis2?
you mean you want to parse a WSDL file and get the details of the
Operations. Then you can use
wsdl4j. This is what use inside Axis2.

thanks,
Amila.

 And one more...
 Please, tell me the way to convert AXIOM's OMElement to org.w3c.Element and
 backward.

 Regards,
 Eugene


  
 Never miss a thing. Make Yahoo your homepage.



-- 
Amila Suriarachchi,
WSO2 Inc.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[Axis2] SOAP12 parameter types

[Evgeniy Vyborov]

Hi, everyone.

I worked with Axis1.x and I used the next code to determine  operations and 
parameter types of the concrete port:
...
SymbolTable symbolTable = wsdlParser.getSymbolTable();
BindingEntry bEntry = symbolTable.getBindingEntry(binding.getQName());
Parameters parameters = null;
Operation operation = null;
Iterator i = bEntry.getParameters().keySet().iterator();
while (i.hasNext()) {
Operation o = (Operation) i.next();
if (o.getName().equals(operationName)) {
operation = o;
parameters = (Parameters) bEntry.getParameters().get(o);

break;
}
}
...
But this code doesn't work with SOAP12 binding.
Can someone tell me how to determine operations parameters and their types 
using Axis1 or Axis2?

And one more...
Please, tell me the way to convert AXIOM's OMElement to org.w3c.Element and  
backward.

Regards,
Eugene

   
-
Never miss a thing.   Make Yahoo your homepage.