Re: Problems when calling getOMElement

2009-11-23 Thread Håkon Sagehaug
Hi

I now tried with axiom 1.2.9-SNAPSHOT and axis2 1.5.1 release, but the
problem is the same. My code looks like this

OMElement omResp = resp.getGetResultResponse().getOMElement(
GetResultResponse.MY_QNAME,
OMAbstractFactory.getOMFactory());

guess the standard way of getting the OM element. Any other int on how to
solve this?

cheers, Håkon

2009/11/21 Håkon Sagehaug hakon.sageh...@bccs.uib.no

 Hi

 I'll try on monday, thanks for the help


 cheers, Hakon

 2009/11/20 Andreas Veithen andreas.veit...@gmail.com

 Can you test this with a snapshot version?

 Andreas

 2009/11/20 Håkon Sagehaug hakon.sageh...@bccs.uib.no:
  hi
 
  The problem is occurs using 1.4 and axiom 1.2.8. I can extract the
 values
  using the java objects, but when I use the #getOmElement() I get the
 just
  the XML without values, so my thought was the serialization or something
  like this.
 
  cheers, Hakon
 
  2009/11/20 Andreas Veithen andreas.veit...@gmail.com
 
  Does this problem occur with snapshot versions of Axis2 and Axiom?
 
  Andreas
 
  On Fri, Nov 20, 2009 at 16:11, Amila Suriarachchi
  amilasuriarach...@gmail.com wrote:
   here is a sample code
  
   InDict inDict = new InDict();
   ArrayOfKeyValueOfstringstring arrayOfKeyValueOfstringstring =
   new
   ArrayOfKeyValueOfstringstring();
   inDict.setInDict(arrayOfKeyValueOfstringstring);
  
   KeyValueOfstringstring_type0[] keyValueOfstringstring_type0 =
   new
   KeyValueOfstringstring_type0[1];
   keyValueOfstringstring_type0[0] = new
   KeyValueOfstringstring_type0();
   keyValueOfstringstring_type0[0].setKey(One Element Array);
   keyValueOfstringstring_type0[0].setValue(One Element
 Array);
  
  
  
  
 arrayOfKeyValueOfstringstring.setKeyValueOfstringstring(keyValueOfstringstring_type0);
  
   try {
   OMElement omElement =
 inDict.getOMElement(InDict.MY_QNAME,
   OMAbstractFactory.getOMFactory());
   System.out.println(OMElement ==  +
 omElement.toString());
   } catch (ADBException e) {
   e.printStackTrace();
   }
  
   thanks,
   Amila.
  
   On Fri, Nov 20, 2009 at 3:14 AM, Andreas Veithen
   andreas.veit...@gmail.com
   wrote:
  
   Håkon,
  
   I think you need to give a bit more context. What version of Axis2?
   What version of Axiom? Code snippet showing what you are trying to
 do,
   etc.
  
   Andreas
  
   2009/11/19 Håkon Sagehaug hakon.sageh...@bccs.uib.no:
Hi
   
Anybody did this, go from adb object through a xslt transfomation?
   
Or having problem getting values out from a XML message when the
 tyep
attribute is used for the data type of the element.
   
cheers, Håkon
   
2009/11/18 Håkon Sagehaug hakon.sageh...@bccs.uib.no
   
Hi
   
To provide more information, we want to do xslt transformation to
our
generated client side object. And  as far as I know we need the
OmElement of
the generated type to do so, but when this don't give back the
values
just
the XML with no values, there is not much to transform. So we
 need a
hint on
how this can be done.
   
   
   
cheers, håkon
   
2009/11/18 Håkon Sagehaug hakon.sageh...@bccs.uib.no
   
Hi all,
   
Any tips on this. stange if it won't work?
   
2009/11/17 Håkon Sagehaug hakon.sageh...@bccs.uib.no
   
Hi all,
   
I've got a client that calls a ws and using adb as the
databinding(client side), then we want to get a string
representation
of the
obejct.  We execute object.getOMElement(), the method returns
 only
the xml
element and not the actual value inside the element. So this
element
here
   
   ns2:BlastOutput_program xsi:type=ns2:BlastOutput_
programblastp/ns2:BlastOutput_program
   
Would returns this string
   
ns2:BlastOutput_program/ns2:BlastOutput_program
   
We where wondering if it had anything to to with the xsi:type
attribute?
Any tips on how to solve this, or another way of getting a
 string
representatioon of the object using adb as the databinding?
   
cheers, Håkon
   
--
Håkon Sagehaug, Scientific Programmer
Parallab, Bergen Center for Computational Science (BCCS)
UNIFOB AS (University of Bergen Research Company)
hakon.sageh...@bccs.uib.no, phone +47 55584125
   
   
   
--
Håkon Sagehaug, Scientific Programmer
Parallab, Bergen Center for Computational Science (BCCS)
UNIFOB AS (University of Bergen Research Company)
hakon.sageh...@bccs.uib.no, phone +47 55584125
   
   
   
--
Håkon Sagehaug, Scientific Programmer
Parallab, Bergen Center for Computational Science (BCCS)
UNIFOB AS (University of Bergen Research Company)
hakon.sageh...@bccs.uib.no, phone +47 55584125
   
   
   
