RichTextEditor and multiple TEXTFORMATs

2009-06-11 Thread herbison

Can someone tell me why this is happening?
If I place this in a RichTextEditor's htmlText field:

TEXTFORMAT LEADING=2P ALIGN=LEFT  cows and dogs/P/TEXTFORMAT


and read it back, without doing a thing to it, i get this:

TEXTFORMAT LEADING=2P ALIGN=LEFT/P/TEXTFORMATTEXTFORMAT
LEADING=2P ALIGN=LEFT  /P/TEXTFORMATTEXTFORMAT LEADING=2P
ALIGN=LEFT/P/TEXTFORMATTEXTFORMAT LEADING=2P ALIGN=LEFT 
cows and dogs/P/TEXTFORMATTEXTFORMAT LEADING=2P ALIGN=LEFT   
/P/TEXTFORMATTEXTFORMAT LEADING=2P
ALIGN=LEFT/P/TEXTFORMATTEXTFORMAT LEADING=2P ALIGN=LEFT 
/P/TEXTFORMAT
-- 
View this message in context: 
http://www.nabble.com/RichTextEditor-and-multiple-TEXTFORMATs-tp23989057p23989057.html
Sent from the Axis - User mailing list archive at Nabble.com.



Re: Axis2 generated wsdl soap address is 0.0.0.0

2007-11-01 Thread Daniel Herbison

There seems to be an extra interface card on the machine that is not
connected.  Is there a way in tomcat/axis to force it to use a specific card
or ip?



Sanka Samaranayke wrote:
 
 Hi Daniel, 
 
 Can you please check whether the IP of the machine on which you
 experiencing the problem is being set properly? 
 I think the problem must be that the IP of the network interface of that
 particular machine has been set to 0.0.0.0 where it is being picked by
 Axis2 WSDL generating mechanism when calculating service endpoint
 addresses.
 
 --Sanka
 
 
 Daniel Herbison wrote:
 Hi All! 
 I have a web service deployed on one machine under axis2 and i'm calling
 it
 using flex and everything is working great.  However when I place the
 service on another machine under axis2 i can no longer run the services
 from
 flex but they do run fine from the browser.  Flex is complaining about
 the
 soap:address being set to 0.0.0.0, see below.  Why is the WSDL being set
 to
 0.0.0.0 on one machine and on the other machine it is being set to the
 correct ip 

 - wsdl:service name=IEventService 
 - wsdl:port name=IEventServiceSOAP11port_http
 binding=axis2:IEventServiceSOAP11Binding 
   soap:address
 location=http://0.0.0.0:8086/axis2/services/IEventService;
 / 
   /wsdl:port 
 - wsdl:port name=IEventServiceSOAP12port_http
 binding=axis2:IEventServiceSOAP12Binding 
   soap12:address
 location=http://0.0.0.0:8086/axis2/services/IEventService; / 
   /wsdl:port 
 - wsdl:port name=IEventServiceHttpport
 binding=axis2:IEventServiceHttpBinding 
   http:address
 location=http://0.0.0.0:8086/axis2/services/IEventService;
 / 
   /wsdl:port 
   /wsdl:service
   
 
 
 -- 
 Sanka Samaranayake
 WSO2 Inc.
 
 http://www.bloglines.com/blog/sanka
 http://www.wso2.org/
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 

-- 
View this message in context: 
http://www.nabble.com/Axis2-generated-wsdl-soap-address-is-0.0.0.0-tf4713352.html#a13529395
Sent from the Axis - User mailing list archive at Nabble.com.


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



Axis2 generated wsdl soap address is 0.0.0.0

2007-10-29 Thread Daniel Herbison

Hi All! 
I have a web service deployed on one machine under axis2 and i'm calling it
using flex and everything is working great.  However when I place the
service on another machine under axis2 i can no longer run the services from
flex but they do run fine from the browser.  Flex is complaining about the
soap:address being set to 0.0.0.0, see below.  Why is the WSDL being set to
0.0.0.0 on one machine and on the other machine it is being set to the
correct ip 

- wsdl:service name=IEventService 
- wsdl:port name=IEventServiceSOAP11port_http
binding=axis2:IEventServiceSOAP11Binding 
  soap:address location=http://0.0.0.0:8086/axis2/services/IEventService;
/ 
  /wsdl:port 
- wsdl:port name=IEventServiceSOAP12port_http
binding=axis2:IEventServiceSOAP12Binding 
  soap12:address
location=http://0.0.0.0:8086/axis2/services/IEventService; / 
  /wsdl:port 
- wsdl:port name=IEventServiceHttpport
binding=axis2:IEventServiceHttpBinding 
  http:address location=http://0.0.0.0:8086/axis2/services/IEventService;
/ 
  /wsdl:port 
  /wsdl:service
-- 
View this message in context: 
http://www.nabble.com/Axis2-generated-wsdl-soap-address-is-0.0.0.0-tf4713352.html#a13472967
Sent from the Axis - User mailing list archive at Nabble.com.


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



Re: wsdl:service soap12:address set to 0.0.0.0, why?

2007-09-13 Thread Daniel Herbison

it is using ipv4 and with only 1 network card.


dims wrote:
 
 How many network cards does this new box have? is it using IPv6?
 
 thanks,
 dims
 
 On 9/12/07, Daniel Herbison [EMAIL PROTECTED] wrote:

 I have a service running under axis2, on one server, and it runs great
 but
 when I take the aar file and copy it to another server, to run under a
 different instance of axis2, I get this 0.0.0.0 soap address and the
 client
 I'm using doesn't like it!  Why?  The original server places the host ip
 in
 that position. Do I have axis2 or tomcat set up incorrectly?

 - wsdl:service name=IEventService
 - wsdl:port name=IEventServiceSOAP11port_http
 binding=axis2:IEventServiceSOAP11Binding
   soap:address
 location=http://0.0.0.0:8086/axis2/services/IEventService;
 /
   /wsdl:port
 - wsdl:port name=IEventServiceSOAP12port_http
 binding=axis2:IEventServiceSOAP12Binding
   soap12:address
 location=http://0.0.0.0:8086/axis2/services/IEventService; /
   /wsdl:port
 - wsdl:port name=IEventServiceHttpport
 binding=axis2:IEventServiceHttpBinding
   http:address
 location=http://0.0.0.0:8086/axis2/services/IEventService;
 /
   /wsdl:port
   /wsdl:service
 --
 View this message in context:
 http://www.nabble.com/wsdl%3Aservice-soap12%3Aaddress-set-to-0.0.0.0%2C-why--tf4432083.html#a12644352
 Sent from the Axis - User mailing list archive at Nabble.com.


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


 
 
 -- 
 Davanum Srinivas :: http://davanum.wordpress.com
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 