--
Håkon Sagehaug, Scientific Programmer
Parallab, Bergen Center for Computational Science (BCCS)
UNIFOB AS (University 

AUTO: Dave Parsons is out of the office. (returning 30/11/2009)

2009-11-23 Thread David Parsons1

I am out of the office until 30/11/2009.

I will respond to your message when I return.

Speak to Sara Mitchell if you have any technical or project related WSRM
issues.
For UDDI issues speak to Mark Lewis.
Anything else speak to my manager Hilora Munro.

Cheers,

Dave


Note: This is an automated response to your message  Re: Problem running
axis2-wsdl2code-maven-plugin sent on 17/11/09 16:03:25.

This is the only notification you will receive while this person is away.



RE: Consuming a Service that takes AnyType

2009-11-23 Thread Meenakshisundaram, Pattabiraman

Thank you. It is worki9ng when I use the ServiceClient.
Thanks


From: McCoy, Daniel (HTSC) [mailto:daniel.mc...@htsco.com]
Sent: Friday, November 20, 2009 4:05 PM
To: axis-user@ws.apache.org
Subject: RE: Consuming a Service that takes AnyType

Convert your request string to an OMElement. Let axis handle the OMElement 
instead of the string.


String XMLRequest = 
soapEnvelope+soapBody+lookRequestDoc.xmlText()+soapBodyClose+soapEnvClose;

OMElement elem = AXIOMUtil.stringToOM(XMLRequest);


Dan McCoy
Architect
Office of the CTO
8 Farms Springs
Farmington, CT 06032
(860) 409-8170
daniel.mc...@thehartford.commailto:daniel.mc...@thehartford.com



From: Meenakshisundaram, Pattabiraman 
[mailto:pattabiraman.meenakshisunda...@chartisinsurance.com]
Sent: Friday, November 20, 2009 3:56 PM
To: axis-user@ws.apache.org
Subject: Consuming a Service that takes AnyType

Hi,
I am using the Stub generated by WSDL2Java for a Service that takes AnyType.
The Service is expecting a Xml content ( Not a String/escaped). When I invoke 
the service through XmlSpy, it works. I used TCP Monitor to see the content 
transferred and I see that the tags are not escaped.
Do not know how to do the same thing with the Generated Client. I am passing it 
as a String. It is not working. Moreover, I notice that only the '' is 
escaped. The  goes unescaped.

Could anyone help me resolve this.

Thanks




This communication, including attachments, is for the exclusive use of 
addressee and may contain proprietary, confidential and/or privileged 
information.  If you are not the intended recipient, any use, copying, 
disclosure, dissemination or distribution is strictly prohibited.  If you are 
not the intended recipient, please notify the sender immediately by return 
e-mail, delete this communication and destroy all copies.




'Binary data detected' problem

2009-11-23 Thread Vaclav Balak
Hi,
  I'm trying to get binary data in response like this:

DataSource fileContent = getFileContent();
DataHandler dataHandler = new DataHandler(fileContent);
response.setFile(dataHandler);

and in my DataSource implementation I'm just returning InputStream
(simplified ;-)):

public InputStream getInputStream() throws IOException {
return getUrlContent(url);  // this doesnt work
// return new ByteArrayInputStream(short
text.getBytes(UTF-8));// this works
}

getUrlContent works - it returns content of specified url. When I try
to return just short text, everything works ok. but when I try to send
something bigger, I get following error message:

Binary data detected! Click 'DOWNLOAD BINARY FILE NOW' button to download file.
WARNING
===
Be careful what you download. If the file contains a virus, you will
infect your machine!!
HIT 'BACK' when done.



How can I handle with this?

Thanks in advance, Vaclav Balak


Re: WS works in Axis 2 1.3 and 1.4.1 but has timeout in Axis 1.5.1?

2009-11-23 Thread pwillemann

Thank you for your answer, however it does not seem to work..  I get the same
error as before:
Here is a code snippet which implemented the suggested solution.

public GetAOIResponse getAOI(GetAOI request) throws SSBException {
GetAOIResponse response = new GetAOIResponse();
try {
response = cistub.getAOI(request);
cistub._getServiceClient().cleanupTransport();   // 
Axis 2 V1.5.1
} catch (AxisFault af) {
logger.error(Error with the local webservice, af);
af.printStackTrace();
} catch (RemoteException re) {
logger.error(Cannot connect to local webservice, re);
re.printStackTrace();
} catch (SSBException e) {
e.printStackTrace();
}
return response;
}

This method will be called many times during its lifetime and I reuse
cistub.  Is that a problem?   I would like to avoid instantiating a new stub
everytime if possible.

Thanks for any help or suggestions

Phil Willemann