-- 
View this message in context: 
http://www.nabble.com/wsdl%3Aservice-soap12%3Aaddress-set-to-0.0.0.0%2C-why--tf4432083.html#a12654467
Sent from the Axis - User mailing list archive at Nabble.com.


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



wsdl:service soap12:address set to 0.0.0.0, why?

2007-09-12 Thread Daniel Herbison

I have a service running under axis2, on one server, and it runs great but
when I take the aar file and copy it to another server, to run under a
different instance of axis2, I get this 0.0.0.0 soap address and the client
I'm using doesn't like it!  Why?  The original server places the host ip in
that position. Do I have axis2 or tomcat set up incorrectly?

- wsdl:service name=IEventService
- wsdl:port name=IEventServiceSOAP11port_http
binding=axis2:IEventServiceSOAP11Binding
  soap:address location=http://0.0.0.0:8086/axis2/services/IEventService;
/ 
  /wsdl:port
- wsdl:port name=IEventServiceSOAP12port_http
binding=axis2:IEventServiceSOAP12Binding
  soap12:address
location=http://0.0.0.0:8086/axis2/services/IEventService; / 
  /wsdl:port
- wsdl:port name=IEventServiceHttpport
binding=axis2:IEventServiceHttpBinding
  http:address location=http://0.0.0.0:8086/axis2/services/IEventService;
/ 
  /wsdl:port
  /wsdl:service
-- 
View this message in context: 
http://www.nabble.com/wsdl%3Aservice-soap12%3Aaddress-set-to-0.0.0.0%2C-why--tf4432083.html#a12644352
Sent from the Axis - User mailing list archive at Nabble.com.


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



Re: [Axis2] Creating Axis2 SOAP Header

2007-05-11 Thread Daniel Herbison

Thank you so far for your help!

The code is getting to the call (invokeBlocking) but is failing with this
exception:

Exception in thread main org.apache.axiom.soap.SOAPProcessingException:
Expecting an implementation of SOAP Envelope as the parent. But received
some other implementation

Could the header be causing this?

When I print the header I see (this looks ok):
soapenv:Header xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope;
 BasicCredentials xmlns=beta
  serviceIdstring1/serviceId
  serviceKeystring2/serviceKey
 /BasicCredentials
/soapenv:Header

current code:
RPCServiceClient serviceClient = new RPCServiceClient();
Options options = serviceClient.getOptions();
options.setSoapVersionURI(org.apache.axis2.namespace.Constants.URI_SOAP12_ENV);
options.setTo(targetEPR);

// start header build
SOAPFactory factory = (SOAPFactory) OMAbstractFactory.getSOAP12Factory();
OMNamespace omNs = factory.createOMNamespace(beta, ); 
SOAPHeader header = factory.createSOAPHeader();
OMElement basicCredentials = factory.createOMElement(BasicCredentials,
omNs); 
OMElement serviceId = factory.createOMElement(serviceId, omNs); 
OMText serviceIdText = factory.createOMText(serviceId, agentID);
serviceId.addChild(serviceIdText); 
OMElement serviceKey = factory.createOMElement(serviceKey, omNs); 
OMText serviceKeyText = factory.createOMText(serviceKey, agentToken);
serviceKey.addChild(serviceKeyText); 
basicCredentials.addChild(serviceId);
basicCredentials.addChild(serviceKey);
header.addChild(basicCredentials);
// end header build

serviceClient.addHeader(header);
QName opSetClaim = new QName(beta, GetClaim );
Object[] opSetParams = new Object[] { agentID, agentToken, requestor };
Class[] returnTypes = new Class[] { Object.class };
Exception occuring on next line
Object[] response = serviceClient.invokeBlocking(opSetClaim, opSetParams,
returnTypes);


Eran Chinthaka wrote:
 
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 Ok, the first advice is *never* use impl classes inside Axiom. Always
 use the factories. The reason is we have multiple implementations of them.
 
 To correct your problem, the easiest way is to create an OMElement
 rather than a SOAPHeaderBlock and call serviceClient.addHeader(OMElement).
 
 The second option is to use the created SOAP12Factory to create
 SOAPHeaderBlock.
 use soapFactory.createSOAPHeaderBlock(...)
 
 HTH.
 Chinthaka
 
 Daniel Herbison wrote:
 I'm trying to add the SOAP header, described in comment in code below, to
 a
 RPC call to a service.  First of all I really do not know if the code to
 create the header is correct, i think it is in the ball park(?)  But I
 get a
 run time error of:
 
 Exception in thread main java.lang.ClassCastException:
 org.apache.axiom.om.impl.OMNamespaceImpl
 at
 org.apache.axiom.soap.impl.dom.SOAPHeaderBlockImpl.init(SOAPHeaderBlockImpl.java:54)
 at
 org.apache.axiom.soap.impl.dom.soap12.SOAP12HeaderBlockImpl.init(SOAP12HeaderBlockImpl.java:45)
 at rpcAxSys.main(Unknown Source)
 
 the line causing the run time error is marked below, why is this doing
 this? 
 Also, is the header creation correct?
 
 code--
 RPCServiceClient serviceClient = new RPCServiceClient();
 Options options = serviceClient.getOptions();
 EndpointReference targetEPR = new
 EndpointReference(https://xyz/Authorize/Service.asmx;);
 options.setTo(targetEPR);
 
 /* header build
  soap:Header
   BasicCredentials xmlns=beta
serviceIdstring1/serviceId
serviceKeystring2/serviceKey  
   /BasicCredentials
  /soap:Header
  */
 OMFactory fac = OMAbstractFactory.getOMFactory();
 OMNamespace omNs = fac.createOMNamespace(beta, xmlns); 
 
 SOAPFactory soapFactory = new SOAP12Factory(); 
 SOAPHeaderBlock soapHeaderBlock = new
 SOAP12HeaderBlockImpl(Security,omNs,soapFactory); 
 soapHeaderBlock.setMustUnderstand(true); 
 
 OMElement basicCredentials = fac.createOMElement(BasicCredentials,
 omNs); 
 
 OMElement serviceId = fac.createOMElement(serviceId, omNs); 
 OMText serviceIdText = fac.createOMText(serviceId, agentID);
 serviceId.addChild(serviceIdText); 
 
 OMElement serviceKey = fac.createOMElement(serviceKey, omNs); 
 OMText serviceKeyText = fac.createOMText(serviceKey, agentToken);
 serviceKey.addChild(serviceKeyText); 
 
 basicCredentials.addChild(serviceId); 
 basicCredentials.addChild(serviceKey); 
 
 soapHeaderBlock.addChild(basicCredentials); 
 
 serviceClient.addHeader(soapHeaderBlock); 
 // end header build
 
 QName opSetClaim = new QName(beta, GetClaim );
 
 Object[] opSetParams = new Object[] { agentID, agentToken, requestor };
 Class[] returnTypes = new Class[] { Object.class };
 
 Object[] response = serviceClient.invokeBlocking(opSetClaim, opSetParams,
 returnTypes);
 
 
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.3 (GNU/Linux)
 Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
 
 iD8DBQFGQ/jSjON2uBzUhh8RAqVZAKC0exk4tKs9zIALPgI65NYyo+AbxQCePUqQ
 xt15TCLceO7fDJe517267k8=
 =duG+
 -END PGP SIGNATURE

Re: Creating Axis2 SOAP Header

2007-05-10 Thread Daniel Herbison

Thank you for your replies!
I tried the code below and still get a runtime casting error.

Exception in thread main java.lang.ClassCastException:
org.apache.axiom.soap.impl.llom.soap12.SOAP12Factory
at rpcAxSys.header2(Unknown Source)
at rpcAxSys.main(Unknown Source)

SOAP12Factory factory = (SOAP12Factory)
OMAbstractFactory.getSOAP12Factory();
OMNamespace omNs = factory.createOMNamespace(beta.va.nortel.com, xmlns); 

SOAPHeader header = factory.createSOAPHeader();

SOAPHeaderBlock block = factory.createSOAPHeaderBlock(BasicCredentials,
omNs);

OMElement serviceId = factory.createOMElement(serviceId, omNs); 
OMText serviceIdText = factory.createOMText(serviceId, agentID);
serviceId.addChild(serviceIdText); 

OMElement serviceKey = factory.createOMElement(serviceKey, omNs); 
OMText serviceKeyText = factory.createOMText(serviceKey, agentToken);
serviceKey.addChild(serviceKeyText); 

block.addChild(serviceId);
block.addChild(serviceKey);

header.addChild(block);


Amila Suriarachchi wrote:
 
 I am not sure about your problem.
 but add this code to specifically set the soap12 for service client.
 
 clientOptions = new Options();
 clientOptions.setSoapVersionURI(SOAP12Constants.SOAP_ENVELOPE_NAMESPACE_URI
 );
 serviceClient.setOptions(clientOptions);
 
 On 5/10/07, Michele Mazzucco [EMAIL PROTECTED] wrote:

 Daniel,

 I think the way you create the SOAPHeaderBlock is not correct. Can
 you try this way please?

 SOAP12Factory factory = (SOAP12Factory)
 OMAbstractFactory.getSOAP12Factory();
 OMNamespace omNs = factory.createOMNamespace(
 http://...;,
 ...
 );

 SOAPEnvelope env = factory.createSOAPEnvelope();
 SOAPHeader header = factory.createSOAPHeader();
 SOAPHeaderBlock block = factory.createSOAPHeaderBlock(
 SOAPHeaderConstants.ELEM_QOSP_HEADER_BLOCK, omNs);
 OMElement type = factory.createOMElement(
 SOAPHeaderConstants.ELEM_MESSAGE_TYPE, omNs);

 type.setText(MessageType.UPLOAD.value());
 block.addChild(type);
 header.addChild(block);

 SOAPBody body = factory.createSOAPBody();
 OMElement method = factory.createOMElement(SOAPUtils.UPLOAD_SERVICE,
 omNs);

 OMElement name = factory.createOMElement(
 SOAPUtils.UPLOAD_SERVICE_FILE_NAME, omNs);
 name.setText(this.fileName);

 method.addChild(name);
 body.addChild(method);
 env.addChild(header);
 env.addChild(body);


 Michele




 On 9 May 2007, at 22:26, Daniel Herbison wrote:

 
  I'm trying to add the SOAP header, described in comment in code
  below, to a
  RPC call to a service.  First of all I really do not know if the
  code to
  create the header is correct, i think it is in the ball park(?)
  But I get a
  run time error of:
 
  Exception in thread main java.lang.ClassCastException:
  org.apache.axiom.om.impl.OMNamespaceImpl
  at
  org.apache.axiom.soap.impl.dom.SOAPHeaderBlockImpl.init
  (SOAPHeaderBlockImpl.java:54)
  at
  org.apache.axiom.soap.impl.dom.soap12.SOAP12HeaderBlockImpl.init
  (SOAP12HeaderBlockImpl.java:45)
  at rpcAxSys.main(Unknown Source)
 
  the line causing the run time error is marked below, why is this
  doing this?
  Also, is the header creation correct?
 
  code--
  RPCServiceClient serviceClient = new RPCServiceClient();
  Options options = serviceClient.getOptions();
  EndpointReference targetEPR = new
  EndpointReference(https://xyz/Authorize/Service.asmx;);
  options.setTo(targetEPR);
 
  /* header build
   soap:Header
BasicCredentials xmlns=beta
 serviceIdstring1/serviceId
 serviceKeystring2/serviceKey
/BasicCredentials
   /soap:Header
   */
  OMFactory fac = OMAbstractFactory.getOMFactory();
  OMNamespace omNs = fac.createOMNamespace(beta, xmlns);
 
  SOAPFactory soapFactory = new SOAP12Factory();
  SOAPHeaderBlock soapHeaderBlock = new
  SOAP12HeaderBlockImpl(Security,omNs,soapFactory);
  soapHeaderBlock.setMustUnderstand(true);
 
  OMElement basicCredentials = fac.createOMElement
  (BasicCredentials, omNs);
 
  OMElement serviceId = fac.createOMElement(serviceId, omNs);
  OMText serviceIdText = fac.createOMText(serviceId, agentID);
  serviceId.addChild(serviceIdText);
 
  OMElement serviceKey = fac.createOMElement(serviceKey, omNs);
  OMText serviceKeyText = fac.createOMText(serviceKey, agentToken);
  serviceKey.addChild(serviceKeyText);
 
  basicCredentials.addChild(serviceId);
  basicCredentials.addChild(serviceKey);
 
  soapHeaderBlock.addChild(basicCredentials);
 
  serviceClient.addHeader(soapHeaderBlock);
  // end header build
 
  QName opSetClaim = new QName(beta, GetClaim );
 
  Object[] opSetParams = new Object[] { agentID, agentToken,
  requestor };
  Class[] returnTypes = new Class[] { Object.class };
 
  Object[] response = serviceClient.invokeBlocking(opSetClaim,
  opSetParams,
  returnTypes);
 
  --
  View this message in context: http://www.nabble.com/Creating-Axis2-
  SOAP-Header-tf3718396.html#a10403132
  Sent from the Axis - User

Re: Creating Axis2 SOAP Header

2007-05-10 Thread Daniel Herbison

I changed this:

SOAPFactory factory = (SOAPFactory) OMAbstractFactory.getSOAP12Factory();

and got rid of the error but it is failing on the call with:

Exception in thread main org.apache.axiom.soap.SOAPProcessingException:
Expecting an implementation of SOAP Envelope as the parent. But received
some other implementation
at
org.apache.axiom.soap.impl.llom.SOAPHeaderImpl.checkParent(SOAPHeaderImpl.java:369)
at
org.apache.axiom.soap.impl.llom.SOAPElement.setParent(SOAPElement.java:75)
at
org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:236)
at
org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:192)
at
org.apache.axis2.client.ServiceClient.addHeadersToEnvelope(ServiceClient.java:647)
at
org.apache.axis2.client.ServiceClient.fillSOAPEnvelope(ServiceClient.java:633)
at
org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:517)
at
org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:500)
at
org.apache.axis2.rpc.client.RPCServiceClient.invokeBlocking(RPCServiceClient.java:97)
at rpcAxSys.main(rpcAxSys.java:51)