Amila Suriarachchi wrote:
 
 On Fri, Nov 13, 2009 at 11:02 PM, pwillemann
 philwillem...@yahoo.comwrote:
 

 I used WSDL2Java to create all my Web service classes.  I do not have any
 custom code.  Everything in my project is autogenerated.  My web service
 works fine in Axis 2 version 1.3 and Axis 2 version 1.4.1.  When I
 migrated
 to 1.5.1 I get timeouts.  Specifically the error says:

 HTTPSender.sendViaPost INFO - Unable to sendViaPost to
 url[http://127.0.0.1:8080/mywebservice/]
 org.apache.commons.httpclient.ConnectionPoolTimeoutException:  Timeout
 waiting for connection.

 I looked to see if there was a migration guide from 1.3/1.4 to 1.5 that
 addresses this issue, however I have been unable to find one.  This web
 service has worked for almost a year, but I am curious if the new version
 of
 Axis has revealed some sort of flaw or if there is an actual problem in
 1.5.1.

 Has anyone had a similar problem or has anyone solved this problem? Any
 help
 would be appreciated very much.  Thanks!

 
 call stub._getServiceClient().cleanupTransport();
 after service invocation.
 
 thanks,
 Amila.
 

 Sincerely yours
 Phil Willemann

 --
 View this message in context:
 http://old.nabble.com/WS-works-in-Axis-2-1.3-and-1.4.1-but-has-timeout-in-Axis-1.5.1--tp26340326p26340326.html
 Sent from the Axis - User mailing list archive at Nabble.com.


 
 
 -- 
 Amila Suriarachchi
 WSO2 Inc.
 blog: http://amilachinthaka.blogspot.com/
 
 

-- 
View this message in context: 
http://old.nabble.com/WS-works-in-Axis-2-1.3-and-1.4.1-but-has-timeout-in-Axis-1.5.1--tp26340326p26479852.html
Sent from the Axis - User mailing list archive at Nabble.com.



Steps to publish existing Wep App code as service

2009-11-23 Thread vandana ahuja

Hi,

I’ve an existing Web App running on WAS7 and was publishing few services using 
WebMethods Glue.Now I want to switch to Axis2.
Can somebody please guide me what is step by step procedure for that.

Most of the articles I found on net were simply publishing axis war on server. 
I don’t want that, but publish my own code.
What I’ve tried so far is:
1)   Copying Axis web.xml servlet and Servlet mapping  in my web.xml
2)   Copying Axis jar files in my Web app lib
3)   Created Service.xml for my services. That’s attached here.
4)   Created following hierarchy:
Web Inf
    -conf
    -axis.xml
    -services
    -service.xml
    -modules
    -module.list
    -SOAPMonitor.mar

And while trying to startup app I got following error.
java.lang.ClassNotFoundException: 
org.apache.commons.fileupload.FileUploadException


Can somebody help me please.

Thanks
Vandana 



**
serviceGroup
 service name=AutomatedDataMaintenanceServices
 scope=application
  description
   OrgHierarchy Automated Data Maintenance Services
  /description
    messageReceivers
 messageReceiver 
 mep=http://www.w3.org/2004/08/wsdl/in-only;
        class=org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver/
 messageReceiver
 mep=http://www.w3.org/2004/08/wsdl/in-out;
        class=org.apache.axis2.rpc.receivers.RPCMessageReceiver/
 /messageReceivers
    parameter name=ServiceClass 
locked=falsecom.avnet.ohm.service.glue.AutomatedDataMaintenanceServicesImpl/parameter
 /service
 service name=RealTimeServices
 scope=application
  description
   OrgHierarchy Real-Time Services
  /description
    messageReceivers
 messageReceiver 
 mep=http://www.w3.org/2004/08/wsdl/in-only;
        class=org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver/
 messageReceiver
 mep=http://www.w3.org/2004/08/wsdl/in-out;
        class=org.apache.axis2.rpc.receivers.RPCMessageReceiver/
 /messageReceivers
    parameter name=ServiceClass 
locked=falsecom.avnet.ohm.service.glue.RealTimeServicesImpl/parameter
 /service
/serviceGroup

*



      The INTERNET now has a personality. YOURS! See your Yahoo! Homepage. 
http://in.yahoo.com/



  The INTERNET now has a personality. YOURS! See your Yahoo! Homepage. 
http://in.yahoo.com/


ClassCastException when calling Axis WebService method

2009-11-23 Thread pcsantos

Hi

I have an Axis (1.4.2) web service and a tomcat 4 server.
From time to time, when calling the web method, an exception occurs as
follows:

method public java.lang.String[]
MyClass.UPDATE(java.lang.String[],java.lang.String[]) with arguments
[Ljava.lang.String;,[Ljava.lang.String;.  The arguments do not match the
signature.
java.lang.IllegalArgumentException: java.lang.classcastexcept...@b5b09d

Can anyone give me a hint on this? 
I believe java.lang.String[] and [Ljava.lang.String are equivalent (and the
parameters being passed are of correct type String[]).. So, how can the
above error be happening since the argument types and those stated in the
call are the exact same?! 
And mostly, why does this error only happens from time to time? After a
restart to the server I no longer get this exception.. til next time.

Thanks in advance

-- 
View this message in context: 
http://old.nabble.com/ClassCastException-when-calling-Axis-WebService-method-tp26483330p26483330.html
Sent from the Axis - User mailing list archive at Nabble.com.



Future of JMS in Axis2?

2009-11-23 Thread tom . damon

Could somebody please clarify future plans for JMS support in Axis2? My
understanding is that Sandesha is the future direction for this function,
but I'm unclear if this refers only to the Axis2 server, or both server and
client. I'm particularly interested in using the Axis2 client standard to
invoke both JMS and HTTP services in  our SOA infrastructure.



Re: Trouble upgrading Maven pom from Axis2 1.4.1 to 1.5.1

2009-11-23 Thread Glen Mazza

Figured it out.  The POM under Step #4 here has been updated to use Axis2
1.5.1, with either JAXB or ADB databinding: 
http://www.jroller.com/gmazza/entry/soap_client_with_axis2

Glen


Glen Mazza wrote:
 
 No response yet.  Has anyone been able to run axis2-wsdl2code-maven-plugin
 with Axis 1.5.1?  I need to know how to upgrade my Axis2 1.4.1 pom.xml
 below to work with it.
 
 Thanks,
 Glen
 
 
 Glen Mazza wrote:
 
 Hello, the pom.xml for the Axis2 SOAP client below works fine with
 axis2.version property set to 1.4.1:
 http://www.jroller.com/gmazza/entry/soap_client_with_axis2 
 (pom is under Step #4)
 
 I'm having trouble, however, upgrading it to either Axis2 1.5 or 1.5.1. 
 When I try axis2.version = 1.5.1, and run mvn clean install, I get the
 following error:
 
 [INFO] Internal error in the plugin manager executing goal
 'org.apache.axis2:axi
 s2-wsdl2code-maven-plugin:1.5.1:wsdl2code': Unable to load the mojo
 'org.apache.
 axis2:axis2-wsdl2code-maven-plugin:1.5.1:wsdl2code' in the plugin
 'org.apache.ax
 is2:axis2-wsdl2code-maven-plugin'. A required class is missing:
 org/apache/axis2
 /wsdl/codegen/CodeGenerationException
 org.apache.axis2.wsdl.codegen.CodeGenerationException
 
 Earlier in the Maven output I get other errors such as these:
 
 C:\research\zipcodemvn install
 [INFO] Scanning for projects...
 [INFO]
 
 [INFO] Building Sample SOAP Client
 [INFO]task-segment: [install]
 [INFO]
 
 [WARNING] POM for 'org.apache.axis2:axis2-jaxbri:pom:1.5.1:compile' is
 invalid.
 
 Its dependencies (if any) will NOT be available to the current build.
 [WARNING] POM for 'org.apache.axis2:axis2-codegen:pom:1.5.1:runtime' is
 invalid.
 
 
 Its dependencies (if any) will NOT be available to the current build.
 [WARNING] POM for 'org.apache.axis2:axis2-kernel:pom:1.5.1:runtime' is
 invalid.
 
 Its dependencies (if any) will NOT be available to the current build.
 [WARNING] POM for 'org.apache.axis2:axis2-adb:pom:1.5.1:runtime' is
 invalid.
 
 Its dependencies (if any) will NOT be available to the current build.
 [WARNING] POM for 'org.apache.axis2:axis2-adb-codegen:pom:1.5.1:runtime'
 is inva
 lid.
 
 Its dependencies (if any) will NOT be available to the current build.
 [WARNING] POM for 'org.apache.axis2:axis2-java2wsdl:pom:1.5.1:runtime' is
 invali
 d.
 
 ...
 
 Any clue what the problem might be?
 
 Thanks,
 Glen
 
 
 

-- 
View this message in context: 
http://old.nabble.com/Trouble-upgrading-Maven-pom-from-Axis2-1.4.1-to-1.5.1-tp26402018p26485727.html
Sent from the Axis - User mailing list archive at Nabble.com.



Axis 1 and ws-policy

2009-11-23 Thread Wishing Carebear
Hello:
I have a snippet of wsdl as shown below. Does Axis 1(1.4.1) supports that.
Please look into the attached wsdl for more details...

Thanks,
cabear

wsdl:definitions name=BusinessCardService
 targetNamespace=http://tempuri.org/; xmlns:wsdl=
http://schemas.xmlsoap.org/wsdl/;
 xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/;
 xmlns:wsu=
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd

 xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/; xmlns:wsam=
http://www.w3.org/2007/05/addressing/metadata;
 xmlns:tns=http://tempuri.org/; xmlns:wsa=
http://schemas.xmlsoap.org/ws/2004/08/addressing;
 xmlns:wsp=http://schemas.xmlsoap.org/ws/2004/09/policy; xmlns:wsap=
http://schemas.xmlsoap.org/ws/2004/08/addressing/policy;
 xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:msc=
http://schemas.microsoft.com/ws/2005/12/wsdl/contract;
 xmlns:wsaw=http://www.w3.org/2006/05/addressing/wsdl; xmlns:soap12=
http://schemas.xmlsoap.org/wsdl/soap12/;
 xmlns:wsa10=http://www.w3.org/2005/08/addressing; xmlns:wsx=
http://schemas.xmlsoap.org/ws/2004/09/mex;
 wsp:Policy wsu:Id=WSHttpBinding_IBusinessCard_policy
  wsp:ExactlyOne
   wsp:All
sp:SymmetricBinding
 xmlns:sp=http://schemas.xmlsoap.org/ws/2005/07/securitypolicy;
 wsp:Policy
  sp:ProtectionToken
   wsp:Policy
sp:SecureConversationToken
 sp:IncludeToken=
http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysToRecipient

 wsp:Policy
  sp:RequireDerivedKeys /
  sp:BootstrapPolicy
   wsp:Policy
sp:SignedParts
 sp:Body /
 sp:Header Name=To
  Namespace=http://www.w3.org/2005/08/addressing; /
 sp:Header Name=From
  Namespace=http://www.w3.org/2005/08/addressing; /
 sp:Header Name=FaultTo
  Namespace=http://www.w3.org/2005/08/addressing; /
 sp:Header Name=ReplyTo
  Namespace=http://www.w3.org/2005/08/addressing; /
 sp:Header Name=MessageID
  Namespace=http://www.w3.org/2005/08/addressing; /
 sp:Header Name=RelatesTo
  Namespace=http://www.w3.org/2005/08/addressing; /
 sp:Header Name=Action
  Namespace=http://www.w3.org/2005/08/addressing; /
/sp:SignedParts
?xml version=1.0 encoding=utf-8?
wsdl:definitions name=BusinessCardService
	targetNamespace=http://tempuri.org/; xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/;
	xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/;
	xmlns:wsu=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd;
	xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/; xmlns:wsam=http://www.w3.org/2007/05/addressing/metadata;
	xmlns:tns=http://tempuri.org/; xmlns:wsa=http://schemas.xmlsoap.org/ws/2004/08/addressing;
	xmlns:wsp=http://schemas.xmlsoap.org/ws/2004/09/policy; xmlns:wsap=http://schemas.xmlsoap.org/ws/2004/08/addressing/policy;
	xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:msc=http://schemas.microsoft.com/ws/2005/12/wsdl/contract;
	xmlns:wsaw=http://www.w3.org/2006/05/addressing/wsdl; xmlns:soap12=http://schemas.xmlsoap.org/wsdl/soap12/;
	xmlns:wsa10=http://www.w3.org/2005/08/addressing; xmlns:wsx=http://schemas.xmlsoap.org/ws/2004/09/mex;
	wsp:Policy wsu:Id=WSHttpBinding_IBusinessCard_policy
		wsp:ExactlyOne
			wsp:All
sp:SymmetricBinding
	xmlns:sp=http://schemas.xmlsoap.org/ws/2005/07/securitypolicy;
	wsp:Policy
		sp:ProtectionToken
			wsp:Policy
sp:SecureConversationToken
	sp:IncludeToken=http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysToRecipient;
	wsp:Policy
		sp:RequireDerivedKeys /
		sp:BootstrapPolicy
			wsp:Policy
sp:SignedParts
	sp:Body /
	sp:Header Name=To
		Namespace=http://www.w3.org/2005/08/addressing; /
	sp:Header Name=From
		Namespace=http://www.w3.org/2005/08/addressing; /
	sp:Header Name=FaultTo
		Namespace=http://www.w3.org/2005/08/addressing; /
	sp:Header Name=ReplyTo
		Namespace=http://www.w3.org/2005/08/addressing; /
	sp:Header Name=MessageID
		Namespace=http://www.w3.org/2005/08/addressing; /
	sp:Header Name=RelatesTo
		Namespace=http://www.w3.org/2005/08/addressing; /
	sp:Header Name=Action
		Namespace=http://www.w3.org/2005/08/addressing; /
/sp:SignedParts
sp:EncryptedParts
	sp:Body /
/sp:EncryptedParts
sp:SymmetricBinding
	wsp:Policy
		sp:ProtectionToken
			wsp:Policy
sp:SpnegoContextToken
	sp:IncludeToken=http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysToRecipient;
	wsp:Policy
		sp:RequireDerivedKeys /

RE: deploying Axis under WebLogic

2009-11-23 Thread Vance
I was able to get Axis version 1.4 deployed under WebLogic 10.3, but not 
version 1.5.
 
But with version 1.4, there's nothing listed under 'Web Services'.
 

--- On Fri, 11/20/09, McCoy, Daniel (HTSC) daniel.mc...@htsco.com wrote:


From: McCoy, Daniel (HTSC) daniel.mc...@htsco.com
Subject: RE: deploying Axis under WebLogic
To: axis-user@ws.apache.org
Date: Friday, November 20, 2009, 6:38 PM



Check this link out. Pretty comprehensive.
 
http://charithaka.blogspot.com/2008/07/how-to-deploy-apache-axis2-on-weblogic.html
 

Dan McCoy
Architect
Office of the CTO
8 Farms Springs
Farmington, CT 06032
(860) 409-8170
daniel.mc...@thehartford.com
 



From: Vance [mailto:aroc...@yahoo.com] 
Sent: Friday, November 20, 2009 6:35 PM
To: axis-user@ws.apache.org
Subject: deploying Axis under WebLogic







Is there documentation somewhere describing how to deploy Axis (1.x) under 
WebLogic 10 ?

This communication, including attachments, is for the exclusive use of 
addressee and may contain proprietary, confidential and/or privileged 
information.  If you are not the intended recipient, any use, copying, 
disclosure, dissemination or distribution is strictly prohibited.  If you are 
not the intended recipient, please notify the sender immediately by return 
e-mail, delete this communication and destroy all copies.




  

ReadWriteLock error with a secure WS

2009-11-23 Thread Julien Sentier
Hi,

I'm trying to create a secure Web Service. By chance, my goal is described by:
http://www.ibm.com/developerworks/java/library/j-jws4/
and
http://www.ibm.com/developerworks/java/library/j-jws7.html

Currently, I'm just following the first how-to: 
http://www.ibm.com/developerworks/java/library/j-jws4/

I've setup apache-tomcat-6.0.20 with axis2-1.5.1 with rahas-1.4.mar and 
rampart-1.4.mar modules.

I've compiled the example provided in the how-to but when I run the client I 
have the following error:
run:
 [java] Connecting to http://localhost:8080/axis2/services/library-username
 [java] Exception in thread main org.apache.axis2.AxisFault: 
java.lang.NoClassDefFoundError: 
edu/emory/mathcs/backport/java/util/concurrent/locks/ReadWriteLock
 [java] at 
org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:435)
 [java] at 
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:371)
 [java] at 
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:417)
 [java] at 
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
 [java] at 
org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
 [java] at 
com.sosnoski.ws.library.adb.LibraryUsernameStub.getBook(LibraryUsernameStub.java:205)
 [java] at 
com.sosnoski.ws.library.adb.WebServiceClient.main(WebServiceClient.java:82)
 [java] Java Result: 1

I've never seen this error and it seems that Google neither. 

Do you see what's wrong? If not, could you indicate me another how-to which 
works?

Regards,
Julien


  


Re: Axis 1 and ws-policy

2009-11-23 Thread Wishing Carebear
Could someone give some pointers.

Thanks,
cabear

On Mon, Nov 23, 2009 at 2:09 PM, Wishing Carebear 
wishing.careb...@gmail.com wrote:

 Hello:
 I have a snippet of wsdl as shown below. Does Axis 1(1.4.1) supports that.
 Please look into the attached wsdl for more details...

 Thanks,
 cabear

 wsdl:definitions name=BusinessCardService
  targetNamespace=http://tempuri.org/; xmlns:wsdl=
 http://schemas.xmlsoap.org/wsdl/;
  xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/;
  xmlns:wsu=
 http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd
 
  xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/; xmlns:wsam=
 http://www.w3.org/2007/05/addressing/metadata;
  xmlns:tns=http://tempuri.org/; xmlns:wsa=
 http://schemas.xmlsoap.org/ws/2004/08/addressing;
  xmlns:wsp=http://schemas.xmlsoap.org/ws/2004/09/policy; xmlns:wsap=
 http://schemas.xmlsoap.org/ws/2004/08/addressing/policy;
  xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:msc=
 http://schemas.microsoft.com/ws/2005/12/wsdl/contract;
  xmlns:wsaw=http://www.w3.org/2006/05/addressing/wsdl; xmlns:soap12=
 http://schemas.xmlsoap.org/wsdl/soap12/;
  xmlns:wsa10=http://www.w3.org/2005/08/addressing; xmlns:wsx=
 http://schemas.xmlsoap.org/ws/2004/09/mex;
  wsp:Policy wsu:Id=WSHttpBinding_IBusinessCard_policy
   wsp:ExactlyOne
wsp:All
 sp:SymmetricBinding
  xmlns:sp=http://schemas.xmlsoap.org/ws/2005/07/securitypolicy;
  wsp:Policy
   sp:ProtectionToken
wsp:Policy
 sp:SecureConversationToken
  sp:IncludeToken=
 http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysToRecipient
 
  wsp:Policy
   sp:RequireDerivedKeys /
   sp:BootstrapPolicy
wsp:Policy
 sp:SignedParts
  sp:Body /
  sp:Header Name=To
   Namespace=http://www.w3.org/2005/08/addressing; /
  sp:Header Name=From
   Namespace=http://www.w3.org/2005/08/addressing; /
  sp:Header Name=FaultTo
   Namespace=http://www.w3.org/2005/08/addressing; /
  sp:Header Name=ReplyTo
   Namespace=http://www.w3.org/2005/08/addressing; /
  sp:Header Name=MessageID
   Namespace=http://www.w3.org/2005/08/addressing; /
  sp:Header Name=RelatesTo
   Namespace=http://www.w3.org/2005/08/addressing; /
  sp:Header Name=Action
   Namespace=http://www.w3.org/2005/08/addressing; /
 /sp:SignedParts



JAXB integrating with AXIS2 - oader constraints violated when linking javax/xml/namespace/QName class

2009-11-23 Thread wazup80

Hi,

I'm new to webservices, and axis2 and I've been stuck on this for a while
and can't seem to fix this issue.  There are alot on the net on this topic,
but I have looked at everything and seem to have no luck.  I'm hoping
someone can help me on this.  

I'm running jboss5.0.0 with Axis2.1.4 and using JAXB and jdk1.5.21.  I have
a webservice that will gather info, and then call another webservice.  I'm
able to call the other webservice and get the data, but now i'm trying to
parse the data.  This is where it fails and where i'm using JAXB.  

I have everything compiled and in the jar file (xxx.aar file).  That
includes the services.xml file and the jaxb generated classes.

Here is where it's failing at:

JAXBContext jc = JAXBContext.newInstance(my.package.name);

my.package.name is the package that contains the JAXB classes generated from
the schema.  When i run this, i get my.package.name doesnt contain
ObjectFactory.class or jaxb.index. 

I read everywhere that it's a classloader issue, so I went ahead and tried
the following:

ClassLoader cl = my.package.name.ObjectFactory.class.getClassLoader();
JAXBContext jc = JAXBContext.newInstance(my.package.name, cl);

That gave me loader constraints violated when linking
javax/xml/namespace/QName class

I went ahead and removed my.package.name package from the jar file under
services and put it in axis2.war\WEB-INF\lib and used the
JAXBContext.newInstance(my.package.name) and this time I only got loader
constraints violated when linking javax/xml/namespace/QName class

I tried removing some of the jars that were in axis2/web-inf/lib directory
that contained the namespace/QName class and that didn't do anything.  Some
of the jars were:

axis2-saaj-api-1.4.1.jar
stax-api.jar from (jboss\lib\endorsed).

I've tried other things as well but I figured this email is long enough as
is.  In either case, I always get the loader constraint error.

One last thing to mention.  I have the same code tested in eclipse and it
works fine.  What I did was I loaded all the jar files that were needed from
axis2\lib and it worked fine.  What was interesting was I noticed that my
sdk contained rt.jar which contained the Qname class.  I wanted to see if my
eclipse was using this version of the class or if it was using it from the
axis2\lib jars.  So I removed the namespace package from the rt.jar and it
didn't work, even though I had the two jars stated above in my java build
path.  Not sure if this testing helps at all, but just wanted to point it
out.

Any help would be appreciated.

Thanks.






-- 
View this message in context: 
http://old.nabble.com/JAXB-integrating-with-AXIS2---oader-constraints-violated-when-linking-javax-xml-namespace-QName-class-tp26489184p26489184.html
Sent from the Axis - User mailing list archive at Nabble.com.



Re: ReadWriteLock error with a secure WS

2009-11-23 Thread Prabath Siriwardena

Hi Julien;

This [1] may be helpful.

Thanks  regards.
-Prabath

[1]:http://blog.rampartfaq.com/2009/11/exception-in-thread-main.html

Julien Sentier wrote:

Hi,

I'm trying to create a secure Web Service. By chance, my goal is described by:
http://www.ibm.com/developerworks/java/library/j-jws4/
and
http://www.ibm.com/developerworks/java/library/j-jws7.html

Currently, I'm just following the first how-to: 
http://www.ibm.com/developerworks/java/library/j-jws4/

I've setup apache-tomcat-6.0.20 with axis2-1.5.1 with rahas-1.4.mar and 
rampart-1.4.mar modules.

I've compiled the example provided in the how-to but when I run the client I 
have the following error:
run:
 [java] Connecting to http://localhost:8080/axis2/services/library-username
 [java] Exception in thread main org.apache.axis2.AxisFault: 
java.lang.NoClassDefFoundError: 
edu/emory/mathcs/backport/java/util/concurrent/locks/ReadWriteLock
 [java] at 
org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:435)
 [java] at 
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:371)
 [java] at 
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:417)
 [java] at 
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
 [java] at 