Is there a way to print the soap message out before calling invokeBlocking?

Code excluding header code, same as before.

rpcAxSys rpc = new rpcAxSys(args[0],args[1],args[2]);
EndpointReference targetEPR = new
EndpointReference(https://pcary571.corp.nortel.com/Authorize/Service.asmx;);
RPCServiceClient serviceClient = new RPCServiceClient();
Options options = serviceClient.getOptions();
options.setTo(targetEPR);
serviceClient.addHeader(rpc.header2());  // header2 has header generation
code below
QName opSetClaim = new QName(beta, GetClaim );
Object[] opSetParams = new Object[] { rpc.agentID, rpc.agentToken,
rpc.requestor };
Class[] returnTypes = new Class[] { Object.class };
Object[] response = serviceClient.invokeBlocking(opSetClaim, opSetParams,
returnTypes); FAILING HERE 




Michele Mazzucco-2 wrote:
 
 Daniel,
 
 could you please enable the debug  of javac (it is enabled by default,
 remove the -g:none option) and tell us which line causes the problem?
 
 Michele
 
 On Thu, 2007-05-10 at 05:28 -0700, Daniel Herbison wrote:
 Thank you for your replies!
 I tried the code below and still get a runtime casting error.
 
 Exception in thread main java.lang.ClassCastException:
 org.apache.axiom.soap.impl.llom.soap12.SOAP12Factory
 at rpcAxSys.header2(Unknown Source)
 at rpcAxSys.main(Unknown Source)
 
 SOAP12Factory factory = (SOAP12Factory)
 OMAbstractFactory.getSOAP12Factory();
 OMNamespace omNs = factory.createOMNamespace(beta.va.nortel.com,
 xmlns); 
 
 SOAPHeader header = factory.createSOAPHeader();
 
 SOAPHeaderBlock block = factory.createSOAPHeaderBlock(BasicCredentials,
 omNs);
 
 OMElement serviceId = factory.createOMElement(serviceId, omNs); 
 OMText serviceIdText = factory.createOMText(serviceId, agentID);
 serviceId.addChild(serviceIdText); 
 
 OMElement serviceKey = factory.createOMElement(serviceKey, omNs); 
 OMText serviceKeyText = factory.createOMText(serviceKey, agentToken);
 serviceKey.addChild(serviceKeyText); 
 
 block.addChild(serviceId);
 block.addChild(serviceKey);
 
 header.addChild(block);
 
 
 Amila Suriarachchi wrote:
  
  I am not sure about your problem.
  but add this code to specifically set the soap12 for service client.
  
  clientOptions = new Options();
 
 clientOptions.setSoapVersionURI(SOAP12Constants.SOAP_ENVELOPE_NAMESPACE_URI
  );
  serviceClient.setOptions(clientOptions);
  
  On 5/10/07, Michele Mazzucco [EMAIL PROTECTED] wrote:
 
  Daniel,
 
  I think the way you create the SOAPHeaderBlock is not correct. Can
  you try this way please?
 
  SOAP12Factory factory = (SOAP12Factory)
  OMAbstractFactory.getSOAP12Factory();
  OMNamespace omNs = factory.createOMNamespace(
  http://...;,
  ...
  );
 
  SOAPEnvelope env = factory.createSOAPEnvelope();
  SOAPHeader header = factory.createSOAPHeader();
  SOAPHeaderBlock block = factory.createSOAPHeaderBlock(
  SOAPHeaderConstants.ELEM_QOSP_HEADER_BLOCK, omNs);
  OMElement type = factory.createOMElement(
  SOAPHeaderConstants.ELEM_MESSAGE_TYPE, omNs);
 
  type.setText(MessageType.UPLOAD.value());
  block.addChild(type);
  header.addChild(block);
 
  SOAPBody body = factory.createSOAPBody();
  OMElement method = factory.createOMElement(SOAPUtils.UPLOAD_SERVICE,
  omNs);
 
  OMElement name = factory.createOMElement(
  SOAPUtils.UPLOAD_SERVICE_FILE_NAME, omNs);
  name.setText(this.fileName);
 
  method.addChild(name);
  body.addChild(method);
  env.addChild(header);
  env.addChild(body);
 
 
  Michele
 
 
 
 
  On 9 May 2007, at 22:26, Daniel Herbison wrote:
 
  
   I'm trying to add the SOAP header, described in comment in code
   below, to a
   RPC call to a service.  First of all I really do not know if the
   code to
   create the header is correct, i think

Creating Axis2 SOAP Header

2007-05-09 Thread Daniel Herbison

I'm trying to add the SOAP header, described in comment in code below, to a
RPC call to a service.  First of all I really do not know if the code to
create the header is correct, i think it is in the ball park(?)  But I get a
run time error of:

Exception in thread main java.lang.ClassCastException:
org.apache.axiom.om.impl.OMNamespaceImpl
at
org.apache.axiom.soap.impl.dom.SOAPHeaderBlockImpl.init(SOAPHeaderBlockImpl.java:54)
at
org.apache.axiom.soap.impl.dom.soap12.SOAP12HeaderBlockImpl.init(SOAP12HeaderBlockImpl.java:45)
at rpcAxSys.main(Unknown Source)

the line causing the run time error is marked below, why is this doing this? 
Also, is the header creation correct?

code--
RPCServiceClient serviceClient = new RPCServiceClient();
Options options = serviceClient.getOptions();
EndpointReference targetEPR = new
EndpointReference(https://xyz/Authorize/Service.asmx;);
options.setTo(targetEPR);

/* header build
 soap:Header
  BasicCredentials xmlns=beta
   serviceIdstring1/serviceId
   serviceKeystring2/serviceKey  
  /BasicCredentials
 /soap:Header
 */
OMFactory fac = OMAbstractFactory.getOMFactory();
OMNamespace omNs = fac.createOMNamespace(beta, xmlns); 

SOAPFactory soapFactory = new SOAP12Factory(); 
SOAPHeaderBlock soapHeaderBlock = new
SOAP12HeaderBlockImpl(Security,omNs,soapFactory); 
soapHeaderBlock.setMustUnderstand(true); 

OMElement basicCredentials = fac.createOMElement(BasicCredentials, omNs); 

OMElement serviceId = fac.createOMElement(serviceId, omNs); 
OMText serviceIdText = fac.createOMText(serviceId, agentID);
serviceId.addChild(serviceIdText); 

OMElement serviceKey = fac.createOMElement(serviceKey, omNs); 
OMText serviceKeyText = fac.createOMText(serviceKey, agentToken);
serviceKey.addChild(serviceKeyText); 

basicCredentials.addChild(serviceId); 
basicCredentials.addChild(serviceKey); 

soapHeaderBlock.addChild(basicCredentials); 

serviceClient.addHeader(soapHeaderBlock); 
// end header build

QName opSetClaim = new QName(beta, GetClaim );

Object[] opSetParams = new Object[] { agentID, agentToken, requestor };
Class[] returnTypes = new Class[] { Object.class };

Object[] response = serviceClient.invokeBlocking(opSetClaim, opSetParams,
returnTypes);

-- 
View this message in context: 
http://www.nabble.com/Creating-Axis2-SOAP-Header-tf3718396.html#a10403132
Sent from the Axis - User mailing list archive at Nabble.com.


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



WstxEOFException Exception

2007-05-01 Thread Daniel Herbison

Hi!
I'm trying to consume a service using axis2 axiom and get the following
exception, anyone know why?
Axiom code is below also.

org.apache.axis2.AxisFault: com.ctc.wstx.exc.WstxEOFException: Unexpected
EOF in prolog
 at [row,col {unknown-source}]: [1,0]; nested exception is: 
org.apache.axiom.om.OMException: com.ctc.wstx.exc.WstxEOFException:
Unexpected EOF in prolog
 at [row,col {unknown-source}]: [1,0]
at
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:126)
at
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:67)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:252)
at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:202)
at
org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:579)
at
org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:508)
at test1.main(test1.java:51)
Caused by: org.apache.axiom.om.OMException:
com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog
 at [row,col {unknown-source}]: [1,0]
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:199)
at
org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.getSOAPEnvelope(StAXSOAPModelBuilder.java:158)
at
org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.identifySOAPVersion(StAXSOAPModelBuilder.java:132)
at
org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.init(StAXSOAPModelBuilder.java:107)
at
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:120)
... 6 more
Caused by: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog
 at [row,col {unknown-source}]: [1,0]