org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
 [java] at 
com.sosnoski.ws.library.adb.LibraryUsernameStub.getBook(LibraryUsernameStub.java:205)
 [java] at 
com.sosnoski.ws.library.adb.WebServiceClient.main(WebServiceClient.java:82)
 [java] Java Result: 1

I've never seen this error and it seems that Google neither. 


Do you see what's wrong? If not, could you indicate me another how-to which 
works?

Regards,
Julien


  

  




Re: Future of JMS in Axis2?

2009-11-23 Thread Amila Suriarachchi
On Tue, Nov 24, 2009 at 12:24 AM, tom.da...@macys.com wrote:


 Could somebody please clarify future plans for JMS support in Axis2?


Now JMS transport is in the new commons/transport project of which 1.0 will
be released soon.

thanks,
Amila.

 My
 understanding is that Sandesha is the future direction for this function,
 but I'm unclear if this refers only to the Axis2 server, or both server and
 client. I'm particularly interested in using the Axis2 client standard to
 invoke both JMS and HTTP services in  our SOA infrastructure.




-- 
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/


Re: WS works in Axis 2 1.3 and 1.4.1 but has timeout in Axis 1.5.1?

2009-11-23 Thread Amila Suriarachchi
On Mon, Nov 23, 2009 at 8:46 PM, pwillemann philwillem...@yahoo.com wrote:


 Thank you for your answer, however it does not seem to work..  I get the
 same
 error as before:
 Here is a code snippet which implemented the suggested solution.

 public GetAOIResponse getAOI(GetAOI request) throws SSBException {
GetAOIResponse response = new GetAOIResponse();
try {
response = cistub.getAOI(request);
cistub._getServiceClient().cleanupTransport();   //
 Axis 2 V1.5.1
} catch (AxisFault af) {
logger.error(Error with the local webservice, af);
af.printStackTrace();
} catch (RemoteException re) {
logger.error(Cannot connect to local webservice,
 re);
re.printStackTrace();
} catch (SSBException e) {
e.printStackTrace();
}
return response;
}

 This method will be called many times during its lifetime and I reuse
 cistub.  Is that a problem?   I would like to avoid instantiating a new
 stub
 everytime if possible.