at 
com.ctc.wstx.sr.StreamScanner.throwUnexpectedEOF(StreamScanner.java:661)
at 
com.ctc.wstx.sr.BasicStreamReader.handleEOF(BasicStreamReader.java:2134)
at
com.ctc.wstx.sr.BasicStreamReader.nextFromProlog(BasicStreamReader.java:2040)
at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1069)
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:116)
... 10 more


CODE...

System.out.println(GetClaim(+id+,+token+,+requestor+));
OMElement GetClaim = GetClaim(id,token,requestor);

Options options = new Options();
options.setTo(targetEPR);
options.setTransportInProtocol(Constants.TRANSPORT_HTTP);

ServiceClient sender = new ServiceClient();
sender.setOptions(options);
OMElement result = sender.sendReceive(GetClaim);


-- 
View this message in context: 
http://www.nabble.com/WstxEOFException-Exception-tf3675595.html#a10270755
Sent from the Axis - User mailing list archive at Nabble.com.


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



Axis2, WSDL2Java and Rampart

2007-03-28 Thread herbison

Hi All!
I’m trying to access a .NET service using Axis2.  From what I understand, if
the WSDL (see policy below) has a WS security policy in it then WSDL2Java
will generate the setUsername and setPassword methods in the service stub. 
Is this correct?