Can you check with Axis2 1.5?

thanks,
Amila.


 Thanks for any help or suggestions

 Phil Willemann


 Amila Suriarachchi wrote:
 
  On Fri, Nov 13, 2009 at 11:02 PM, pwillemann
  philwillem...@yahoo.comwrote:
 
 
  I used WSDL2Java to create all my Web service classes.  I do not have
 any
  custom code.  Everything in my project is autogenerated.  My web service
  works fine in Axis 2 version 1.3 and Axis 2 version 1.4.1.  When I
  migrated
  to 1.5.1 I get timeouts.  Specifically the error says:
 
  HTTPSender.sendViaPost INFO - Unable to sendViaPost to
  url[http://127.0.0.1:8080/mywebservice/]
  org.apache.commons.httpclient.ConnectionPoolTimeoutException:  Timeout
  waiting for connection.
 
  I looked to see if there was a migration guide from 1.3/1.4 to 1.5 that
  addresses this issue, however I have been unable to find one.  This web
  service has worked for almost a year, but I am curious if the new
 version
  of
  Axis has revealed some sort of flaw or if there is an actual problem in
  1.5.1.
 
  Has anyone had a similar problem or has anyone solved this problem? Any
  help
  would be appreciated very much.  Thanks!
 
 
  call stub._getServiceClient().cleanupTransport();
  after service invocation.
 
  thanks,
  Amila.
 
 
  Sincerely yours
  Phil Willemann
 
  --
  View this message in context:
 
 http://old.nabble.com/WS-works-in-Axis-2-1.3-and-1.4.1-but-has-timeout-in-Axis-1.5.1--tp26340326p26340326.html
  Sent from the Axis - User mailing list archive at Nabble.com.
 
 
 
 
  --
  Amila Suriarachchi
  WSO2 Inc.
  blog: http://amilachinthaka.blogspot.com/
 
 

 --
 View this message in context:
 http://old.nabble.com/WS-works-in-Axis-2-1.3-and-1.4.1-but-has-timeout-in-Axis-1.5.1--tp26340326p26479852.html
 Sent from the Axis - User mailing list archive at Nabble.com.




-- 
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/


Must Understand check failed for header - Security

2009-11-23 Thread amitvora

Hi,

I am using axis2 1.5.1 and rampart 1.4. I have created a Axis2 client
programmatically. The service is not a Axis2 service. It is an Oracle ESB
service. The service has mustUnderstand block attached to the header. The
request envelope goes successfully to the server, the service processes the
request also. But, I am not able to get the response out of it. It throws an
exception in the following line:

operationClient.execute(true);

Exception in thread main org.apache.axis2.AxisFault: Must Understand check
failed for header
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd
: Security
at
org.apache.axis2.engine.AxisEngine.checkMustUnderstand(AxisEngine.java:97)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:163)
at
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:364)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:417)
at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
at
org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
at grie11062009.CallWSS2.main(CallWSS2.java:92)