Here is the WSDL2Java invocation:
sh ${AXIS2_HOME}/bin/axis2.sh \
org.apache.axis2.wsdl.WSDL2Java \
-uri service \
-d xmlbeans -s -r client_repository

The client repository has the rampart and addressing mar in it and the
axis2.xml.

When I run the WSDL2Java above I get the following output and NO username or
password stubs are created.  WHY?

Using AXIS2_HOME:   /home/coi/downloads/axis2-1.1.1
 Using JAVA_HOME:   /usr/jdk1.5.0_03
Retrieving schema at
'http://Pcary571.corp.nortel.com/WSDL/Authorize/ServiceBSP10.xml', relative
to 'http://pcary571.corp.nortel.com/WSDL/Authorize/ServiceBSP1.xml'.
Retrieving schema at
'http://Pcary571.corp.nortel.com/WSDL/Authorize/ServiceBSP12.xml', relative
to 'http://Pcary571.corp.nortel.com/WSDL/Authorize/ServiceBSP10.xml'.
Retrieving schema at
'http://Pcary571.corp.nortel.com/WSDL/Authorize/ServiceBSP11.xml', relative
to 'http://Pcary571.corp.nortel.com/WSDL/Authorize/ServiceBSP10.xml'.
Retrieving schema at
'http://Pcary571.corp.nortel.com/WSDL/Authorize/ServiceBSP12.xml', relative
to 'http://pcary571.corp.nortel.com/WSDL/Authorize/ServiceBSP1.xml'.
Retrieving schema at
'http://Pcary571.corp.nortel.com/WSDL/Authorize/ServiceBSP11.xml', relative
to 'http://pcary571.corp.nortel.com/WSDL/Authorize/ServiceBSP1.xml'.
Mar 28, 2007 10:54:01 AM
org.apache.axis2.xmlbeans.CodeGenerationUtility$Axis2EntityResolver
resolveEntity
INFO: Resolving schema with publicId [beta.va.nortel.com] and systemId
[/http:/Pcary571.corp.nortel.com/WSDL/Authorize/ServiceBSP10.xml]
Mar 28, 2007 10:54:02 AM
org.apache.axis2.xmlbeans.CodeGenerationUtility$Axis2EntityResolver
resolveEntity
INFO: Resolving schema with publicId
[http://schemas.microsoft.com/2003/10/Serialization/] and systemId
[/http:/Pcary571.corp.nortel.com/WSDL/Authorize/ServiceBSP11.xml]
Mar 28, 2007 10:54:02 AM
org.apache.axis2.xmlbeans.CodeGenerationUtility$Axis2EntityResolver
resolveEntity
INFO: Resolving schema with publicId
[http://schemas.microsoft.com/2003/10/Serialization/Arrays] and systemId
[/http:/Pcary571.corp.nortel.com/WSDL/Authorize/ServiceBSP12.xml]
Mar 28, 2007 10:54:12 AM org.apache.axis2.deployment.DeploymentEngine
prepareRepository
INFO: no services directory found under
/home/coi/projects/coi/source_code/coidw/axsysTest/client_repository
Mar 28, 2007 10:54:12 AM org.apache.axis2.deployment.DeploymentEngine
doDeploy
INFO: Deploying module : addressing-1.1.1
Mar 28, 2007 10:54:20 AM org.apache.axis2.deployment.DeploymentEngine
doDeploy
INFO: Deploying module : rampart-1.1
cannot create repository : policy will not be supported
cannot find a PolicyExtension to process
http://schemas.xmlsoap.org/ws/2005/07/securitypolicytype assertions
cannot find a PolicyExtension to process
http://schemas.xmlsoap.org/ws/2005/07/securitypolicytype assertions
Mar 28, 2007 10:54:21 AM org.apache.axis2.wsdl.codegen.writer.ClassWriter
createOutFile
INFO: File ./src/com/nortel/va/beta/ClaimProcessorStub.java will not be
overwritten.



WS security policy
wsp:Policy wsu:Id=BasicHttpBinding_IClaim_policy
- wsp:ExactlyOne
- wsp:All
- sp:TransportBinding
xmlns:sp=http://schemas.xmlsoap.org/ws/2005/07/securitypolicy;
- wsp:Policy
- sp:TransportToken
- wsp:Policy
  sp:HttpsToken RequireClientCertificate=false / 
  /wsp:Policy
  /sp:TransportToken
- sp:AlgorithmSuite
- wsp:Policy
  sp:Basic256 / 
  /wsp:Policy
  /sp:AlgorithmSuite
- sp:Layout
- wsp:Policy
  sp:Lax / 
  /wsp:Policy
  /sp:Layout
  sp:IncludeTimestamp / 
  /wsp:Policy
  /sp:TransportBinding
- sp:SignedSupportingTokens
xmlns:sp=http://schemas.xmlsoap.org/ws/2005/07/securitypolicy;
- wsp:Policy
- sp:UsernameToken
sp:IncludeToken=http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysToRecipient;
- wsp:Policy
  sp:WssUsernameToken10 / 
  /wsp:Policy
  /sp:UsernameToken
  /wsp:Policy
  /sp:SignedSupportingTokens
- sp:Wss10 xmlns:sp=http://schemas.xmlsoap.org/ws/2005/07/securitypolicy;
- wsp:Policy
  sp:MustSupportRefKeyIdentifier / 
  sp:MustSupportRefIssuerSerial / 
  /wsp:Policy
  /sp:Wss10
  /wsp:All
  /wsp:ExactlyOne
/wsp:Policy


-- 
View this message in context: 
http://www.nabble.com/Axis2%2C-WSDL2Java-and-Rampart-tf3481259.html#a9716824
Sent from the Axis - User mailing list archive at Nabble.com.


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



Re: [Axis2] Support of ws-policy?

2007-03-27 Thread herbison

Sanka:
I've been trying to do this exact thing and when notifiing wsdl2java about
the repository (axis2, it has rampart mar in it)  it tells me policy will
not be supported.  

Any ideas why?


WSDL2Java (using axis2.sh) cmd:
sh ${AXIS2_HOME}/bin/axis2.sh \
org.apache.axis2.wsdl.WSDL2Java \
-uri wsdl url \
-d xmlbeans -s -r $AXIS2_HOME/repository

I get:

...
Mar 27, 2007 4:48:06 PM org.apache.axis2.deployment.DeploymentEngine
doDeploy
INFO: Deploying Web service  version.aar
cannot create repository : policy will not be supported
cannot find a PolicyExtension to process
http://schemas.xmlsoap.org/ws/2005/07/securitypolicytype assertions
cannot find a PolicyExtension to process
http://schemas.xmlsoap.org/ws/2005/07/securitypolicytype assertions
Mar 27, 2007 4:48:07 PM org.apache.axis2.wsdl.codegen.writer.ClassWriter
createOutFile
INFO: File ./src/com/nortel/va/beta/ClaimProcessorStub.java will not be
overwritten.


Sanka Samaranayke wrote:
 
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 Hi Carsten,
 
 Right now we do have we a limited support for WSSecurity Policies in
 Axis2. For instance If you attach a policy with a Username token
 assertion then the wsdl2java will generate a stub with two utility
 methods to set username and the password.
 
 
 e.g.
 
 wsp:Policy
 xmlns:sp=http://schemas.xmlsoap.org/ws/2005/07/securitypolicy;
  
 xmlns:wsp=http://schemas.xmlsoap.org/ws/2004/09/policy;
 sp:SignedSupportingTokens
 wsp:Policy
 sp:UsernameToken
 sp:IncludeToken=http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysToRecipient;
 /
 /wsp:Policy
 /sp:SignedSupportingTokens
 /wsp:Policy
 
 

 You need to specify an axis2 repository with rampart module in it both
 at codegen time and runtime. At the codegen time you could specify
 the repository as the following codegen option.
 
  -r path to the repostiory.
 
 And when you creating the stub instance you need to pass a
 ConfigurationContext created using that repository. If do those two
 steps if will get a stub that has the above methods. Plus at the
 runtime the stub will automatically engage the security module and do
 whatever necessary.
 
 e.g.
   Stub stub = new Stub(.);
 
..
stub.setUsername(...);
stub.setPassword(...);
   
 
   stub.sendAndReceive(..);
 
 
 
 At the moment we are adding a new codebase to Apache Neethi project
 which is based on a much improved architecture. And based on that new
 implementation we will improve the support for WS Policy plus its
 extensions for Security, Reliable Messaging .. etc pretty soon.
 
 Keep in touch ..
 
 - --Sanka
 
 
 
 
 Carsten Ziegeler wrote:
 Can someone please give me a hint on how to turn on ws policy validation
 with Axis2? I already installed the rampart module.

 Will the wsdl2java code generator generate the necessary bit?

 Thanks
 Carsten
 
 
 - --
 Sanka Samaranayake
 WSO2 Inc.
 http://sankas.blogspot.com/ - http://www.wso2.net/
 T:+94-77-3506382 F:+94-11-2424304
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.2.1 (GNU/Linux)
 
 iD8DBQFEtQfV/Hd0ETKdgNIRAoqbAJ9AQA9Tr0DFMBHyOtFXnBRwRejhrACglquN
 gZNZLtiVjSGnSxW8Dd3dccI=
 =vkyN
 -END PGP SIGNATURE-
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 

-- 
View this message in context: 
http://www.nabble.com/-Axis2--Support-of-ws-policy--tf1930928.html#a9701947
Sent from the Axis - User mailing list archive at Nabble.com.


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



Axis 1.4 Security using UsernameToken

2007-03-21 Thread herbison

I'm tring to access a .NET service, using code generated by wsdl2java, where
I have to set the UsernameToken fields Username and Password in the soap
header.  How is this done?!!  I've been going around in circles all morning
and nothing seems to get me any closer in setting the soap fields.  This is
what the client looks like now:

String id=user;
String key=password;
PWCallback pwCallback = new PWCallback();
pwCallback.setUsername(id);
pwCallback.setPassword(key);

ClaimProcessorLocator loc = new ClaimProcessorLocator();
Remote remote = loc.getPort( Claim.class);
Stub axisPort = (Stub)remote;
axisPort._setProperty(UsernameToken.PASSWORD_TYPE,
WSConstants.PASSWORD_DIGEST);
axisPort._setProperty(WSHandlerConstants.USER, id);
axisPort._setProperty(WSHandlerConstants.PW_CALLBACK_REF, pwCallback);

IClaim iclaim = (IClaim) loc.getBasicHttpBinding_IClaim();
Claim claim = iclaim.getClaim();

-- 
View this message in context: 
http://www.nabble.com/Axis-1.4-Security-using-UsernameToken-tf3443206.html#a9601255
Sent from the Axis - User mailing list archive at Nabble.com.


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



Axis NullPointerException on array

2007-01-19 Thread herbison

Can anyone make since of the error I'm getting below.

I have a method 
String [] x getSite2SiteTraffic(String [] y) {...}

I used WSDL2Java to create the client stubs and invoked it like:

CoiDWDbApiService service = new CoiDWDbApiServiceLocator();
CoiDWDbApi coidw = service.getCoiDWDataService();

String [] sret = coidw.getSite2SiteTraffic(SITE2SITE); // SITE2SITE is an
array of strings

and I get this error:

Exception in thread main AxisFault
 faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
 faultSubcode: 
 faultString: java.lang.NullPointerException
 faultActor: 
 faultNode: 
 faultDetail: 
{http://xml.apache.org/axis/}hostname:zrtps0r7

java.lang.NullPointerException
at
org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
at
org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
at
org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown
Source)
at
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown
Source)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
at
org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
at
org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at
com.nortel.nmm.coidwServiceClients.CoiDWDataServiceSoapBindingStub.getSite2SiteTraffic(CoiDWDataServiceSoapBindingStub.java:2889)
at testSite2Site.main(testSite2Site.java:42)

HERE is the soap request:

?xml version=1.0 encoding=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
ns1:getSite2SiteTraffic
soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/;
xmlns:ns1=http://coidwServices.nmm.xx.com;
  htmlParams soapenc:arrayType=xsd:string[28]
xsi:type=soapenc:Array
xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;
htmlParams xsi:type=xsd:stringdoDomainGroups/htmlParams
htmlParams xsi:type=xsd:stringshowIN/htmlParams
htmlParams xsi:type=xsd:stringtypeReport/htmlParams
htmlParams xsi:type=xsd:stringdateData/htmlParams
htmlParams xsi:type=xsd:stringscheduler/htmlParams
htmlParams xsi:type=xsd:stringtimeSlice/htmlParams
htmlParams xsi:type=xsd:stringbottomMarginPercent/htmlParams
htmlParams xsi:type=xsd:stringloadTopDomains/htmlParams
htmlParams xsi:type=xsd:stringaddTrendLayer/htmlParams
htmlParams xsi:type=xsd:stringdomains/htmlParams
htmlParams xsi:type=xsd:stringdropDownCalendar/htmlParams
htmlParams xsi:type=xsd:stringgraphSelect/htmlParams
htmlParams xsi:type=xsd:stringbytediv/htmlParams
htmlParams xsi:type=xsd:stringorderByTraffic/htmlParams
htmlParams xsi:type=xsd:stringuseLastValidDate/htmlParams
htmlParams
xsi:type=xsd:stringrememberPrimaryConversation/htmlParams
htmlParams xsi:type=xsd:stringFromCity/htmlParams
htmlParams xsi:type=xsd:stringmonths/htmlParams
htmlParams xsi:type=xsd:stringtypeGroup/htmlParams
htmlParams xsi:type=xsd:stringFromRegion/htmlParams
htmlParams xsi:type=xsd:stringorientation/htmlParams
htmlParams xsi:type=xsd:stringloadEOM/htmlParams
htmlParams xsi:type=xsd:stringshowAllXAxisTics/htmlParams
htmlParams xsi:type=xsd:stringtimeInterval/htmlParams
htmlParams xsi:type=xsd:stringFromContinent/htmlParams
htmlParams xsi:type=xsd:stringrightMarginPercent/htmlParams
htmlParams xsi:type=xsd:stringuserID/htmlParams
htmlParams 

Style message

2007-01-16 Thread herbison

Does anyone have a beginning to end example of how to do a Axis web-service
of style message?  Server code, client code, wsdd, etc...
-- 
View this message in context: 
http://www.nabble.com/Style-message-tf3021821.html#a8392873
Sent from the Axis - User mailing list archive at Nabble.com.


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



Re: XML Encoding

2007-01-14 Thread herbison

Thank you Anne!

Until now I've been using the RPC style because it was easy and I had
control of who wanted to consume my services, only me!  Now I have some
macromedia flex folks wanting to use them and the xml encoding is not to
their liking.  I tried the wrapped style but the xml still comes across as
stated below.  If I use the message style then I will have to conform my
services to one of:

public Element [] method(Element [] bodies) or
public SOAPBodyElement [] method (SOAPBodyElement [] boides) or
public Document method(Document body) or
public void method(SOAPBodyEnvelope req, SOAPBodyEnvelope resp) ???

will the flex code on the client side have to use these same classes?

So their choices are the message style of do the encoding?



Anne Thomas Manes wrote:
 
 Use provider=java:MSG and the messaging API.
 
 Anne
 
 On 1/12/07, herbison [EMAIL PROTECTED] wrote:

 I need to write a function that will return a XML document.  When I do
 this
 the xml is encode with lt; and gt;.  How do I stop this from happing?

 THe wsdd look like this:
 deployment xmlns=http://xml.apache.org/axis/wsdd/;
 xmlns:java=http://xml.apache.org/axis/wsdd/providers/java;
 service   name=iTrapService   provider=java:RPC 
 parameter name=className value=iTrapAPI/
 parameter name=scope value=session/
 parameter name=allowedMethods value=*/
 /service
 /deployment

 --
 View this message in context:
 http://www.nabble.com/XML-Encoding-tf2969336.html#a8309121
 Sent from the Axis - User mailing list archive at Nabble.com.


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


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

-- 
View this message in context: 
http://www.nabble.com/XML-Encoding-tf2969336.html#a8359556
Sent from the Axis - User mailing list archive at Nabble.com.


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



WSDL2Java Logger

2006-05-31 Thread herbison

I’m running the WSDL2Java app under Axis 1.2 and I get the following error:

java.io.IOException: Type {http://log4j.apache.org}Logger 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)
at java.lang.Thread.run(Thread.java:595)

What is it trying to tell me? Is there a log4j variable it is trying to
deference but can’t?

--
View this message in context: 
http://www.nabble.com/WSDL2Java+Logger-t1712915.html#a4651214
Sent from the Axis - User forum at Nabble.com.


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



Axis and WSDL:types

2006-05-31 Thread herbison

When axis creates a WSDL why does it place the import namespace
http://log4j.apache.org in the wsdl:types section?

- wsdl:types
- schema
targetNamespace=http://coi.us.nortel.com:8087/axis/services/CoiDWJobSchedulerAPI;
xmlns=http://www.w3.org/2001/XMLSchema;
  import namespace=http://log4j.apache.org; / 
  import namespace=http://xml.apache.org/xml-soap; / 
  import namespace=http://schemas.xmlsoap.org/soap/encoding/; / 
- complexType name=ArrayOf_xsd_string
- complexContent
- restriction base=soapenc:Array
  attribute ref=soapenc:arrayType wsdl:arrayType=xsd:string[] / 
  /restriction
  /complexContent
  /complexType
  /schema
- schema targetNamespace=http://xml.apache.org/xml-soap;
xmlns=http://www.w3.org/2001/XMLSchema;
  import namespace=http://log4j.apache.org; / 
  import
namespace=http://coi.us.nortel.com:8087/axis/services/CoiDWJobSchedulerAPI;
/ 
  import namespace=http://schemas.xmlsoap.org/soap/encoding/; / 
- complexType name=mapItem
- sequence
  element name=key nillable=true type=xsd:anyType / 
  element name=value nillable=true type=xsd:anyType / 
  /sequence
  /complexType
- complexType name=Map
- sequence
  element maxOccurs=unbounded minOccurs=0 name=item
type=apachesoap:mapItem / 
  /sequence
  /complexType
  /schema
  /wsdl:types
--
View this message in context: 
http://www.nabble.com/Axis+and+WSDL%3Atypes-t1713370.html#a4652625
Sent from the Axis - User forum at Nabble.com.


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