How do I solve this issue?

Thanks and regards,
Amit Vora
-- 
View this message in context: 
http://old.nabble.com/Must-Understand-check-failed-for-header---Security-tp26491276p26491276.html
Sent from the Axis - User mailing list archive at Nabble.com.



Re: Must Understand check failed for header - Security

2009-11-23 Thread Prabath Siriwardena
You get this error because the security header in the response not being 
processed by your client - which is by the Rampart module.


Please double check whether you have engaged rampart at the client side 
-also please post us the response you get from the service.


Thanks  regards.
-Prabath

amitvora wrote:

Hi,

I am using axis2 1.5.1 and rampart 1.4. I have created a Axis2 client
programmatically. The service is not a Axis2 service. It is an Oracle ESB
service. The service has mustUnderstand block attached to the header. The
request envelope goes successfully to the server, the service processes the
request also. But, I am not able to get the response out of it. It throws an
exception in the following line:

operationClient.execute(true);

Exception in thread main org.apache.axis2.AxisFault: Must Understand check
failed for header
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd
: Security
at
org.apache.axis2.engine.AxisEngine.checkMustUnderstand(AxisEngine.java:97)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:163)
at
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:364)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:417)
at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
at
org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
at grie11062009.CallWSS2.main(CallWSS2.java:92)

How do I solve this issue?

Thanks and regards,
Amit Vora