Re: [Axis2] [rampart] Problems using rampart

[Dimuthu Leelaratne]

Hi Sebastian,

This is not a rampart problem. The pointed out JIRA shows the bug.  I
walked through the stack trace. This happens for specific SOAP
messages, when they are converted to DOOM as mentioned. I have never
experienced the problem. Maybe because the SOAP messages that I use
wouldn't re-create the problem.

Regards,
Dimuthu


On 1/17/07, Sebastian Roschke <[EMAIL PROTECTED]> wrote:

Hi everybody,

I have a problem using rampart in axis2. I just have configured the
axis2-client.xml this way, that it should use rampart. At the moment I
have no configuration for the rampart module at all. While using the
client api to invoke a soap request, I get the following exceptions:

org.apache.axis2.AxisFault: Error in extracting message properties;
nested exception is:
org.apache.rampart.RampartException: Error in extracting message
properties
at
org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:65)
at org.apache.axis2.engine.Phase.invoke(Phase.java:381)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:518)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:651)
at
org.apache.axis2.description.OutOnlyAxisOperationClient.execute(OutOnlyAxisOperation.java:353)
at
skid.messaging.ws.client.client.MessagingClientServiceStub.addClient(MessagingClientServiceStub.java:126)
at skid.messaging.client.ClientControl.main(ClientControl.java:55)
Caused by: org.apache.rampart.RampartException: Error in extracting
message properties
at
org.apache.rampart.RampartMessageData.(RampartMessageData.java:294)
at org.apache.rampart.MessageBuilder.build(MessageBuilder.java:56)
at
org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:59)
... 6 more
Caused by: org.apache.ws.security.WSSecurityException: Error in
converting SOAP Envelope to Document; nested exception is:
org.apache.axiom.om.OMException: javax.xml.stream.XMLStreamException
at
org.apache.rampart.util.Axis2Util.getDocumentFromSOAPEnvelope(Axis2Util.java:121)
at
org.apache.rampart.RampartMessageData.(RampartMessageData.java:146)
... 8 more
Caused by: org.apache.axiom.om.OMException:
javax.xml.stream.XMLStreamException
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:199)
at org.apache.axiom.om.impl.dom.NodeImpl.build(NodeImpl.java:469)
at
org.apache.axiom.om.impl.dom.DocumentImpl.build(DocumentImpl.java:476)
at
org.apache.rampart.util.Axis2Util.getDocumentFromSOAPEnvelope(Axis2Util.java:107)
... 9 more
Caused by: javax.xml.stream.XMLStreamException
at
org.apache.axiom.om.impl.llom.OMStAXWrapper.updateLastNode(OMStAXWrapper.java:952)
at
org.apache.axiom.om.impl.llom.OMStAXWrapper.next(OMStAXWrapper.java:913)
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:116)
... 12 more

This exception is thrown when invoking the first request on the stub. I
can find the following link concerning that problem:
http://www.mail-archive.com/axis-dev@ws.apache.org/msg25582.html


As proposed in this post I should check wether the soap message includes
MIME parts. I used MIME parts in former times, but at the moment I
disabled all MTOM related things.

Do you have any suggestions concernings this problem? Is it a known
problem or a bug?







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

Re: WS-SECURITY WITH SAML2 TOKENS

[Dimuthu Leelaratne]

Hi Evaristo,'

Rampart uses opensaml-1.1 library to give support for the SAML.
Currently the library doen't support SAML2.

Regards,
Dimuthu

On 1/17/07, Evaristo José Camarero <[EMAIL PROTECTED]> wrote:


Hi:

Does Axis2 with rampart module support SAML2 Security
Tokens?

Regards,

Evaristo





__
LLama Gratis a cualquier PC del Mundo.
Llamadas a fijos y móviles desde 1 céntimo por minuto.
http://es.voice.yahoo.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]

Re: Custom exception mapping with JibX

[Vedha Vijayan]

Thanks for your reply.

I'm currently doing some research and after perusing the
recommendations, I wanted to try out the abstract+concrete wsdl
approach. 

Although, the advantages to following this approach is not significant,
I'd like to think that in future there will be few benefits. 


I have a follow up question to this thread:

I create the wsdl, which i can validate properly. I generate the
skeleton code using wsdl2java by providing the binding file using
-Ebindingfile. I'm able to successfully deploy the service.


However, I have a problem with my client. I use ADB databinding for the
client, and when i run my client, I get the following exception:



org.apache.axis2.AxisFault: java.lang.RuntimeException: Unable to access
binding information for class com.comergent.bean.simple.UserContactBean
Make sure the binding has been compiled
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:271)
at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:202)
at com.comergent.user.stub.UserServiceStub.getUser(Unknown
Source)
at
com.comergent.user.client.UserServiceAdbClient.getUser(Unknown Source)
at com.comergent.user.client.UserServiceAdbClient.main(Unknown
Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.tools.ant.taskdefs.ExecuteJava.run(ExecuteJava.java:202)
at
org.apache.tools.ant.taskdefs.ExecuteJava.execute(ExecuteJava.java:134)
at org.apache.tools.ant.taskdefs.Java.run(Java.java:710)
at org.apache.tools.ant.taskdefs.Java.executeJava(Java.java:178)
at org.apache.tools.ant.taskdefs.Java.execute(Java.java:84)
at
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at
org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
at
org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:37)
at
org.apache.tools.ant.Project.executeTargets(Project.java:1068)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
at
org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:107)
at
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at
org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
at
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
at
org.apache.tools.ant.Project.executeTargets(Project.java:1068)
at org.apache.tools.ant.Main.runBuild(Main.java:668)


What is surprising to me is that, it is trying to look for the binding
file for the Userbean. From what I understand, the binding file is
required only for JiBX databinding and that is the choice on the server
side. However, when the client uses a different databinding framework
and when there is no dependency on the UserContactBean class from the
client-side, why do i run into this problem?

Thanks in advance,
vedha




On Wed, 2007-01-17 at 11:46 +1300, Dennis Sosnoski wrote:
> Vedha Vijayan wrote:
> >  I'm trying to expose an existing service as a Web service. I've got few
> > queries regarding the process involved in doing so and about custom
> > exception mapping with JiBX. 
> >
> > 1. I generated the bindings (JiBX) and the schema for the classes
> > involved. The recommended procedure of creating a wsdl is to have an
> > abstract wsdl that defines the messages and then a concrete wsdl that
> > defines the bindings and the services. Is there a automated process to
> > go from the xsd and the Java class to generating the wsdl's? I had to
> > hand-code/edit the wsdl created using java2wsdl command. Is there any
> > tool that takes in the schema generated as a parameter and uses that to
> > automatically generate the wsdl? How do people go about devising means
> > to generate abstract and concrete wsdl's?
> >   
> There currently is no automated process to go from the xsd and Java 
> class to generating the WSDL(s), but I'm working on a tool of that type 
> and will post to this list when something is available.
> 
> I'm curious about your abstract+concrete WSDL process, though - who 
> recommends this procedure, and what benefits do you see as a result?

Re: Configuration in Rampart 1.1

[Dimuthu Leelaratne]

Hi Sriram,

As I understand your single client can tallk to multiple services but
with different security requirements. For configurations now we
encourage using Policy file according to WS Security Policy
specification 
(http://specs.xmlsoap.org/ws/2005/07/securitypolicy/ws-securitypolicy.pdf).

Since your services require different security settings, we may have
to create different Policy.xml files. After that according to the
service the client is going to invoke you  can load the relevant
Policy file as follows.

StAXOMBuilder builder  = new StAXOMBuilder(pathToPolicyfile);
   Policy clientPolicy =
PolicyEngine.getPolicy(builder.getDocumentElement());
//setting the object
Options options = new Options();
   options.setProperty(RampartMessageData.KEY_RAMPART_POLICY,
clientPolicy);


Schemas are available at,
http://ws.apache.org/axis2/modules/rampart/1_1/security-module.html

Cheers,
Dimuthu



On 1/18/07, Sriram Vaidyanathan <[EMAIL PROTECTED]> wrote:

Hi,
 I am currently trying to upgrade to Rampart 1.1 from Rampart 1.0 and using 
Rampart 1.0 we could talk to multiple services from a single client by 
programmatically configuring the parameters using the OutflowConfiguration 
class.

From previous posts in the forum it looks like these are deprecated with the 
1.1 releases. Is there an alternative way we can dynamically configure the 
parameters in 1.1?  Any help on this would be appreciated.

Thanks and Regards
Sriram Vaidyanathan




-
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]

Re: wsdl2java generates incorrect/incomplete code

[Jeff Greif]

Anne,

As usual, you are a fount of useful information.  Thanks for all you
do to explain the various SOA standards to the world.

Questions:

1.  What schema is supposed to be provided by ?xsd.

  a.  Is it the schema containing the declarations of the types or
elements used as message parts?

  b.  What if that information is contained in several schemas?

  c.  Does this access schemas contained in the types section of the
wsdl and/or imports from those schemas?

2.  Starting from a correct and consistent wsdl descriptor, is there a
deterministic algorithm that finds all the policy metadata?

  a.  If the policies are embedded in the wsdl and/or referenced in
the wsdl, does extracting all the embedded ones and retrieving all the
references (recursively if that's necessary), will that be all of the
policies that apply?

  b.  Will there be any policies that apply that are not referenced
or embedded in the wsdl?

  c.  If policies must be retrieved from a UDDI repository, is that
repository referenced in the wsdl or is there some out-of-band process
that must be followed to determine its existence?

  d.  Similarly for access via ?policy.

3.  Do the queries service-endpoint?policy and service-endpoint?xsd
produce exceptions when not implemented, or do they produce some empty
result?  If they produce a result, is it guaranteed that the result
contains or references (perhaps recursively) all the policies or
schemas needed to consume the web service?

4.  Do you ever need to use more than one of the various methods
(query-url, wsdl-cracking, Ws-MetadataExchange or UDDI) of obtaining
the metadata, or is any one that doesn't fail equivalent to any other
that doesn't fail?

Jeff

On 1/17/07, Anne Thomas Manes <[EMAIL PROTECTED]> wrote:

The way it supposed to work is thus:

- A web service has various metadata files associated with it:
   - WSDL defines the supported interfaces, MEPs, and bindings
   - XSD defines the message formats
   - WS-Policy defines its constraints and capabilities
(policies can be embedded in the WSDL or attached via UDDI)
- You have various means to locate the metadata
   - Look it up via UDDI (all metadata should be registered,
   WS-PolicyAttachment defines how policies are attached via UDDI)
   - Query the service for its metadata using WS-MetadataExchange
   - Query the service access point, appending "?wsdl", "?xsd", and "?policy"
   to the URL and hope that the service supports this convention

Anne
On 1/17/07, Jeff Greif <[EMAIL PROTECTED]> wrote:
> Anne,
>
> So if you want to dynamically consume web services based on the wsdl
> alone, the WS-Policy constructs have to be embedded there and the
> client machinery has to know how to process them to determine what
> headers are required, if any?  Is this the way it's supposed to work?
>
> Is the alternative to get the WS-Policy requirements from some
> different repository?  Is there a regular scheme related to UDDI or
> something that provides this?
>
> Jeff
>
> On 1/17/07, Anne Thomas Manes <[EMAIL PROTECTED]> wrote:
> > Bruce,
> >
> ...
> > But I reiterate my earlier comment. I strongly discourage you from
> > defining headers in the WSDL. The WSDL represents the information that
> > the application should be responsible for. Typically headers are added
> > to the message and processed by the middleware, not by the
> > application. Therefore the requirement for headers should be specified
> > separately -- preferably using WS-Policy, even though it isn't final
> > yet.
> >
> > I also *strongly* recommend that you not define your own header
> > formats, but rather that you conform to standard SOAP extensions -- in
> > your case WS-Addressing and WS-Security. (You've used standard element
> > definitions from WS-Addressing and XML Signature, but you haven't
> > followed the standard header formats for using these elements.)
> >
> > Axis2 can automatically manage WS-Addressing and WS-Security headers
> > for you, and they will do so in an interoperable way. But you mustn't
> > define the headers in the WSDL -- you must configure them in the
> > config file.
> >
> > Anne
> >
> > On 1/17/07, R Bruce Hoffman <[EMAIL PROTECTED]> wrote:
> > > First, let me sincerely thank you for your rapid response.
> > >
> > > I had originally questioned the other developers on that repeated import
> > > of the namespace and been told it was ok. I probably have to be more
> > > forceful when my gut says it's wrong... but, as you can probably tell, I
> > > am new to this WSDL stuff.. previous services I have deployed were from
> > > POJOs and not defined by or through WSDL, and I am no xml expert either.
> > >
> > > At least I have ammo to go back to them and have their manager apply the
> > > "2 by 4" process...  ;-)
> > >
> > > Next here are the other two xsd's that I had left off.
> > >
> > > again, thanks.
> > >
> > >
> > > On Wed, 2007-01-17 at 08:50 -0500, Anne Thomas Manes wrote:
> > > > Bruce,
> > > >
> > > > Giving the WSDL a

Re: [Axis2] Simple stand-alone client to invoke web services

[footh]

Paul, thanks for the reply.

You are correct.  I was actually missing libraries and
I mistakenly assummed it had to do with the axis
configuration files.

I was able to just instantiate a ServiceClient and
invoke a service without a problem.

Best regards,

JF

--- Paul Fremantle <[EMAIL PROTECTED]> wrote:

> Footh
> 
> Can you please give more details when you say the
> default constructor
> doesn't work?
> 
> ServiceClient sc = new ServiceClient();
> 
> should work fine without an external repository or
> axis2.xml. Also if
> you need modules like addressing in a simple client
> like this you can
> just put the .mar file in the classpath.
> 
> Paul
> 
> On 1/16/07, footh <[EMAIL PROTECTED]> wrote:
> > Thanks for the reply.
> >
> > I already have something very similar to that.  I
> was
> > hoping, however, to avoid having to use external
> files
> > to create the configuration.
> >
> > But, I can concede on that if it is absolutely
> > necessary.  However, do I need to use the
> axis2.xml
> > file that comes with Axis2?  It seems to have a
> bunch
> > of parameters that I am not interested in.  In
> fact,
> > I'm not even sure what parameters I need if I want
> to
> > simply invoke and request-response service over
> HTTP.
> >
> > Additionally, do I need to have the repository
> > directory?  I notice that the addressing module is
> in
> > there, but can I just stick that with the rest of
> the
> > .jar files?
> > --- "Yadav, Yogendra (IT)"
> > <[EMAIL PROTECTED]> wrote:
> >
> > > Try this
> > >
> > >   ConfigurationContext ctx =
> > >
> >
>
ConfigurationContextFactory.createConfigurationContextFromFileSystem("C:
> > >
> /work/AXIS2-Examples/for-client-testing/repository",
> > >
> >
>
"C:/work/AXIS2-Examples/for-client-testing/axis2.xml");
> > >   ServiceClient sc = new ServiceClient(ctx,
> > > null);
> > >   Options opt = new Options();
> > >   opt.setTo(new
> > >
> >
>
EndpointReference("http://localhost:8080/axis2/services/XSDJAXBService";)
> > > );
> > >   opt.setTransportInProtocol(
> > > Constants.TRANSPORT_HTTP );
> > >   opt.setAction("ServiceMethod");
> > >   sc.engageModule( new QName(
> > > Constants.MODULE_ADDRESSING ) );
> > >   sc.setOptions(opt);
> > >
> > >   OMElement payload = getPayload();
> > >   OMElement ol = sc.sendReceive( payloadRoot
> );
> > >
> > >
> > > -Original Message-
> > > From: footh [mailto:[EMAIL PROTECTED]
> > > Sent: Tuesday, January 16, 2007 3:07 PM
> > > To: axis-user@ws.apache.org
> > > Subject: [Axis2] Simple stand-alone client to
> invoke
> > > web services
> > >
> > > I have a separate java web application running
> under
> > > Tomcat 5.5 in which
> > > I want to dynamically invoke web services using
> > > Axis2.
> > >
> > > I was able to easily do this using Axis1, but I
> am
> > > running into a
> > > problem with Axis2.  I've followed the simple
> > > examples in the
> > > documentation with creating a ServiceClient
> object
> > > and then sending a
> > > payload.
> > >
> > > However, I am having trouble with the
> ServiceClient
> > > object.  I was
> > > creating it with the default constructor, but
> that
> > > doesn't work without
> > > the default axis2.xml file and repository.
> > >
> > > So, I looked into creating my own
> > > ContextConfiguration, but I can't seem to find
> any
> > > way of doing it
> > > dynamically.  Do I have to point to a separate
> file
> > > every time
> > > (axis2.xml) or can I create the configuration in
> > > code alone?  Can anyone
> > > point me to examples of how this might be done?
> > >
> > >
> > >
> > >
> >
>

> > > 
> > > Food fight? Enjoy some healthy debate
> > > in the Yahoo! Answers Food & Drink Q&A.
> > >
> >
>
http://answers.yahoo.com/dir/?link=list&sid=396545367
> > >
> > >
> >
>
-
> > > To unsubscribe, e-mail:
> > > [EMAIL PROTECTED]
> > > For additional commands, e-mail:
> > > [EMAIL PROTECTED]
> > >
> >
>

> > >
> > > NOTICE: If received in error, please destroy and
> > > notify sender. Sender does not intend to waive
> > > confidentiality or privilege. Use of this email
> is
> > > prohibited when received in error.
> > >
> > >
> >
>
-
> > > To unsubscribe, e-mail:
> > > [EMAIL PROTECTED]
> > > For additional commands, e-mail:
> > > [EMAIL PROTECTED]
> > >
> > >
> >
> >
> >
> >
> >
>

> > Sucker-punch spam with award-winning protection.
> > Try the free Yahoo! Mail Beta.
> >
>
http://advision.webevents.yahoo.com/mailbeta/features_spam.html
> >
> >
>
-
> > To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> > For additional commands, e-mail:
> [

Could AXIS2 used together with jUDDI?

[Jiang Liu]

Hi all
I am having a project that require to retrieve service from private UDDI 
registry. Currently i am using Geronimo server + AXIS2 + jUDDI v09rc4.

>From the jUDDI's configuration page, there are errors:
jUDDI Dependencies: Resource & Properties Files

Looking for: log4j.xml
-Not Found

jUDDI DataSource Validation

+ Got a JNDI Context!
- No 'java:comp/env/jdbc/juddiDB' DataSource Located(jdbc/juddiDB)
- DB connection was not aquired. (null)
- SELECT COUNT(*) FROM PUBLISHER failed (null)

Also with my simple UDDI registry client, errors are:
- Unable to find required classes (javax.activation.DataHandler and 
javax.mail.internet.MimeMultipart). Attachment support is disabled.

at org.uddi4j.UDDIElement.(UDDIElement.java:40)
at org.uddi4j.response.AuthToken.(AuthToken.java:85)
at org.uddi4j.client.UDDIProxy.get_authToken(UDDIProxy.java:1626)
at Client.main(Client.java:25)


Is that the problem with my jUDDI and geronimo or the problem with jUDDI and 
AXIS2?

cheers!!
-
Jiang Liu
Student Number: 3075163
CS/Yallara Name: ljiang

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

Re: wsdl2java generates incorrect/incomplete code

[R Bruce Hoffman]

you call 10MB big? HA! I download System i software and Redhat
distributions... that's big. Send away... my email should be able to
handle anything less than a couple of GB...


On Wed, 2007-01-17 at 19:56 -0500, Anne Thomas Manes wrote:
> I use the Cape Clear SOA Editor tool. It's free, but not open source.
> No support. I have permission to distribute it, so I can send it to
> you if you like. It's a big file, though. (>10MB)
> 
> Anne
> 
> On 1/17/07, R Bruce Hoffman <[EMAIL PROTECTED]> wrote:
> > Again, thank you so much for the effort and information.
> >
> > What tool is it that you are using to validate this stuff? And, is it a
> > commercial product or open source tool?
> >
> >
> > On Wed, 2007-01-17 at 13:20 -0500, Anne Thomas Manes wrote:
> > > Bruce,
> > >
> > > I took the WSDL file, commented out the imports, pasted the schemas
> > > inline, and validated the WSDL. I found one error:
> > >
> > >There is no schema component of the name [ds:Signature] 
> > > defined
> > >in the WSDL either via imported or embedded schema.
> > >
> > > I don't understand why this error comes up, because as far as I can
> > > tell, the DSig namespace is properly imported, and certainly the
> > > Signature element is properly defined in the DSig namespace. I know
> > > that quite a few folks have experienced problems when trying to use
> > > the DSig namespace, so my guess is that many tools have trouble with
> > > the "#" in the namespace URI.
> > >
> > > My tool also raised two warnings:
> > >
> > >You have nested sequences (which should be okay)
> > >You have a maxOccurs attribute on an xsd:sequence 
> > > declaration
> > >  (something to avoid)
> > >
> > > Something else I noticed: The request and reply schemas do not specify
> > > elementFormDefault="qualified". This isn't an error, but it often
> > > causes interoperability errors.
> > >
> > > But I reiterate my earlier comment. I strongly discourage you from
> > > defining headers in the WSDL. The WSDL represents the information that
> > > the application should be responsible for. Typically headers are added
> > > to the message and processed by the middleware, not by the
> > > application. Therefore the requirement for headers should be specified
> > > separately -- preferably using WS-Policy, even though it isn't final
> > > yet.
> > >
> > > I also *strongly* recommend that you not define your own header
> > > formats, but rather that you conform to standard SOAP extensions -- in
> > > your case WS-Addressing and WS-Security. (You've used standard element
> > > definitions from WS-Addressing and XML Signature, but you haven't
> > > followed the standard header formats for using these elements.)
> > >
> > > Axis2 can automatically manage WS-Addressing and WS-Security headers
> > > for you, and they will do so in an interoperable way. But you mustn't
> > > define the headers in the WSDL -- you must configure them in the
> > > config file.
> > >
> > > Anne
> > >
> > > On 1/17/07, R Bruce Hoffman <[EMAIL PROTECTED]> wrote:
> > > > First, let me sincerely thank you for your rapid response.
> > > >
> > > > I had originally questioned the other developers on that repeated import
> > > > of the namespace and been told it was ok. I probably have to be more
> > > > forceful when my gut says it's wrong... but, as you can probably tell, I
> > > > am new to this WSDL stuff.. previous services I have deployed were from
> > > > POJOs and not defined by or through WSDL, and I am no xml expert either.
> > > >
> > > > At least I have ammo to go back to them and have their manager apply the
> > > > "2 by 4" process...  ;-)
> > > >
> > > > Next here are the other two xsd's that I had left off.
> > > >
> > > > again, thanks.
> > > >
> > > >
> > > > On Wed, 2007-01-17 at 08:50 -0500, Anne Thomas Manes wrote:
> > > > > Bruce,
> > > > >
> > > > > Giving the WSDL a quick look, I noticed that it is not valid. I don't
> > > > > know if this is what's causing your problem, but it's a good place to
> > > > > start.
> > > > >
> > > > > In your WSDL  section, you attempt to import the same namespace
> > > > > twice. This is not allowed. If the namespace is defined in multiple
> > > > > schemas, and your goal is to import both schemas, then you must define
> > > > > a schema with the same target namespace and  the schemas
> > > > > into the namespace. e.g.:
> > > > >
> > > > > > > > >   xmlns:xs="http://www.w3.org/2001/XMLSchema";
> > > > >   elementFormDefault="qualified">
> > > > >> > > >   
> > > > > schemaLocation="1.0/receive-purchase-order-request.xsd"/>
> > > > >> > > >   
> > > > > schemaLocation="1.0/receive-purchase-order-reply.xsd"/>
> > > > >   
> > > > >
> > > > > Another error that I found: you must not specify the parameterOrder
> > > > > attribute in the  definition when using doc

Re: wsdl2java generates incorrect/incomplete code

[Anne Thomas Manes]

The way it supposed to work is thus:

- A web service has various metadata files associated with it:
  - WSDL defines the supported interfaces, MEPs, and bindings
  - XSD defines the message formats
  - WS-Policy defines its constraints and capabilities
   (policies can be embedded in the WSDL or attached via UDDI)
- You have various means to locate the metadata
  - Look it up via UDDI (all metadata should be registered,
  WS-PolicyAttachment defines how policies are attached via UDDI)
  - Query the service for its metadata using WS-MetadataExchange
  - Query the service access point, appending "?wsdl", "?xsd", and "?policy"
  to the URL and hope that the service supports this convention

Anne
On 1/17/07, Jeff Greif <[EMAIL PROTECTED]> wrote:

Anne,

So if you want to dynamically consume web services based on the wsdl
alone, the WS-Policy constructs have to be embedded there and the
client machinery has to know how to process them to determine what
headers are required, if any?  Is this the way it's supposed to work?

Is the alternative to get the WS-Policy requirements from some
different repository?  Is there a regular scheme related to UDDI or
something that provides this?

Jeff

On 1/17/07, Anne Thomas Manes <[EMAIL PROTECTED]> wrote:
> Bruce,
>
...
> But I reiterate my earlier comment. I strongly discourage you from
> defining headers in the WSDL. The WSDL represents the information that
> the application should be responsible for. Typically headers are added
> to the message and processed by the middleware, not by the
> application. Therefore the requirement for headers should be specified
> separately -- preferably using WS-Policy, even though it isn't final
> yet.
>
> I also *strongly* recommend that you not define your own header
> formats, but rather that you conform to standard SOAP extensions -- in
> your case WS-Addressing and WS-Security. (You've used standard element
> definitions from WS-Addressing and XML Signature, but you haven't
> followed the standard header formats for using these elements.)
>
> Axis2 can automatically manage WS-Addressing and WS-Security headers
> for you, and they will do so in an interoperable way. But you mustn't
> define the headers in the WSDL -- you must configure them in the
> config file.
>
> Anne
>
> On 1/17/07, R Bruce Hoffman <[EMAIL PROTECTED]> wrote:
> > First, let me sincerely thank you for your rapid response.
> >
> > I had originally questioned the other developers on that repeated import
> > of the namespace and been told it was ok. I probably have to be more
> > forceful when my gut says it's wrong... but, as you can probably tell, I
> > am new to this WSDL stuff.. previous services I have deployed were from
> > POJOs and not defined by or through WSDL, and I am no xml expert either.
> >
> > At least I have ammo to go back to them and have their manager apply the
> > "2 by 4" process...  ;-)
> >
> > Next here are the other two xsd's that I had left off.
> >
> > again, thanks.
> >
> >
> > On Wed, 2007-01-17 at 08:50 -0500, Anne Thomas Manes wrote:
> > > Bruce,
> > >
> > > Giving the WSDL a quick look, I noticed that it is not valid. I don't
> > > know if this is what's causing your problem, but it's a good place to
> > > start.
> > >
> > > In your WSDL  section, you attempt to import the same namespace
> > > twice. This is not allowed. If the namespace is defined in multiple
> > > schemas, and your goal is to import both schemas, then you must define
> > > a schema with the same target namespace and  the schemas
> > > into the namespace. e.g.:
> > >
> > > > >   xmlns:xs="http://www.w3.org/2001/XMLSchema";
> > >   elementFormDefault="qualified">
> > >> >   
schemaLocation="1.0/receive-purchase-order-request.xsd"/>
> > >> >   
schemaLocation="1.0/receive-purchase-order-reply.xsd"/>
> > >   
> > >
> > > Another error that I found: you must not specify the parameterOrder
> > > attribute in the  definition when using document
> > > style. (It is only used with RPC style.)
> > >
> > > As a general practice, it's a bad idea to define headers in your WSDL,
> > > especially if you are using standard headers. (The XMLBeans error
> > > indicates that you are using WS-Addressing and DSIG.) You should
> > > define your header requirements using WS-Policy and configuration
> > > files.
> > >
> > > Also, in regards to schema you did provide
> > > (targetNamespace="urn:/fih/purchase-order"), some best practices
> > > advice:
> > >
> > > - Avoid using anonymous types. Rather than defining structures as
> > > elements, define them as named types, and then define elements as
> > > those types. e.g.:
> > >
> > > Do this:
> > >
> > > 
> > >   
> > >   
> > >   
> > >   
> > >   
> > > 
> > >
> > > Rather than this:
> > >
> > >   
> > >   
> > >  

Configuration in Rampart 1.1

[Sriram Vaidyanathan]

Hi,
 I am currently trying to upgrade to Rampart 1.1 from Rampart 1.0 and using 
Rampart 1.0 we could talk to multiple services from a single client by 
programmatically configuring the parameters using the OutflowConfiguration 
class.

>From previous posts in the forum it looks like these are deprecated with the 
>1.1 releases. Is there an alternative way we can dynamically configure the 
>parameters in 1.1?  Any help on this would be appreciated.

Thanks and Regards
Sriram Vaidyanathan




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

Re: wsdl2java generates incorrect/incomplete code

[Anne Thomas Manes]

I use the Cape Clear SOA Editor tool. It's free, but not open source.
No support. I have permission to distribute it, so I can send it to
you if you like. It's a big file, though. (>10MB)

Anne

On 1/17/07, R Bruce Hoffman <[EMAIL PROTECTED]> wrote:

Again, thank you so much for the effort and information.

What tool is it that you are using to validate this stuff? And, is it a
commercial product or open source tool?


On Wed, 2007-01-17 at 13:20 -0500, Anne Thomas Manes wrote:
> Bruce,
>
> I took the WSDL file, commented out the imports, pasted the schemas
> inline, and validated the WSDL. I found one error:
>
>There is no schema component of the name [ds:Signature] defined
>in the WSDL either via imported or embedded schema.
>
> I don't understand why this error comes up, because as far as I can
> tell, the DSig namespace is properly imported, and certainly the
> Signature element is properly defined in the DSig namespace. I know
> that quite a few folks have experienced problems when trying to use
> the DSig namespace, so my guess is that many tools have trouble with
> the "#" in the namespace URI.
>
> My tool also raised two warnings:
>
>You have nested sequences (which should be okay)
>You have a maxOccurs attribute on an xsd:sequence declaration
>  (something to avoid)
>
> Something else I noticed: The request and reply schemas do not specify
> elementFormDefault="qualified". This isn't an error, but it often
> causes interoperability errors.
>
> But I reiterate my earlier comment. I strongly discourage you from
> defining headers in the WSDL. The WSDL represents the information that
> the application should be responsible for. Typically headers are added
> to the message and processed by the middleware, not by the
> application. Therefore the requirement for headers should be specified
> separately -- preferably using WS-Policy, even though it isn't final
> yet.
>
> I also *strongly* recommend that you not define your own header
> formats, but rather that you conform to standard SOAP extensions -- in
> your case WS-Addressing and WS-Security. (You've used standard element
> definitions from WS-Addressing and XML Signature, but you haven't
> followed the standard header formats for using these elements.)
>
> Axis2 can automatically manage WS-Addressing and WS-Security headers
> for you, and they will do so in an interoperable way. But you mustn't
> define the headers in the WSDL -- you must configure them in the
> config file.
>
> Anne
>
> On 1/17/07, R Bruce Hoffman <[EMAIL PROTECTED]> wrote:
> > First, let me sincerely thank you for your rapid response.
> >
> > I had originally questioned the other developers on that repeated import
> > of the namespace and been told it was ok. I probably have to be more
> > forceful when my gut says it's wrong... but, as you can probably tell, I
> > am new to this WSDL stuff.. previous services I have deployed were from
> > POJOs and not defined by or through WSDL, and I am no xml expert either.
> >
> > At least I have ammo to go back to them and have their manager apply the
> > "2 by 4" process...  ;-)
> >
> > Next here are the other two xsd's that I had left off.
> >
> > again, thanks.
> >
> >
> > On Wed, 2007-01-17 at 08:50 -0500, Anne Thomas Manes wrote:
> > > Bruce,
> > >
> > > Giving the WSDL a quick look, I noticed that it is not valid. I don't
> > > know if this is what's causing your problem, but it's a good place to
> > > start.
> > >
> > > In your WSDL  section, you attempt to import the same namespace
> > > twice. This is not allowed. If the namespace is defined in multiple
> > > schemas, and your goal is to import both schemas, then you must define
> > > a schema with the same target namespace and  the schemas
> > > into the namespace. e.g.:
> > >
> > > > >   xmlns:xs="http://www.w3.org/2001/XMLSchema";
> > >   elementFormDefault="qualified">
> > >> >   
schemaLocation="1.0/receive-purchase-order-request.xsd"/>
> > >> >   
schemaLocation="1.0/receive-purchase-order-reply.xsd"/>
> > >   
> > >
> > > Another error that I found: you must not specify the parameterOrder
> > > attribute in the  definition when using document
> > > style. (It is only used with RPC style.)
> > >
> > > As a general practice, it's a bad idea to define headers in your WSDL,
> > > especially if you are using standard headers. (The XMLBeans error
> > > indicates that you are using WS-Addressing and DSIG.) You should
> > > define your header requirements using WS-Policy and configuration
> > > files.
> > >
> > > Also, in regards to schema you did provide
> > > (targetNamespace="urn:/fih/purchase-order"), some best practices
> > > advice:
> > >
> > > - Avoid using anonymous types. Rather than defining structures as
> > > elements, define them as named types, and then define elements as
> >

Re: error in generated classes in axis2 1.1.1

[Ajith Ranabahu]

Hi,
The best thing to do would be to open a Jira and attach your
schema/WSDL. It would be also a good idea to validate the WSDL/Schema
(probably something like the XSV in W3C or the cape clear WSDL editor)
It could be that your schema containing an unsupported schema
constructs for ADB [It should throw an error in that case anyway] so
you may also try XMLBeans as a databinding.

Ajith

On 1/17/07, emerson cargnin <[EMAIL PROTECTED]> wrote:

I just generated the stub using axis2 1.1.1

In some classes generated, im getting the error "The field parentQName
is defined in an inherited type and an enclosing scope". I used the
option u (Unpacks the databinding classes), the error is on these
classes.The error is always on any code that refers to "parentQName"
field.

Thanks very much
Emerson

example of the code generated:

   public org.apache.axiom.om.OMDataSource getOMDataSource(
final javax.xml.namespace.QName parentQName,
final org.apache.axiom.om.OMFactory factory){


org.apache.axiom.om.OMDataSource dataSource =
   new
org.apache.axis2.databinding.ADBDataSource(this,parentQName){

 public void serialize(
  javax.xml.stream.XMLStreamWriter
xmlWriter) throws javax.xml.stream.XMLStreamException {



java.lang.String prefix = parentQName.getPrefix();

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





--
Ajith Ranabahu

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

RE: Question axis 2 Java2WSDL tool

[Harish Hirasave]

Anne,

I meant I used the -uw option in step 3 below which generates the input
parameter as String now but the output parameter is a wrapped Response
Object which is causing problems when I invoke the service using php. I
get a boolean output instead of String because of this.

Thanks
Harish

-Original Message-
From: Harish Hirasave [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, January 17, 2007 1:31 PM
To: axis-user@ws.apache.org
Subject: RE: Question axis 2 Java2WSDL tool

Hi Anne,

I am using axis 2-1.1.1 and not axis 1.x. I am migrating from axis 1.2
to axis 2 -1.1.1. I did the following.

1. Created a Pojo
2. Generated a wsdl using Java2WSDL. This is where I am having problems
as axis 2 is generating request and response objects and not basic java
objects as parameters. The Java2WSDL tool does not have an option to
generate wsdl as unwrapped which I want as the client that uses my wsdl
is a non java client like php. 
3. Generated stub and skeleton using WSDL2Java. This has a -ur option
but does not seem to be working. 

Thanks
Harish

-Original Message-
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, January 16, 2007 8:03 PM
To: axis-user@ws.apache.org
Subject: Re: Question axis 2 Java2WSDL tool

In Axis 1.x, you must specify style="unwrapped" in the WSDD, or you
must ensure that the WSDL conforms to the wrapped doc/literal
convention.

On 1/16/07, Harish Hirasave <[EMAIL PROTECTED]> wrote:
> Hello Anne,
>
> I could not find this feature of automatic unwrapping. The Java2WSDL
and
> WSDL2Java in axis2-1.1.1 work in the same way as the axis2-1.1. The
code
> gets generated wrapped and I am unable to un wrap the classes and get
> return types as basic java objects. Please tell how this feature of
> unwrapping has been implemented and how to use it.
>
> Thanks
> Harish
>
> -Original Message-
> From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
> Sent: Friday, January 12, 2007 7:06 AM
> To: axis-user@ws.apache.org
> Subject: Re: Question axis 2 Java2WSDL tool
>
> Try using Axis2 1.1.1. What you're looking for is automatic
> "unwrapping" of the wrapper element, and that has only recently been
> implemented.
>
> Anne
>
> On 1/11/07, Harish Hirasave <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> >
> > I want document literal style but not wrapped. I am trying to
convert
> an
> > application from axis 1.2 to axis 2.1 and hence would like to use
> document
> > literal but I don't want the wrapper objects as the client that
would
> use
> > the service will not be a java client. Is there a way I can do this?
> >
> >
> >
> >  
> >
> >
> > From: Manoj Khangaonkar [mailto:[EMAIL PROTECTED]
> >  Sent: Thursday, January 11, 2007 3:18 PM
> >  To: axis-user@ws.apache.org
> >  Subject: Re: Question axis 2 Java2WSDL tool
> >
> >
> >
> >
> >
> > Harish,
> >
> >
> >
> >
> >
> > By default , AXIS2 java2WSDL generates what is called doc lit
wrapped
> style
> > WSDL.
> >
> >
> >
> >
> >
> > My guess is you want RPC lit style WSDL - like below
> >
> >
> >
> >
> >
> >  > name="getEligibleIVRPromotionsResponseMessage">
> >
> > 
> >
> > 
> >
> >
> > I think AXIS2 java2WSDL does not support this ( not 100% sure) ---
You
> might
> > want to try using the original AXIS java2WSDL - You typically pass
in
> the
> > WSDL
> >
> >
> > style as a command line parameter.
> >
> >
> >
> >
> >
> > In the original java2WSDL you could say java2WSDL -style rpc
> .
> >
> >
> >
> >
> >
> > in AXIS2 , you would java2WSDL -st  but I am not sure what the
> supported
> > values are.
> >
> >
> >
> >
> >
> > Mj
> >
> >
> >
> >
> >
> >
> > On 1/11/07, Harish Hirasave <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> > Hi,
> >
> >
> >
> > I have a pojo from which I am trying a generate a wsdl. The pojo has
> the
> > method
> >
> >
> >
> > public String getEligibleIVRPromotions(String phone)
> >
> > throws RemoteException
> >
> > {
> >
> > String errorMsg =
> > "IVRServiceSoapBindingImpl.getEligibleIVRPromotions(String):";
> >
> > String xml = null;
> >
> > return xml;
> >
> > }
> >
> >
> >
> > This method returns a String object.
> >
> >
> >
> > When I convert it to wsdl using the java2WSDL tool the wsdl method
> gets
> > generated with a getEligibleIVRPromotionsRequest Object as input and
> > getEligibleIVRPromotionsResponse Object as the return
> > object.
> >
> >
> >
> > How do I prevent this and  make the method return a String object
and
> not a
> > wrapper object getEligibleIVRPromotionsResponse? Attached
> > is the wsdl. Please help.
> >
> >
> >
> >
> >
> >
> >
> > Thanks
> >
> > Harish
> >
> >
> >
-
> >  To unsubscribe, e-mail:
> > [EMAIL PROTECTED]
> >  For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> >
> >
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: 

Re: [Axis2] Session Management and WS-Addressing

[Tim, Jane and Chelsea Johnson]

Thanks for replying. Yes, I read that article. That is why I am stumped as to 
why my service doesn't response with the correct headers when the client calls 
it the first time with the correct WS-Addressing headers. Do I have to build 
the WS-Addressing headers by hand or should Axis2 build them for me 
automatically? 

When you deploy a service in SOAP session and when a client tries to access the 
service in the first time, Axis2 will generate serviceGroupId and send that to 
the client as a reference parameter in wsa:ReplyTo, as shown below:


   
  http://www.w3.org/2005/08/addressing/anonymous
   
   
  http://ws.apache.org/namespaces/axis2";>
urn:uuid:65E9C56F702A398A8B11513011677354
  
   

If the client wants to live in the same session, he has to copy that reference 
parameter and send it back to the server when he invokes the service the second 
time. As long as a client sends the valid serviceGroupId, he can use the same 
session, and the service can maintain the session-related data. Unlike a 
request session, a SOAP session has a default timeout period, so if the client 
does not touch the service for 30 seconds, the session will expire, and if the 
client sends the old serviceGroupId, he will get an AxisFault too.

  - Original Message - 
  From: Brian De Pradine 
  To: axis-user@ws.apache.org 
  Sent: Wednesday, January 17, 2007 7:52 AM
  Subject: Re: [Axis2] Session Management and WS-Addressing



  Hello, 

  You may find the following link useful, [1] 

  [1]  http://www.developer.com/java/web/article.php/3620661 

  Cheers

  Brian DePradine
  Web Services Development
  IBM Hursley
  External  +44 (0) 1962 816319 Internal 246319

  If you can't find the time to do it right the first time, where will you find 
the time to do it again?


  "Tim, Jane and Chelsea Johnson" <[EMAIL PROTECTED]> wrote on 17/01/2007 
00:54:12:

  > I am running the latest version of axis2 - 1.1.1. I am trying to use 
session 
  > management via WS-Addressing.
  > In soapmonitor I can see the WS-Addressing headers going out on the request 
  > to the server. But my service's response doesn't have any of the 
  > WS-Addressing headers (specifically the groupID header). Addressing is 
  > enabled globally via the entry in Axis2.xml. In service.xml I set scope for 
  > the service to be "soapsession".
  > 
  > This is what the client is sending. Is there something I need to add or 
  > change to get the service to re-act with WS-Addressing headers.
  > 
  > 
  > http://www.w3.org/2005/08/addressing"; 
  > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
  >   
  > http://localhost:8080/axis2/services/AiMessageServices
  > 
  >   http://www.w3.
  > org/2005/08/addressing/anonymous
  > 
  > urn:uuid:F18B205BFF468A597911689950656872
  > urn:login
  >   
  >   
  > 
  >   124
  >   2567
  >   SJPC120.y
  >   2003
  > 
  >   
  >  
  > 
  > 
  > 
  > -
  > To unsubscribe, e-mail: [EMAIL PROTECTED]
  > For additional commands, e-mail: [EMAIL PROTECTED]
  > 

wsa:To and wsa:From, etc.. are missing in the SOAP header

[Gul Onural]

I am using ServiceClient's addHeader method to add header to my SOAP
messages on my client. But I don't see 
the following block of elements (wsa:MessageID, wsa:To, wsa:Action,
wsa:From, Address,...) in the header. 

I thought they would be automatically added by the ws addressing. What
else I need to do to get them in the header ?



 
urn:uuid:920C5190-0B8F-11D9-8CED-F22EDEEBF7E5
http://localhost:8081/axis/services/BankPort<
/wsa:To>
urn:DummyWSAAction

 
http://schemas.xmlsoap.org/ws/2004/03/addressing/role/anonymous

Re: wsdl2java generates incorrect/incomplete code

[Jeff Greif]

Anne,

So if you want to dynamically consume web services based on the wsdl
alone, the WS-Policy constructs have to be embedded there and the
client machinery has to know how to process them to determine what
headers are required, if any?  Is this the way it's supposed to work?

Is the alternative to get the WS-Policy requirements from some
different repository?  Is there a regular scheme related to UDDI or
something that provides this?

Jeff

On 1/17/07, Anne Thomas Manes <[EMAIL PROTECTED]> wrote:

Bruce,


...

But I reiterate my earlier comment. I strongly discourage you from
defining headers in the WSDL. The WSDL represents the information that
the application should be responsible for. Typically headers are added
to the message and processed by the middleware, not by the
application. Therefore the requirement for headers should be specified
separately -- preferably using WS-Policy, even though it isn't final
yet.

I also *strongly* recommend that you not define your own header
formats, but rather that you conform to standard SOAP extensions -- in
your case WS-Addressing and WS-Security. (You've used standard element
definitions from WS-Addressing and XML Signature, but you haven't
followed the standard header formats for using these elements.)

Axis2 can automatically manage WS-Addressing and WS-Security headers
for you, and they will do so in an interoperable way. But you mustn't
define the headers in the WSDL -- you must configure them in the
config file.

Anne

On 1/17/07, R Bruce Hoffman <[EMAIL PROTECTED]> wrote:
> First, let me sincerely thank you for your rapid response.
>
> I had originally questioned the other developers on that repeated import
> of the namespace and been told it was ok. I probably have to be more
> forceful when my gut says it's wrong... but, as you can probably tell, I
> am new to this WSDL stuff.. previous services I have deployed were from
> POJOs and not defined by or through WSDL, and I am no xml expert either.
>
> At least I have ammo to go back to them and have their manager apply the
> "2 by 4" process...  ;-)
>
> Next here are the other two xsd's that I had left off.
>
> again, thanks.
>
>
> On Wed, 2007-01-17 at 08:50 -0500, Anne Thomas Manes wrote:
> > Bruce,
> >
> > Giving the WSDL a quick look, I noticed that it is not valid. I don't
> > know if this is what's causing your problem, but it's a good place to
> > start.
> >
> > In your WSDL  section, you attempt to import the same namespace
> > twice. This is not allowed. If the namespace is defined in multiple
> > schemas, and your goal is to import both schemas, then you must define
> > a schema with the same target namespace and  the schemas
> > into the namespace. e.g.:
> >
> > >   xmlns:xs="http://www.w3.org/2001/XMLSchema";
> >   elementFormDefault="qualified">
> >>   
schemaLocation="1.0/receive-purchase-order-request.xsd"/>
> >>   
schemaLocation="1.0/receive-purchase-order-reply.xsd"/>
> >   
> >
> > Another error that I found: you must not specify the parameterOrder
> > attribute in the  definition when using document
> > style. (It is only used with RPC style.)
> >
> > As a general practice, it's a bad idea to define headers in your WSDL,
> > especially if you are using standard headers. (The XMLBeans error
> > indicates that you are using WS-Addressing and DSIG.) You should
> > define your header requirements using WS-Policy and configuration
> > files.
> >
> > Also, in regards to schema you did provide
> > (targetNamespace="urn:/fih/purchase-order"), some best practices
> > advice:
> >
> > - Avoid using anonymous types. Rather than defining structures as
> > elements, define them as named types, and then define elements as
> > those types. e.g.:
> >
> > Do this:
> >
> > 
> >   
> >   
> >   
> >   
> >   
> > 
> >
> > Rather than this:
> >
> >   
> >   
> >   
> >   
> >   
> >   
> >   
> >   
> >
> > And I recommend being cautious about defining each element as a global
> > element. The only elements that really should be defined as global
> > elements are those elements that will be the root of a document. i.e,
> > rather than defining "BaselineItemDataSegment" as a gloal element and
> > referencing it from the type definition, define the element within the
> > type definition and reference its type, e.g.:
> >
> >
> > We also need to see the "unr:/fih/c-efm/purchase-order/1.0" schema files.
> > (You sent us the "http://www.fih.org/XML/WD0"; namespace schema, instead.)
> >
> > 
> >   
> >>  type="baselineItemDataSegment
> >  minOccurs="0"/>
> >>  

Re: [axis2] WSDL2JAVA with XMLBean binding does not create instance of the derived type

[Bo Xie]

Hi Ramesh,

Sorry to get back on this late.

I noticed that the same code behave differently when invoked standalone(from
main()), or from the service.


From standalone, the xsi:type are in the XML properly(same as your test).

While from service, the xsi:type attribute are missing. Please see attached
file test program. They are calling the same method(populateAddress().

I am just wondering if there is any setting on the service side that may
influence the generation of the xsi:type?

Below are the XML output from two cases and the populateAddress method.

Thanks,
-Bo

XML dump  when running from main(). xsi:type is generated.

http://quickstart.samples/xsd";>
   http://www.w3.org/2001/XMLSchema-instance";>
   Sunnyvale
   XYZ
   CA
   94087
   
   http://www.w3.org/2001/XMLSchema-instance";>
   Hongkong
   XYZ
   2300331 E.C
   


XML dump when running as service. xsi:type is missing.

http://quickstart.samples/xsd";>
   
   Sunnyvale
   XYZ
   CA
   94087
   
   
   Hongkong
   XYZ
   2300331 E.C
   


The populateAddress method.

private static void populateAddress(GetAddressesResponseDocument resDoc) {
   // TODO Auto-generated method stub
   GetAddressesResponseDocument.GetAddressesResponse res =
   resDoc.addNewGetAddressesResponse();
   samples.quickstart.service.xmlbeans.xsd.Address[] addArray = new
samples.quickstart.service.xmlbeans.xsd.Address[2];
   samples.quickstart.service.xmlbeans.xsd.USAddress addr =
samples.quickstart.service.xmlbeans.xsd.USAddress.Factory.newInstance();

   //samples.quickstart.service.xmlbeans.xsd.USAddress addr =
samples.quickstart.service.xmlbeans.xsd.USAddress.Factory.newInstance();
   addr.setName("XYZ");
   addr.setCity("Sunnyvale");
   addr.setState(USState.CA);
   addr.setZip(new BigInteger("94087"));


   //samples.quickstart.service.xmlbeans.xsd.EUAddress addr1 =
(EUAddress) res.addNewAddresses().changeType(EUAddress.type);
   samples.quickstart.service.xmlbeans.xsd.EUAddress addr1 =
samples.quickstart.service.xmlbeans.xsd.EUAddress.Factory.newInstance();
   addr1.setName("XYZ");
   addr1.setCity("Hongkong");
   addr1.setExportCode(new BigInteger("66553322"));
   addr1.setPostcode("2300331 E.C");

   addArray[0] = addr;
   addArray[1] = addr1;

   res.setAddressesArray(addArray);

   XmlOptions ops = new XmlOptions();
   ops.setSavePrettyPrint();
   ops.setSavePrettyPrintIndent(4);
   //String xmlStr = res.xmlText(ops);
   //System.out.println("Response Element String: \n" + xmlStr);
   String xmlStr1 = resDoc.xmlText(ops);
   System.out.println("Response Document String: \n" + xmlStr1);
   }



On 1/8/07, Ramesh Gurunathan <[EMAIL PROTECTED]> wrote:


Hi Bo,

Sorry for getting back so late. I missed your mail from my email pool.

I indeed used axis2 1.1 and with xbean-2.2.0.jar that is shipped with
the release. This is what I did to prove that polymorphism in XML
works. My schema defines three complex types - BaseAddress, USAddress,
and UKAddress. The second item extends first and the third item
extends second. There is an element called 'UpdateCustomerAddress'
that includes, by signature, type BaseAddress unbounded. The element
could be used in the WSDL messages, but I didn't want go there.

Now I complied the schema using the schema compiler tool from XML
beans. (It makes no difference whether you use WSDL2Java of axis2 or
directly compile using scomp of XML beans).

I then wrote a test class, which uses the XML beans classes generated
classes, to verify the runtime object type for the address property in
UpdateCustomerAddress document. Please refer to the attachment for the
schema and test class.

In essence, the test class creates an XML programmatically, which
contains a BaseAddress, an USAddress, and UKAddress all bound to the
addresses property. Then it dumps the objects into XML, re-parses it,
and examines the objects using instanceof operator to ensure that the
types are correctly created. The test output is also in the
attachment.

TIP: I am not sure if this is significant, but ensure that your
schema's elementFormDefault is "qualified"

I hope this helps you.

Ramesh

On 1/9/07, Bo Xie <[EMAIL PROTECTED]> wrote:
> Hi Ramesh,
>
>  Did you by any chance use Axis2 1.1.1 instead of 1.1 for your
testing?
> If you indeed used 1.1 only, can you give some details on how did you
test
> the instanceof? BTW, I opened AXIS2-1938 for this issue before saw your
last
> reply.
>
>  Thanks,
>  -Bo
>
>
> On 1/5/07, Bo Xie <[EMAIL PROTECTED]> wrote:
> > Hi Ramesh,
> >
> > It is comforting to know it actually works. Thanks for trying it
out.
> >
> > I was using axis2. 1.1 and I just reinstall the axis2 1.1 and
tried it
> again, still get the same problem. I have two question.
> > 1. When you mentioned XML Bean 2.2.0, it is the one
xbean-2.2.0.jar
> comes with the axis2 package, not an out

RE: Axis2 1.1.1 with XMLBeans as the Data binding framework.

[Sriram Vaidyanathan]

Hi Paul,
  I have raised a JIRA for the issue 
(https://issues.apache.org/jira/browse/AXIS2-1993)

Thanks,
Sriram Vaidyanathan
Software Engineer - Java
Copart Auto Auctions, Inc.
4665 Business Center Drive
Fairfield, CA 94534
www.copart.com  
(707) 639-5248

-Original Message-
From: Paul Fremantle [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 17, 2007 1:38 AM
To: axis-user@ws.apache.org
Subject: Re: Axis2 1.1.1 with XMLBeans as the Data binding framework.

Sriram

Please can you raise a JIRA?

Paul

On 1/17/07, Sriram Vaidyanathan <[EMAIL PROTECTED]> wrote:
> Paul,
>  I switched from Axis2 1.1.1 to Axis21.1 and tried to build with the 
> xsd:include and it worked without any issues. So this seems to be a problem 
> with Axis2 1.1.1. So should a JIRA be filed this in Axis2 1.1.1?
>
> Also, if I go ahead and upgrade to Axis2 1.1 instead of Axis2 1.1.1 for my 
> project, are there any issues with 1.1 that I need to be aware of before 
> making the upgrade.
>
> Appreciate your help so far. Thanks.
>
> Thanks,
> Sriram Vaidyanathan
> Software Engineer - Java
> Copart Auto Auctions, Inc.
> 4665 Business Center Drive
> Fairfield, CA 94534
> www.copart.com 
> (707) 639-5248
>
> -Original Message-
> From: Paul Fremantle [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, January 16, 2007 10:11 PM
> To: axis-user@ws.apache.org
> Subject: Re: Axis2 1.1.1 with XMLBeans as the Data binding framework.
>
> Sriram
>
> You are right. I managed to recreate your problem. I think there is a
> bug in the XMLBeans databinding.
>
> Try using xsd:import instead of include:
>
>  namespace="http://www.sample.com/test"; />
>
> Paul
>
> On 1/17/07, Sriram Vaidyanathan <[EMAIL PROTECTED]> wrote:
> > Hi Paul,
> >
> > Thanks for the response.
> >
> > If I remove the SampleService.xsd from the folder, then I get the expection 
> > as you posted.  See [1] below.
> >
> > But if I have the file present, then I get a different version of the same 
> > exception. See [2] below.  So, I am wondering if I have the file present, 
> > is it hiding some other problem. ?
> >
> >
> >
> >
> > [1]
> > Running AXIS Tool WSDL2Java with Axis2 Home as  C:\axis2-1.1.1
> >[delete] Deleting directory C:\cvs\aps\cieca\wsdl\xmlbeans_gen_src
> >  [java] Retrieving schema at 'SampleService.xsd', relative to 
> > 'file:/C:/cvs/aps/sample/wsdl/src/main/config/'.
> >  [java] Exception in thread "main" 
> > org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL
> >  [java] at 
> > org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerationEngine.java:114)
> >  [java] at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32)
> >  [java] at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)
> >  [java] Caused by: javax.wsdl.WSDLException: WSDLException (at 
> > /wsdl:definitions/wsdl:types/xsd:schema[2]): faultCode=OTHER_ERROR: An 
> > error occurred trying to resolve schema referenced at 'SampleService.xsd', 
> > relative to 'file:/C:/cvs/aps/sample/wsdl/src/main/config/'.: 
> > java.io.FileNotFoundException: This file was not found: 
> > file:/C:/cvs/aps/sample/wsdl/src/main/config/SampleService.xsd
> >  [java] at com.ibm.wsdl.xml.WSDLReaderImpl.parseSchema(Unknown 
> > Source)
> >  [java] at com.ibm.wsdl.xml.WSDLReaderImpl.parseSchema(Unknown 
> > Source)
> >  [java] at com.ibm.wsdl.xml.WSDLReaderImpl.parseTypes(Unknown 
> > Source)
> >  [java] at com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(Unknown 
> > Source)
> >  [java] at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
> >  [java] at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
> >  [java] at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
> >  [java] at 
> > org.apache.axis2.wsdl.codegen.CodeGenerationEngine.readInTheWSDLFile(CodeGenerationEngine.java:276)
> >  [java] at 
> > org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerationEngine.java:97)
> >
> >
> > [2]
> >
> > [INFO] Executing tasks
> >  [echo] Running AXIS Tool WSDL2Java with Axis2 Home as  C:\axis2-1.1.1
> >[delete] Deleting directory C:\cvs\aps\sample\wsdl\xmlbeans_gen_src
> >  [java] Retrieving schema at 'SampleService.xsd', relative to 
> > 'file:/C:/cvs/aps/sample/wsdl/src/main/config/'.
> >  [java] Jan 16, 2007 9:31:48 PM 
> > org.apache.axis2.xmlbeans.CodeGenerationUtility$Axis2EntityResolver 
> > resolveEntity
> >  [java] INFO: Resolving schema with publicId [null] and systemId 
> > [\SampleService.xsd]
> >  [java] Exception in thread "main" 
> > org.apache.axis2.wsdl.codegen.CodeGenerationException: 
> > java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
> >  [java] at 
> > org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:224)
> >  [java] at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:

Re: wsdl2java generates incorrect/incomplete code

[R Bruce Hoffman]

Again, thank you so much for the effort and information.

What tool is it that you are using to validate this stuff? And, is it a
commercial product or open source tool?


On Wed, 2007-01-17 at 13:20 -0500, Anne Thomas Manes wrote:
> Bruce,
> 
> I took the WSDL file, commented out the imports, pasted the schemas
> inline, and validated the WSDL. I found one error:
> 
>There is no schema component of the name [ds:Signature] defined
>in the WSDL either via imported or embedded schema.
> 
> I don't understand why this error comes up, because as far as I can
> tell, the DSig namespace is properly imported, and certainly the
> Signature element is properly defined in the DSig namespace. I know
> that quite a few folks have experienced problems when trying to use
> the DSig namespace, so my guess is that many tools have trouble with
> the "#" in the namespace URI.
> 
> My tool also raised two warnings:
> 
>You have nested sequences (which should be okay)
>You have a maxOccurs attribute on an xsd:sequence declaration
>  (something to avoid)
> 
> Something else I noticed: The request and reply schemas do not specify
> elementFormDefault="qualified". This isn't an error, but it often
> causes interoperability errors.
> 
> But I reiterate my earlier comment. I strongly discourage you from
> defining headers in the WSDL. The WSDL represents the information that
> the application should be responsible for. Typically headers are added
> to the message and processed by the middleware, not by the
> application. Therefore the requirement for headers should be specified
> separately -- preferably using WS-Policy, even though it isn't final
> yet.
> 
> I also *strongly* recommend that you not define your own header
> formats, but rather that you conform to standard SOAP extensions -- in
> your case WS-Addressing and WS-Security. (You've used standard element
> definitions from WS-Addressing and XML Signature, but you haven't
> followed the standard header formats for using these elements.)
> 
> Axis2 can automatically manage WS-Addressing and WS-Security headers
> for you, and they will do so in an interoperable way. But you mustn't
> define the headers in the WSDL -- you must configure them in the
> config file.
> 
> Anne
> 
> On 1/17/07, R Bruce Hoffman <[EMAIL PROTECTED]> wrote:
> > First, let me sincerely thank you for your rapid response.
> >
> > I had originally questioned the other developers on that repeated import
> > of the namespace and been told it was ok. I probably have to be more
> > forceful when my gut says it's wrong... but, as you can probably tell, I
> > am new to this WSDL stuff.. previous services I have deployed were from
> > POJOs and not defined by or through WSDL, and I am no xml expert either.
> >
> > At least I have ammo to go back to them and have their manager apply the
> > "2 by 4" process...  ;-)
> >
> > Next here are the other two xsd's that I had left off.
> >
> > again, thanks.
> >
> >
> > On Wed, 2007-01-17 at 08:50 -0500, Anne Thomas Manes wrote:
> > > Bruce,
> > >
> > > Giving the WSDL a quick look, I noticed that it is not valid. I don't
> > > know if this is what's causing your problem, but it's a good place to
> > > start.
> > >
> > > In your WSDL  section, you attempt to import the same namespace
> > > twice. This is not allowed. If the namespace is defined in multiple
> > > schemas, and your goal is to import both schemas, then you must define
> > > a schema with the same target namespace and  the schemas
> > > into the namespace. e.g.:
> > >
> > > > >   xmlns:xs="http://www.w3.org/2001/XMLSchema";
> > >   elementFormDefault="qualified">
> > >> >   
> > > schemaLocation="1.0/receive-purchase-order-request.xsd"/>
> > >> >   
> > > schemaLocation="1.0/receive-purchase-order-reply.xsd"/>
> > >   
> > >
> > > Another error that I found: you must not specify the parameterOrder
> > > attribute in the  definition when using document
> > > style. (It is only used with RPC style.)
> > >
> > > As a general practice, it's a bad idea to define headers in your WSDL,
> > > especially if you are using standard headers. (The XMLBeans error
> > > indicates that you are using WS-Addressing and DSIG.) You should
> > > define your header requirements using WS-Policy and configuration
> > > files.
> > >
> > > Also, in regards to schema you did provide
> > > (targetNamespace="urn:/fih/purchase-order"), some best practices
> > > advice:
> > >
> > > - Avoid using anonymous types. Rather than defining structures as
> > > elements, define them as named types, and then define elements as
> > > those types. e.g.:
> > >
> > > Do this:
> > >
> > > 
> > >   
> > >> > minOccurs="0"/>
> > >> > minOccurs="0"/>
> > >   
> > >   
> > >   

RE: [AXIS 1.x - WSS4J] - HTTPs or Secure HTTP

[Alick Buckley]

 
I assume it does.
 
I am using Axis 1.4 and WSS4J v1.5.1 over HTTP protocol over TCP/IP sockets.
 
HTTPS is just is a secured layer over TCP/IP sockets ( SSL ) this is
independent of the data being sent over the connection.
 
SOAP protocol ---> HTTP protocol --> TCP/IP protocol >
 

-Original Message-
From: José Ferreiro [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 17 January 2007 7:20 PM
To: wss4j-dev@ws.apache.org; axis-user@ws.apache.org
Subject: [AXIS 1.x - WSS4J] - HTTPs or Secure HTTP


Hi!
Could someone tell me if HTTPs or Secure HTTP is supported by Axis 1.x and
WSS4J?

Thank you.

RE: [newbie] Can a POJO have IN-OUT arguments?

[Sullivan, David]

Thanks for the replies. We'll need to do just that. In our case we're
automating the creation of the service [with Axis2] and I was hoping
that there was a way to have the IN/OUT arguments (If used) and return
type (if used) automatically combined and defined in the WSDL Response.

We can add this feature if necessary, thanks.  

-Original Message-
From: Arnout Engelen [mailto:[EMAIL PROTECTED] 
Sent: Friday, January 12, 2007 3:17 PM
To: axis-user@ws.apache.org
Subject: Re: [newbie] Can a POJO have IN-OUT arguments?

Sullivan, David schreef:
>
> For example, I'd like to have a prototype that looks something like
this:
>
> public int copyWeather(Weather arg1, WeatherHolder arg2) {...}
>
Why not simply return a Weather POJO (or a POJO with a Weather and an
int)?


Arnout

-
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]

RE: Question axis 2 Java2WSDL tool

[Harish Hirasave]

Hi Anne,

I am using axis 2-1.1.1 and not axis 1.x. I am migrating from axis 1.2
to axis 2 -1.1.1. I did the following.

1. Created a Pojo
2. Generated a wsdl using Java2WSDL. This is where I am having problems
as axis 2 is generating request and response objects and not basic java
objects as parameters. The Java2WSDL tool does not have an option to
generate wsdl as unwrapped which I want as the client that uses my wsdl
is a non java client like php. 
3. Generated stub and skeleton using WSDL2Java. This has a -ur option
but does not seem to be working. 

Thanks
Harish

-Original Message-
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, January 16, 2007 8:03 PM
To: axis-user@ws.apache.org
Subject: Re: Question axis 2 Java2WSDL tool

In Axis 1.x, you must specify style="unwrapped" in the WSDD, or you
must ensure that the WSDL conforms to the wrapped doc/literal
convention.

On 1/16/07, Harish Hirasave <[EMAIL PROTECTED]> wrote:
> Hello Anne,
>
> I could not find this feature of automatic unwrapping. The Java2WSDL
and
> WSDL2Java in axis2-1.1.1 work in the same way as the axis2-1.1. The
code
> gets generated wrapped and I am unable to un wrap the classes and get
> return types as basic java objects. Please tell how this feature of
> unwrapping has been implemented and how to use it.
>
> Thanks
> Harish
>
> -Original Message-
> From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
> Sent: Friday, January 12, 2007 7:06 AM
> To: axis-user@ws.apache.org
> Subject: Re: Question axis 2 Java2WSDL tool
>
> Try using Axis2 1.1.1. What you're looking for is automatic
> "unwrapping" of the wrapper element, and that has only recently been
> implemented.
>
> Anne
>
> On 1/11/07, Harish Hirasave <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> >
> > I want document literal style but not wrapped. I am trying to
convert
> an
> > application from axis 1.2 to axis 2.1 and hence would like to use
> document
> > literal but I don't want the wrapper objects as the client that
would
> use
> > the service will not be a java client. Is there a way I can do this?
> >
> >
> >
> >  
> >
> >
> > From: Manoj Khangaonkar [mailto:[EMAIL PROTECTED]
> >  Sent: Thursday, January 11, 2007 3:18 PM
> >  To: axis-user@ws.apache.org
> >  Subject: Re: Question axis 2 Java2WSDL tool
> >
> >
> >
> >
> >
> > Harish,
> >
> >
> >
> >
> >
> > By default , AXIS2 java2WSDL generates what is called doc lit
wrapped
> style
> > WSDL.
> >
> >
> >
> >
> >
> > My guess is you want RPC lit style WSDL - like below
> >
> >
> >
> >
> >
> >  > name="getEligibleIVRPromotionsResponseMessage">
> >
> > 
> >
> > 
> >
> >
> > I think AXIS2 java2WSDL does not support this ( not 100% sure) ---
You
> might
> > want to try using the original AXIS java2WSDL - You typically pass
in
> the
> > WSDL
> >
> >
> > style as a command line parameter.
> >
> >
> >
> >
> >
> > In the original java2WSDL you could say java2WSDL -style rpc
> .
> >
> >
> >
> >
> >
> > in AXIS2 , you would java2WSDL -st  but I am not sure what the
> supported
> > values are.
> >
> >
> >
> >
> >
> > Mj
> >
> >
> >
> >
> >
> >
> > On 1/11/07, Harish Hirasave <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> > Hi,
> >
> >
> >
> > I have a pojo from which I am trying a generate a wsdl. The pojo has
> the
> > method
> >
> >
> >
> > public String getEligibleIVRPromotions(String phone)
> >
> > throws RemoteException
> >
> > {
> >
> > String errorMsg =
> > "IVRServiceSoapBindingImpl.getEligibleIVRPromotions(String):";
> >
> > String xml = null;
> >
> > return xml;
> >
> > }
> >
> >
> >
> > This method returns a String object.
> >
> >
> >
> > When I convert it to wsdl using the java2WSDL tool the wsdl method
> gets
> > generated with a getEligibleIVRPromotionsRequest Object as input and
> > getEligibleIVRPromotionsResponse Object as the return
> > object.
> >
> >
> >
> > How do I prevent this and  make the method return a String object
and
> not a
> > wrapper object getEligibleIVRPromotionsResponse? Attached
> > is the wsdl. Please help.
> >
> >
> >
> >
> >
> >
> >
> > Thanks
> >
> > Harish
> >
> >
> >
-
> >  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]
>
>
> -
> 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]


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

Re: wsdl2java generates incorrect/incomplete code

[Anne Thomas Manes]

Bruce,

I took the WSDL file, commented out the imports, pasted the schemas
inline, and validated the WSDL. I found one error:

  There is no schema component of the name [ds:Signature] defined
  in the WSDL either via imported or embedded schema.

I don't understand why this error comes up, because as far as I can
tell, the DSig namespace is properly imported, and certainly the
Signature element is properly defined in the DSig namespace. I know
that quite a few folks have experienced problems when trying to use
the DSig namespace, so my guess is that many tools have trouble with
the "#" in the namespace URI.

My tool also raised two warnings:

  You have nested sequences (which should be okay)
  You have a maxOccurs attribute on an xsd:sequence declaration
(something to avoid)

Something else I noticed: The request and reply schemas do not specify
elementFormDefault="qualified". This isn't an error, but it often
causes interoperability errors.

But I reiterate my earlier comment. I strongly discourage you from
defining headers in the WSDL. The WSDL represents the information that
the application should be responsible for. Typically headers are added
to the message and processed by the middleware, not by the
application. Therefore the requirement for headers should be specified
separately -- preferably using WS-Policy, even though it isn't final
yet.

I also *strongly* recommend that you not define your own header
formats, but rather that you conform to standard SOAP extensions -- in
your case WS-Addressing and WS-Security. (You've used standard element
definitions from WS-Addressing and XML Signature, but you haven't
followed the standard header formats for using these elements.)

Axis2 can automatically manage WS-Addressing and WS-Security headers
for you, and they will do so in an interoperable way. But you mustn't
define the headers in the WSDL -- you must configure them in the
config file.

Anne

On 1/17/07, R Bruce Hoffman <[EMAIL PROTECTED]> wrote:

First, let me sincerely thank you for your rapid response.

I had originally questioned the other developers on that repeated import
of the namespace and been told it was ok. I probably have to be more
forceful when my gut says it's wrong... but, as you can probably tell, I
am new to this WSDL stuff.. previous services I have deployed were from
POJOs and not defined by or through WSDL, and I am no xml expert either.

At least I have ammo to go back to them and have their manager apply the
"2 by 4" process...  ;-)

Next here are the other two xsd's that I had left off.

again, thanks.


On Wed, 2007-01-17 at 08:50 -0500, Anne Thomas Manes wrote:
> Bruce,
>
> Giving the WSDL a quick look, I noticed that it is not valid. I don't
> know if this is what's causing your problem, but it's a good place to
> start.
>
> In your WSDL  section, you attempt to import the same namespace
> twice. This is not allowed. If the namespace is defined in multiple
> schemas, and your goal is to import both schemas, then you must define
> a schema with the same target namespace and  the schemas
> into the namespace. e.g.:
>
>   xmlns:xs="http://www.w3.org/2001/XMLSchema";
>   elementFormDefault="qualified">
>  
schemaLocation="1.0/receive-purchase-order-request.xsd"/>
>  schemaLocation="1.0/receive-purchase-order-reply.xsd"/>
>   
>
> Another error that I found: you must not specify the parameterOrder
> attribute in the  definition when using document
> style. (It is only used with RPC style.)
>
> As a general practice, it's a bad idea to define headers in your WSDL,
> especially if you are using standard headers. (The XMLBeans error
> indicates that you are using WS-Addressing and DSIG.) You should
> define your header requirements using WS-Policy and configuration
> files.
>
> Also, in regards to schema you did provide
> (targetNamespace="urn:/fih/purchase-order"), some best practices
> advice:
>
> - Avoid using anonymous types. Rather than defining structures as
> elements, define them as named types, and then define elements as
> those types. e.g.:
>
> Do this:
>
> 
>   
>   
>   
>   
>   
> 
>
> Rather than this:
>
>   
>   
>   
>   
>   
>   
>   
>   
>
> And I recommend being cautious about defining each element as a global
> element. The only elements that really should be defined as global
> elements are those elements that will be the root of a document. i.e,
> rather than defining "BaselineItemDataSegment" as a gloal element and
> referencing it from the type definition, define the element within the
> type definition and reference its type, e.g.:
>
>
> We also need to see the "u

SOAP11, SCHEMA_1999

[M.Zdila/EpiSoftware Ltd.]

Hello

I've googled, but found nothing :-(

I need to communicate with client's web service that supports SOAP 1.1, schema 
version 1999. What I need to achieve is to serialize base64 data as 
xsi:type="SOAP-ENC:base64" but unfortunately the request still contains 
xsi:type="soapenc:base64Binary".

I am using spring remoting with following handler with no help:

import javax.xml.namespace.QName;
import javax.xml.rpc.handler.GenericHandler;
import javax.xml.rpc.handler.MessageContext;

import org.apache.axis.Constants;
import org.apache.axis.schema.SchemaVersion;

public class MyHandler extends GenericHandler {

  @Override
  public QName[] getHeaders() {
return null;
  }

  @Override
  public boolean handleRequest(MessageContext context) {
((org.apache.axis.MessageContext) 
context).setSchemaVersion(SchemaVersion.SCHEMA_1999);
((org.apache.axis.MessageContext) 
context).setEncodingStyle(Constants.URI_SOAP11_ENC);
return true;
// return super.handleRequest(context);
  }
  
}

Thanks in advance!

-- 
Martin Zdila
Analyst/Developer

EpiSoftware Slovakia Ltd.
Letna 27, 043 14 Kosice

tel:+421-908-363-848
tel:+421-55-6770-420
mailto:[EMAIL PROTECTED]
http://www.episoftware.com
xmpp:[EMAIL PROTECTED]
callto://m.zdila/

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

Re: Help defining fault

[Javier Kohen]

El mié, 17-01-2007 a las 12:33 -0500, Anne Thomas Manes escribió:
> Note that a faultcode value does not need to be defined as an element.
> The value is defined as a QName, but you don't have to define an
> element for it. What you need to do is define the MyElement element,
> and that's the element that you must reference from the 
> definition.

Could you please show me a valid WSDL/XSD fragment for the message I
provided?

My first approach did involve referencing the MyElement element directly
from the part, but it didn't seem to work (unfortunately I don't recall
the details).

I found little to no examples online involving non-standard fault codes,
so I'm pretty lost. I have written a few large WSDLs from message-data
and this is the last remaining itch.

Thanks for your time,
> On 1/17/07, Javier Kohen <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > I need help defining the WSDL for the following fault message. Note that
> > AuthenticationFailed has no namespace prefix, but MyElement does:
> > 
> >   AuthenticationFailed
> >   Authentication Failed
> >   
> > new auth token
> >   
> > 
> >
> > The best I could come up with was the following, but it doesn't qualify
> > MyElement properly, as it ends up with an empty namespace:
> >
> > 
> > 
> > 
> >
> > Then:
> > 
> > 
> > 
> > 
> > 
> >
> >
> > Thanks for your attention,
> > --
> > Javier Kohen <[EMAIL PROTECTED]>
> > ICQ: blashyrkh #2361802
> > Jabber: [EMAIL PROTECTED]
> >
> >
> >
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]

-- 
Javier Kohen <[EMAIL PROTECTED]>
ICQ: blashyrkh #2361802
Jabber: [EMAIL PROTECTED]


signature.asc
Description: Esta parte del mensaje está firmada	digitalmente

error in generated classes in axis2 1.1.1

[emerson cargnin]

I just generated the stub using axis2 1.1.1

In some classes generated, im getting the error "The field parentQName
is defined in an inherited type and an enclosing scope". I used the
option u (Unpacks the databinding classes), the error is on these
classes.The error is always on any code that refers to "parentQName"
field.

Thanks very much
Emerson

example of the code generated:

  public org.apache.axiom.om.OMDataSource getOMDataSource(
   final javax.xml.namespace.QName parentQName,
   final org.apache.axiom.om.OMFactory factory){


   org.apache.axiom.om.OMDataSource dataSource =
  new
org.apache.axis2.databinding.ADBDataSource(this,parentQName){

public void serialize(
 javax.xml.stream.XMLStreamWriter
xmlWriter) throws javax.xml.stream.XMLStreamException {



   java.lang.String prefix = parentQName.getPrefix();

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

Re: Help defining fault

[Anne Thomas Manes]

Note that a faultcode value does not need to be defined as an element.
The value is defined as a QName, but you don't have to define an
element for it. What you need to do is define the MyElement element,
and that's the element that you must reference from the 
definition.

Anne

On 1/17/07, Javier Kohen <[EMAIL PROTECTED]> wrote:

Hi,

I need help defining the WSDL for the following fault message. Note that
AuthenticationFailed has no namespace prefix, but MyElement does:

  AuthenticationFailed
  Authentication Failed
  
new auth token
  


The best I could come up with was the following, but it doesn't qualify
MyElement properly, as it ends up with an empty namespace:





Then:







Thanks for your attention,
--
Javier Kohen <[EMAIL PROTECTED]>
ICQ: blashyrkh #2361802
Jabber: [EMAIL PROTECTED]





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

RE: Need help to get HTTP Header

[Gnanasekaran Vinayakamurthy]

Hi Thilina,

 Wonderful We got the Http Header values properly with the latest
nightly build fix..

Thanks for your speedy help

Thank you!


-Original Message-
From: Thilina Gunarathne [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, January 16, 2007 9:04 PM
To: axis-user@ws.apache.org
Cc: Gnanasekaran Vinayakamurthy
Subject: Re: Need help to get HTTP Header

Hi,
Thanx for logging the JIRA.
I've committed a fix yesterday afternoon (15 hours ago)..  Please try
the latest nightly  and let us know the feedback..

>And any help that you guys can provide
> on this front will go a long way to promoting the Axis2 in our
organization
Have Fun!!

Cheers,
Thilina
>
>
> -Original Message-
> From: Thilina Gunarathne [mailto:[EMAIL PROTECTED]
> Sent: Friday, January 12, 2007 8:23 PM
> To: axis-user@ws.apache.org
> Subject: Re: Need help to get HTTP Header
>
> Yes... IIRC I also witnessed the above behaviour... I'm currently
> doing a cleanup of the transports and  planning on fixing the above
> too...
>
> Please log a JIRA for the record purposes... So that we'll not forget
> it..:)
>
> Thanks,
> Thilina
>
> On 1/13/07, Gnanasekaran Vinayakamurthy
> <[EMAIL PROTECTED]> wrote:
> > Hi
> >
> > When I run axis2 client in debug mode, I could inspect the
msgcontext
> > object, which has Http header values as in the order of
> >
>
msgcontext-->operationContext-->properties-->TRANSPORT_IN-->AutoCloseInp
> >
>
utStream-->watcher-->HttpMethodBase-->responseHeaders(HeaderGroup)-->Hea
> > der
> >
> > And I think Transport Phase in Axis2 missed to parse the Http
> header(as
> > in above) from input stream and thus missed not setting property
> > TRANSPORT_HEADERS in msgContext.
> >
> > Is it a bug in axis2?
> >
> > Could any one please clarify?
> >
> >
> > Thanks,
> > Vinay
> >
> > -Original Message-
> > From: Deepal Jayasinghe [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, January 11, 2007 9:43 PM
> > To: axis-user@ws.apache.org
> > Subject: Re: Need help to get HTTP Header
> >
> > Hi Gnanasekaran ;
> >
> > In the server side you can get transport header from message context
> as
> > follows;
> > Map headers = (Map)
> > msgContext.getProperty(MessageContext.TRANSPORT_HEADERS);
> >
> > > Hi all,
> > >
> > > Is there any way where I can get response HTTP Header data in
Axis2?
> > >
> > > We are trying to get cookie from Http header, but no luck so
far
> > > we are getting header values from xml soap message only, but not
> able
> > > to get the HTTP Header.
> > >
> > > Below is the soap response from the server (captured using tcpmon)
> > >
> > >
> >
>

> > **
> > >
> > > HTTP/1.1 200 OK
> > >
> > > Date: Thu, 11 Jan 2007 18:21:34 GMT
> > >
> > > Server: Microsoft-IIS/6.0
> > >
> > > MicrosoftOfficeWebServer: 5.0_Pub
> > >
> > > X-Powered-By: ASP.NET
> > >
> > > X-AspNet-Version: 2.0.50727
> > >
> > > RSAuthenticationHeader: sqlAuthCookie
> > >
> > > Set-Cookie:
> > >
> >
>
sqlAuthCookie=2E4D80C2D790C877650865B5FCD3E0F1DCC565C68BCCB22B3167B7063C
> >
>
61CBB11ED07D75F85354C1E56F17B46E6F3246D97F202C53424CA028F8DE4421BE498173
> > FD58E42E8D2E55C3059167301E7E6C;
> > > path=/; HttpOnly
> > >
> > > Cache-Control: private, max-age=0
> > >
> > >
> > >
> > > Content-Type: text/xml; charset=utf-8
> > >
> > >
> > >
> > > Content-Length: 794
> > >
> > >
> > >
> > >
> > >
> >
> >
> >
> >
-
> > 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]
> >
> >
>
>
> --
> Thilina Gunarathne
> WSO2, Inc.; http://www.wso2.com/
> Home page: http://webservices.apache.org/~thilina/
> Blog: http://thilinag.blogspot.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]
>
>


-- 
Thilina Gunarathne
WSO2, Inc.; http://www.wso2.com/
Home page: http://webservices.apache.org/~thilina/
Blog: http://thilinag.blogspot.com/

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

Re: Array is not supported

[Anne Thomas Manes]

If you can't change the WSDL, then I suggest that you use Axis rather
than Axis2.
See http://ws.apache.org/axis/.

Anne

On 1/17/07, robert lazarski <[EMAIL PROTECTED]> wrote:

RPC/encoded is legacy and axis2 doesn't support it. Take a look at
this article for your other options:

http://www-128.ibm.com/developerworks/webservices/library/ws-whichwsdl/

HTH,
Robert

On 1/17/07, Jon Horsman <[EMAIL PROTECTED]> wrote:
> Hey All,
>
> I'm new to SOAP and axis, and am trying to come up to speed.  I have
> been given a wsdl file at work and have been told to investigate how
> we could build a web service around it with axis/java.
>
> So far everything is going ok until one of the wsdl files had an array
> in it.  I got the following error when trying to use wsdl2java
>
> Exception in thread "main"
> org.apache.axis2.wsdl.codegen.CodeGenerationException:
> java.lang.RuntimeException:
> java.lang.reflect.InvocationTargetException
> .
> .
> .
> Caused by: org.apache.axis2.schema.SchemaCompilationException:
> {http://schemas.xmlsoap.org/soap/encoding/}Array is not supported.
>
>
> I've done some googling and found "This is not a bug but a known
> restriction- we don't support SOAP Encoding style arrays."  Being new
> to SOAP i'm not sure exactly what this means.  The wsdl file i was
> given has lines like
>
>   
>
> 
>  
>maxOccurs="unbounded"/>
>  
>  
> 
>
>   
>
> Its obvious its the "SOAP-ENC:Array" that is causing this problem.
> This probably a stupid question, but is there another way to use
> arrays with axis, perhaps a non SOAP-ENC type?  How do people work
> around the need to use arrays?  I'm being pressed for time to give an
> an answer to "can we make this work?" and i'm not sure what that
> answer should be.
>
> Any help would be much appreciated.
>
> Jon.
>
> -
> 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]




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

Re: Do you know a tool to easily visualize a wsdl file ?

[ChadDavis]

Samy,

I think the DOM view offerd by MLVIEW is exactly what you show below.
Note: I sent a screen cap of the dom view of MLView to your email
address directly.  I didn't want to clog the bandwith of the list with
a pic.

ALso, I think many xml editors provide a similar DOM view.

Chad

On 1/17/07, Samy Mechiri <[EMAIL PROTECTED]> wrote:

I am on Windows/CygWin

I am not sure it is what I searching for.
I don't want a simple xml editor. What I want is really specific to wsdl
files.

The idea is to get rid of overload of all the xml grammar

An example of output would be:
"""
configureMyThing: 
-thingName: [xsd:string]
-thingConfig: [myns:ThingConfiguration]
-thingCount: [xsd:int]
-thingLinks: [xsd:string]
...
...
"""

There you see all the arguments of the functions are separated with
potentially the name of the argument and it's type (when type is not a
primitive it is also recursively detailed)


regards,

Samy MECHIRI - Software Engineer
KXEN - 92158 Suresnes CEDEX
FRANCE

-Original Message-
From: ChadDavis [mailto:[EMAIL PROTECTED]
Sent: mercredi 17 janvier 2007 17:18
To: axis-user@ws.apache.org
Subject: Re: Do you know a tool to easily visualize a wsdl file ?

What platform / os are you on?

On linux, I had trouble with several xml editors being able to handle
long wsdl's.  The best I'v found is called MLView.  I'm not sure its
what your looking for, in terms of graphical representation, but it is
super fast and represents the document as a DOM hieararchy, which makes
it very easy to see the various elements and regions of a wsdl.
Or you can view the document as the raw document but with element based
"code folding" which also makes it very easy to peruse lengthy
documents.



On 1/17/07, Samy Mechiri <[EMAIL PROTECTED]> wrote:
>
>
> Hi everyone,
>
> do you know any small, easily usable tool to visualize what operations

> (and their arguments) are available on a wsd file ?
>
> There seem to be nusoap having such a tool (i've read about it on
> http://www.xml.com/lpt/a/1388) but I could not find any reference to
> it on nusoap's web page.
>
> Ideally it would output the results as a txt or html file
>
> Thank you for reading.

-
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]




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

Re: Do you know a tool to easily visualize a wsdl file ?

[Jesús Daniel Blázquez Carazo]

You can use XML spy

- Original Message - 
From: "Samy Mechiri" <[EMAIL PROTECTED]>

To: 
Sent: Wednesday, January 17, 2007 5:38 PM
Subject: RE: Do you know a tool to easily visualize a wsdl file ?



I am on Windows/CygWin

I am not sure it is what I searching for.
I don't want a simple xml editor. What I want is really specific to wsdl
files.

The idea is to get rid of overload of all the xml grammar

An example of output would be:
"""
configureMyThing: 
-thingName: [xsd:string]
-thingConfig: [myns:ThingConfiguration]
-thingCount: [xsd:int]
-thingLinks: [xsd:string]
...
...
"""

There you see all the arguments of the functions are separated with
potentially the name of the argument and it's type (when type is not a
primitive it is also recursively detailed)


regards,

Samy MECHIRI - Software Engineer
KXEN - 92158 Suresnes CEDEX
FRANCE

-Original Message-
From: ChadDavis [mailto:[EMAIL PROTECTED] 
Sent: mercredi 17 janvier 2007 17:18

To: axis-user@ws.apache.org
Subject: Re: Do you know a tool to easily visualize a wsdl file ?

What platform / os are you on?

On linux, I had trouble with several xml editors being able to handle
long wsdl's.  The best I'v found is called MLView.  I'm not sure its
what your looking for, in terms of graphical representation, but it is
super fast and represents the document as a DOM hieararchy, which makes
it very easy to see the various elements and regions of a wsdl.
Or you can view the document as the raw document but with element based
"code folding" which also makes it very easy to peruse lengthy
documents.



On 1/17/07, Samy Mechiri <[EMAIL PROTECTED]> wrote:



Hi everyone,

do you know any small, easily usable tool to visualize what operations



(and their arguments) are available on a wsd file ?

There seem to be nusoap having such a tool (i've read about it on
http://www.xml.com/lpt/a/1388) but I could not find any reference to 
it on nusoap's web page.


Ideally it would output the results as a txt or html file

Thank you for reading.


-
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]



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

RE: Do you know a tool to easily visualize a wsdl file ?

[Samy Mechiri]

I am on Windows/CygWin

I am not sure it is what I searching for.
I don't want a simple xml editor. What I want is really specific to wsdl
files.

The idea is to get rid of overload of all the xml grammar

An example of output would be:
"""
configureMyThing: 
-thingName: [xsd:string]
-thingConfig: [myns:ThingConfiguration]
-thingCount: [xsd:int]
-thingLinks: [xsd:string]
...
...
"""

There you see all the arguments of the functions are separated with
potentially the name of the argument and it's type (when type is not a
primitive it is also recursively detailed)


regards,
 
Samy MECHIRI - Software Engineer
KXEN - 92158 Suresnes CEDEX
FRANCE

-Original Message-
From: ChadDavis [mailto:[EMAIL PROTECTED] 
Sent: mercredi 17 janvier 2007 17:18
To: axis-user@ws.apache.org
Subject: Re: Do you know a tool to easily visualize a wsdl file ?

What platform / os are you on?

On linux, I had trouble with several xml editors being able to handle
long wsdl's.  The best I'v found is called MLView.  I'm not sure its
what your looking for, in terms of graphical representation, but it is
super fast and represents the document as a DOM hieararchy, which makes
it very easy to see the various elements and regions of a wsdl.
Or you can view the document as the raw document but with element based
"code folding" which also makes it very easy to peruse lengthy
documents.



On 1/17/07, Samy Mechiri <[EMAIL PROTECTED]> wrote:
>
>
> Hi everyone,
>
> do you know any small, easily usable tool to visualize what operations

> (and their arguments) are available on a wsd file ?
>
> There seem to be nusoap having such a tool (i've read about it on
> http://www.xml.com/lpt/a/1388) but I could not find any reference to 
> it on nusoap's web page.
>
> Ideally it would output the results as a txt or html file
>
> Thank you for reading.

-
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]

Re: Array is not supported

[robert lazarski]

RPC/encoded is legacy and axis2 doesn't support it. Take a look at
this article for your other options:

http://www-128.ibm.com/developerworks/webservices/library/ws-whichwsdl/

HTH,
Robert

On 1/17/07, Jon Horsman <[EMAIL PROTECTED]> wrote:

Hey All,

I'm new to SOAP and axis, and am trying to come up to speed.  I have
been given a wsdl file at work and have been told to investigate how
we could build a web service around it with axis/java.

So far everything is going ok until one of the wsdl files had an array
in it.  I got the following error when trying to use wsdl2java

Exception in thread "main"
org.apache.axis2.wsdl.codegen.CodeGenerationException:
java.lang.RuntimeException:
java.lang.reflect.InvocationTargetException
.
.
.
Caused by: org.apache.axis2.schema.SchemaCompilationException:
{http://schemas.xmlsoap.org/soap/encoding/}Array is not supported.


I've done some googling and found "This is not a bug but a known
restriction- we don't support SOAP Encoding style arrays."  Being new
to SOAP i'm not sure exactly what this means.  The wsdl file i was
given has lines like

  
   

 
  
 
 

   
  

Its obvious its the "SOAP-ENC:Array" that is causing this problem.
This probably a stupid question, but is there another way to use
arrays with axis, perhaps a non SOAP-ENC type?  How do people work
around the need to use arrays?  I'm being pressed for time to give an
an answer to "can we make this work?" and i'm not sure what that
answer should be.

Any help would be much appreciated.

Jon.

-
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]

Array is not supported

[Jon Horsman]

Hey All,

I'm new to SOAP and axis, and am trying to come up to speed.  I have
been given a wsdl file at work and have been told to investigate how
we could build a web service around it with axis/java.

So far everything is going ok until one of the wsdl files had an array
in it.  I got the following error when trying to use wsdl2java

Exception in thread "main"
org.apache.axis2.wsdl.codegen.CodeGenerationException:
java.lang.RuntimeException:
java.lang.reflect.InvocationTargetException
.
.
.
Caused by: org.apache.axis2.schema.SchemaCompilationException:
{http://schemas.xmlsoap.org/soap/encoding/}Array is not supported.


I've done some googling and found "This is not a bug but a known
restriction- we don't support SOAP Encoding style arrays."  Being new
to SOAP i'm not sure exactly what this means.  The wsdl file i was
given has lines like

 
  
   

 


   
  
 

Its obvious its the "SOAP-ENC:Array" that is causing this problem.
This probably a stupid question, but is there another way to use
arrays with axis, perhaps a non SOAP-ENC type?  How do people work
around the need to use arrays?  I'm being pressed for time to give an
an answer to "can we make this work?" and i'm not sure what that
answer should be.

Any help would be much appreciated.

Jon.

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

Re: Do you know a tool to easily visualize a wsdl file ?

[ChadDavis]

What platform / os are you on?

On linux, I had trouble with several xml editors being able to handle
long wsdl's.  The best I'v found is called MLView.  I'm not sure its
what your looking for, in terms of graphical representation, but it is
super fast and represents the document as a DOM hieararchy, which
makes it very easy to see the various elements and regions of a wsdl.
Or you can view the document as the raw document but with element
based "code folding" which also makes it very easy to peruse lengthy
documents.



On 1/17/07, Samy Mechiri <[EMAIL PROTECTED]> wrote:



Hi everyone,

do you know any small, easily usable tool to visualize what operations (and
their arguments) are available on a wsd file ?

There seem to be nusoap having such a tool (i've read about it on
http://www.xml.com/lpt/a/1388) but I could not find any reference to it on
nusoap's web page.

Ideally it would output the results as a txt or html file

Thank you for reading.


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

[Axis2] RE:RE: RE: Axis2 1.2 release plan

[falom]

Hi Paul,

BTW, I've also tried to change the jms axis2.xml config to use geronimo's 
org.activemq.jndi.ActiveMQInitialContextFactory instead of 
org.apache.activemq.jndi.ActiveMQInitialContextFactory, i got same noclassfound 
exception.

falom

falom <[EMAIL PROTECTED]> wrote： Hi Paul,

I installed axis2 war in both tomcat and geronimo.

First I managed to test axis2 jms transport in tomcat connecting to standalone 
activemq broker by deploying one service using servicelifecycle to start up the 
jmslistener. 

BUT when i deploy the same service in geronimo, while trying connect to the 
activemq broker within geronimo, i got following exception attached, seems like 
problem related to classloader, or something else which i am really stuck 
with(BTW, i have put necessary activemq jars in every possible folders i can 
think of under geronimo and axis2 war, same exception all the time), please 
help! 

Also I'd very much like to look more into Synapse and related jms soap samples, 
which i know is a more robust pattern to bridge jms and web services. But i 
need to first solve this problem in geronimo first.

falom

22:46:30,709 INFO  [JMSActiveEchoServiceLifeCycle] 
JMSActiveEchoServiceLifeCycle startUp  called.
22:46:30,719 ERROR [JMSListener] Error connecting to JMS connection factory : 
TopicConnectionFactory
javax.naming.NoInitialContextException: Cannot instantiate class: 
org.apache.activemq.jndi.ActiveMQInitialContextFactory [Root exception is 
java.lang.ClassNotFoundException: 
org.apache.activemq.jndi.ActiveMQInitialContextFactory in classloader 
default/axis211/1164548268298/war]
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:657)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.(InitialContext.java:197)
at 
org.apache.axis2.transport.jms.JMSConnectionFactory.createInitialContext(JMSConnectionFactory.java:133)
at  
org.apache.axis2.transport.jms.JMSConnectionFactory.connect(JMSConnectionFactory.java:122)
at 
org.apache.axis2.transport.jms.JMSListener.initializeConnectionFactories(JMSListener.java:244)
at org.apache.axis2.transport.jms.JMSListener.init(JMSListener.java:104)
at 
org.apache.axis2.jms2.JMSActiveEchoServiceLifeCycle.startUp(JMSActiveEchoServiceLifeCycle.java:56)
at 
org.apache.axis2.deployment.ServiceBuilder.loadServiceLifeCycleClass(ServiceBuilder.java:354)
at 
org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:136)
at 
org.apache.axis2.deployment.repository.util.ArchiveReader.buildServiceGroup(ArchiveReader.java:91)
at 
org.apache.axis2.deployment.repository.util.ArchiveReader.processServiceGroup(ArchiveReader.java:133)
at  
org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:528)
at 
org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:196)
at 
org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:227)
at 
org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:174)
at 
org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:88)
at 
org.apache.axis2.deployment.WarBasedAxisConfigurator.loadServices(WarBasedAxisConfigurator.java:252)
at 
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:72)
at 
org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:373)
at  org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:317)
at 
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1105)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:932)
at 
org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3915)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4176)
at 
org.apache.geronimo.tomcat.GeronimoStandardContext.access$201(GeronimoStandardContext.java:67)
at 
org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:337)
at 
org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:31)
at  
org.apache.geronimo.tomcat.GeronimoStandardContext.start(GeronimoStandardContext.java:192)
at 
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
at 
org.apache.geronimo.tomcat.TomcatContainer.addContext(TomcatContainer.java:313)
at 
org.apache.geronimo.tomcat.TomcatContainer$$FastClassByCGLIB$$9370b073.invoke()
at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
at 
org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastM

Help defining fault

[Javier Kohen]

Hi,

I need help defining the WSDL for the following fault message. Note that
AuthenticationFailed has no namespace prefix, but MyElement does:

  AuthenticationFailed
  Authentication Failed
  
new auth token
  


The best I could come up with was the following, but it doesn't qualify
MyElement properly, as it ends up with an empty namespace:





Then:







Thanks for your attention,
-- 
Javier Kohen <[EMAIL PROTECTED]>
ICQ: blashyrkh #2361802
Jabber: [EMAIL PROTECTED]


signature.asc
Description: Esta parte del mensaje está firmada	digitalmente

[Axis2] RE: RE: Axis2 1.2 release plan

[falom]

Hi Paul,

I installed axis2 war in both tomcat and geronimo.

First I managed to test axis2 jms transport in tomcat connecting to standalone 
activemq broker by deploying one service using servicelifecycle to start up the 
jmslistener. 

BUT when i deploy the same service in geronimo, while trying connect to the 
activemq broker within geronimo, i got following exception attached, seems like 
problem related to classloader, or something else which i am really stuck 
with(BTW, i have put necessary activemq jars in every possible folders i can 
think of under geronimo and axis2 war, same exception all the time), please 
help! 

Also I'd very much like to look more into Synapse and related jms soap samples, 
which i know is a more robust pattern to bridge jms and web services. But i 
need to first solve this problem in geronimo first.

falom

22:46:30,709 INFO  [JMSActiveEchoServiceLifeCycle] 
JMSActiveEchoServiceLifeCycle startUp called.
22:46:30,719 ERROR [JMSListener] Error connecting to JMS connection factory : 
TopicConnectionFactory
javax.naming.NoInitialContextException: Cannot instantiate class: 
org.apache.activemq.jndi.ActiveMQInitialContextFactory [Root exception is 
java.lang.ClassNotFoundException: 
org.apache.activemq.jndi.ActiveMQInitialContextFactory in classloader 
default/axis211/1164548268298/war]
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:657)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.(InitialContext.java:197)
at 
org.apache.axis2.transport.jms.JMSConnectionFactory.createInitialContext(JMSConnectionFactory.java:133)
at 
org.apache.axis2.transport.jms.JMSConnectionFactory.connect(JMSConnectionFactory.java:122)
at 
org.apache.axis2.transport.jms.JMSListener.initializeConnectionFactories(JMSListener.java:244)
at org.apache.axis2.transport.jms.JMSListener.init(JMSListener.java:104)
at 
org.apache.axis2.jms2.JMSActiveEchoServiceLifeCycle.startUp(JMSActiveEchoServiceLifeCycle.java:56)
at 
org.apache.axis2.deployment.ServiceBuilder.loadServiceLifeCycleClass(ServiceBuilder.java:354)
at 
org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:136)
at 
org.apache.axis2.deployment.repository.util.ArchiveReader.buildServiceGroup(ArchiveReader.java:91)
at 
org.apache.axis2.deployment.repository.util.ArchiveReader.processServiceGroup(ArchiveReader.java:133)
at 
org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:528)
at 
org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:196)
at 
org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:227)
at 
org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:174)
at 
org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:88)
at 
org.apache.axis2.deployment.WarBasedAxisConfigurator.loadServices(WarBasedAxisConfigurator.java:252)
at 
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:72)
at 
org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:373)
at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:317)
at 
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1105)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:932)
at 
org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3915)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4176)
at 
org.apache.geronimo.tomcat.GeronimoStandardContext.access$201(GeronimoStandardContext.java:67)
at 
org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:337)
at 
org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:31)
at 
org.apache.geronimo.tomcat.GeronimoStandardContext.start(GeronimoStandardContext.java:192)
at 
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
at 
org.apache.geronimo.tomcat.TomcatContainer.addContext(TomcatContainer.java:313)
at 
org.apache.geronimo.tomcat.TomcatContainer$$FastClassByCGLIB$$9370b073.invoke()
at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
at 
org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
at 
org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:122)
at 
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:817)
at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57)
at

Migrating from Axis 1 to Axis 2 (client side) with programmatic WSDL parsing

[Nick Haines]

Hi,

 

I'm currently upgrading some code from Axis 1 to Axis 2, and am having
problems matching some of the functionality in Axis 1 with Axis2.  

I've had a look in the documentation and not found anything so far as it
seems we are in a minority using it this way.

 

We currently make WebService calls using the Service object initially -
it allows you to pass in a WSDL, and it creates the equivalent of an
EndpointReference etc.

In Axis2 there seems to be no way of doing this, do I need to do the
parsing myself?

 

We also use the Call.invoke mechanism which takes Objects as parameters
to the WebService and returns the result as an Object. 

So far in Axis2 it seems as though I will have to create the section
ourselves using the OM.  That's fine except it means writing Java->XML
data mappings unless I'm missing something obvious?

Is there some standard way to do this that I have overlooked?

 

Thanks in advance for the help, and apologies if I've missed answers to
this anywhere, I have searched and failed miserably!

 

Nick

 

 

 

 

Re: [Axis2] Session Management and WS-Addressing

[Brian De Pradine]

Hello,

You may find the following link useful, [1]

[1]  http://www.developer.com/java/web/article.php/3620661

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319 Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?


"Tim, Jane and Chelsea Johnson" <[EMAIL PROTECTED]> wrote on 17/01/2007 
00:54:12:

> I am running the latest version of axis2 - 1.1.1. I am trying to use 
session 
> management via WS-Addressing.
> In soapmonitor I can see the WS-Addressing headers going out on the 
request 
> to the server. But my service's response doesn't have any of the 
> WS-Addressing headers (specifically the groupID header). Addressing is 
> enabled globally via the entry in Axis2.xml. In service.xml I set scope 
for 
> the service to be "soapsession".
> 
> This is what the client is sending. Is there something I need to add or 
> change to get the service to re-act with WS-Addressing headers.
> 
> 
> http://www.w3.org/2005/08/addressing"; 
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
>   
> http://localhost:8080/axis2/services/AiMessageServices
> 
>   http://www.w3.
> org/2005/08/addressing/anonymous
> 
> urn:uuid:F18B205BFF468A597911689950656872
> urn:login
>   
>   
> 
>   124
>   2567
>   SJPC120.y
>   2003
> 
>   
>  
> 
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

[Axis2] In-container testing

[Angel Todorov]

Hi,

Has anyone performed in-container testing for Axis2? Currently all the
JUnit tests that axis2 includes are executed on the client side and
don't share a common runtime. Is there any existing framework for
in-container testing of Axis2? I looked at Jakarta Cactus, but haven't
estimated yet what the effort would be to port the existing axis2
tests to it . Thanks

Regards,
Angel

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

Re: wsdl2java generates incorrect/incomplete code

[R Bruce Hoffman]

First, let me sincerely thank you for your rapid response.

I had originally questioned the other developers on that repeated import
of the namespace and been told it was ok. I probably have to be more
forceful when my gut says it's wrong... but, as you can probably tell, I
am new to this WSDL stuff.. previous services I have deployed were from
POJOs and not defined by or through WSDL, and I am no xml expert either.

At least I have ammo to go back to them and have their manager apply the
"2 by 4" process...  ;-)

Next here are the other two xsd's that I had left off.

again, thanks.


On Wed, 2007-01-17 at 08:50 -0500, Anne Thomas Manes wrote:
> Bruce,
> 
> Giving the WSDL a quick look, I noticed that it is not valid. I don't
> know if this is what's causing your problem, but it's a good place to
> start.
> 
> In your WSDL  section, you attempt to import the same namespace
> twice. This is not allowed. If the namespace is defined in multiple
> schemas, and your goal is to import both schemas, then you must define
> a schema with the same target namespace and  the schemas
> into the namespace. e.g.:
> 
>   xmlns:xs="http://www.w3.org/2001/XMLSchema";
>   elementFormDefault="qualified">
>  
> schemaLocation="1.0/receive-purchase-order-request.xsd"/>
>  schemaLocation="1.0/receive-purchase-order-reply.xsd"/>
>   
> 
> Another error that I found: you must not specify the parameterOrder
> attribute in the  definition when using document
> style. (It is only used with RPC style.)
> 
> As a general practice, it's a bad idea to define headers in your WSDL,
> especially if you are using standard headers. (The XMLBeans error
> indicates that you are using WS-Addressing and DSIG.) You should
> define your header requirements using WS-Policy and configuration
> files.
> 
> Also, in regards to schema you did provide
> (targetNamespace="urn:/fih/purchase-order"), some best practices
> advice:
> 
> - Avoid using anonymous types. Rather than defining structures as
> elements, define them as named types, and then define elements as
> those types. e.g.:
> 
> Do this:
> 
> 
>   
>minOccurs="0"/>
>minOccurs="0"/>
>   
>   
> 
> 
> Rather than this:
> 
>   
>   
>   
>minOccurs="0"/>
>ref="ReferenceIdentificationSegment" minOccurs="0"/>
>   
>   
>   
> 
> And I recommend being cautious about defining each element as a global
> element. The only elements that really should be defined as global
> elements are those elements that will be the root of a document. i.e,
> rather than defining "BaselineItemDataSegment" as a gloal element and
> referencing it from the type definition, define the element within the
> type definition and reference its type, e.g.:
> 
> 
> We also need to see the "unr:/fih/c-efm/purchase-order/1.0" schema files.
> (You sent us the "http://www.fih.org/XML/WD0"; namespace schema, instead.)
> 
> 
>   
> type="baselineItemDataSegment
>  minOccurs="0"/>
> type="referenceIdentificationSegment"
>  minOccurs="0"/>
>   
>   
> 
> Anne
> 
> On 1/17/07, R Bruce Hoffman <[EMAIL PROTECTED]> wrote:
> > Sure... sorry.
> >
> > Also, when using xmlbeans binding, I get the following error:
> >
> >  Using AXIS2_HOME:   /usr/local/axis2
> >  Using JAVA_HOME:   /usr/lib/jvm/java-1.5.0-sun
> > Retrieving schema at '../../../../fih/1.0/fih-header.xsd', relative to
> > 'file:/home/hoffmanb/ax/wsdl/fih/c-efm/purchase-order/receive-purchase-order/'.
> > Retrieving schema at
> > 'http://www.w3.org/TR/2002/REC-xmldsig-core-20020212/xmldsig-core-schema.xsd',
> >  relative to 'file:/home/hoffmanb/ax/wsdl/fih/1.0/fih-header.xsd'.
> > Retrieving schema at
> > 'http://schemas.xmlsoap.org/ws/2004/08/addressing/', relative to
> > 'file:/home/hoffmanb/ax/wsdl/fih/1.0/fih-header.xsd'.
> > Retrieving schema at '1.0/receive-purchase-order-request.xsd', relative
> > to
> > 'file:/home/hoffmanb/ax/wsdl/fih/c-efm/purchase-order/receive-purchase-order/'.
> > Retrieving schema at 'LimitedPurchaseOrder.xsd', relative to
> > 'file:/home/hoffmanb/ax/wsdl/fih/c-efm/purchase-order/receive-purchase-order/1.0/receive-purchase-order-request.xsd'.
> > Retrieving schema at '1.0/receive-purchase-order-reply.xsd', relative to
> > 'file:/home/hoffmanb/ax/wsdl/fih/c-efm/purchase-order/receive-purchase-order/'.
> > Jan 16, 2007 1:39:58 PM org.apache.axis2.xmlbeans.CodeGenerationUtility
> > $Axis2EntityResolver resolveEntity
> > INFO: Resolving schema with publicId [urn:/fih/1.0] and systemId
> > [/fih/1.0/fih-header.xsd]
> > Jan 16, 200

Re: Sending MTOM attachments from Axis2 client

[Nathan Kuroczycki]

Angel,

I observed that behaviour using TCPMon.

Nathan


On 1/17/07, Angel Todorov <[EMAIL PROTECTED]> wrote:


Hi,

where do you observe that behavior ? Via the soap monitor or by using
a TCP (HTTP more specifically) sniffer ? Normally to see if MTOM is
working you should use some TCP monitor, soap monitor or any other
soap message monitor won't help you.

--Angel

On 1/17/07, Nathan Kuroczycki <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I am trying to send the request XML with the binary within an MTOM
> attachment. However, the code below sends the binary inline with the
rest of
> the xml request. My understanding from the Axis2 examples is that by
> enabling MTOM, the binary will be sent as a referenced attachment. Is
there
> something that I'm not doing?
>
> Thanks,
> Nathan
>
>
> ServiceClient service = new ServiceClient();
>
>
>
> Options options = new Options();
>
> options.setTo(new EndpointReference(URL));
>
> options.setAction("urn:update");
>
> options.setProperty(Constants.Configuration.ENABLE_MTOM,
> Constants.VALUE_TRUE );
>
> service.setOptions(options);
>
>
>
> try {
>
>
>
> OMFactory fac = OMAbstractFactory.getOMFactory();
>
> OMNamespace omNs = fac.createOMNamespace("catalog", "");
>
> OMElement up = fac.createOMElement("in0", omNs);
>
>
>
> FileDataSource fds = new FileDataSource("file.xml");
>
> DataHandler dataHandler = new DataHandler(fds);
>
>
>
> OMText textData = fac.createOMText(dataHandler, true);
>
> textData.setOptimize(true);
>
>
>
> up.addChild(textData);
>
>
>
> //OMElement res = service.sendReceive(up);
>
> //service.fireAndForget(up);
>
> service.sendRobust(up);
>
> }
>
> catch(Exception error) {
>
> error.printStackTrace();
>
> }

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

Re: Sending MTOM attachments from Axis2 client

[Angel Todorov]

Hi,

where do you observe that behavior ? Via the soap monitor or by using
a TCP (HTTP more specifically) sniffer ? Normally to see if MTOM is
working you should use some TCP monitor, soap monitor or any other
soap message monitor won't help you.

--Angel

On 1/17/07, Nathan Kuroczycki <[EMAIL PROTECTED]> wrote:

Hi,

I am trying to send the request XML with the binary within an MTOM
attachment. However, the code below sends the binary inline with the rest of
the xml request. My understanding from the Axis2 examples is that by
enabling MTOM, the binary will be sent as a referenced attachment. Is there
something that I'm not doing?

Thanks,
Nathan


ServiceClient service = new ServiceClient();



Options options = new Options();

options.setTo(new EndpointReference(URL));

options.setAction("urn:update");

options.setProperty(Constants.Configuration.ENABLE_MTOM,
Constants.VALUE_TRUE );

service.setOptions(options);



try {



OMFactory fac = OMAbstractFactory.getOMFactory();

OMNamespace omNs = fac.createOMNamespace("catalog", "");

OMElement up = fac.createOMElement("in0", omNs);



FileDataSource fds = new FileDataSource("file.xml");

DataHandler dataHandler = new DataHandler(fds);



OMText textData = fac.createOMText(dataHandler, true);

textData.setOptimize(true);



up.addChild(textData);



//OMElement res = service.sendReceive(up);

//service.fireAndForget(up);

service.sendRobust(up);

}

catch(Exception error) {

error.printStackTrace();

}


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

Do you know a tool to easily visualize a wsdl file ?

[Samy Mechiri]

Hi everyone,
 
do you know any small, easily usable tool to visualize what operations
(and their arguments) are available on a wsd file ?
 
There seem to be nusoap having such a tool (i've read about it on
http://www.xml.com/lpt/a/1388) but I could not find any reference to it
on nusoap's web page.
 
Ideally it would output the results as a txt or html file
 
Thank you for reading.

Re: wsdl2java generates incorrect/incomplete code

[Anne Thomas Manes]

Bruce,

Giving the WSDL a quick look, I noticed that it is not valid. I don't
know if this is what's causing your problem, but it's a good place to
start.

In your WSDL  section, you attempt to import the same namespace
twice. This is not allowed. If the namespace is defined in multiple
schemas, and your goal is to import both schemas, then you must define
a schema with the same target namespace and  the schemas
into the namespace. e.g.:

  http://www.w3.org/2001/XMLSchema";
elementFormDefault="qualified">




Another error that I found: you must not specify the parameterOrder
attribute in the  definition when using document
style. (It is only used with RPC style.)

As a general practice, it's a bad idea to define headers in your WSDL,
especially if you are using standard headers. (The XMLBeans error
indicates that you are using WS-Addressing and DSIG.) You should
define your header requirements using WS-Policy and configuration
files.

Also, in regards to schema you did provide
(targetNamespace="urn:/fih/purchase-order"), some best practices
advice:

- Avoid using anonymous types. Rather than defining structures as
elements, define them as named types, and then define elements as
those types. e.g.:

Do this:

   





   

Rather than this:










And I recommend being cautious about defining each element as a global
element. The only elements that really should be defined as global
elements are those elements that will be the root of a document. i.e,
rather than defining "BaselineItemDataSegment" as a gloal element and
referencing it from the type definition, define the element within the
type definition and reference its type, e.g.:


We also need to see the "unr:/fih/c-efm/purchase-order/1.0" schema files.
(You sent us the "http://www.fih.org/XML/WD0"; namespace schema, instead.)

   






Anne

On 1/17/07, R Bruce Hoffman <[EMAIL PROTECTED]> wrote:

Sure... sorry.

Also, when using xmlbeans binding, I get the following error:

 Using AXIS2_HOME:   /usr/local/axis2
 Using JAVA_HOME:   /usr/lib/jvm/java-1.5.0-sun
Retrieving schema at '../../../../fih/1.0/fih-header.xsd', relative to
'file:/home/hoffmanb/ax/wsdl/fih/c-efm/purchase-order/receive-purchase-order/'.
Retrieving schema at
'http://www.w3.org/TR/2002/REC-xmldsig-core-20020212/xmldsig-core-schema.xsd', 
relative to 'file:/home/hoffmanb/ax/wsdl/fih/1.0/fih-header.xsd'.
Retrieving schema at
'http://schemas.xmlsoap.org/ws/2004/08/addressing/', relative to
'file:/home/hoffmanb/ax/wsdl/fih/1.0/fih-header.xsd'.
Retrieving schema at '1.0/receive-purchase-order-request.xsd', relative
to
'file:/home/hoffmanb/ax/wsdl/fih/c-efm/purchase-order/receive-purchase-order/'.
Retrieving schema at 'LimitedPurchaseOrder.xsd', relative to
'file:/home/hoffmanb/ax/wsdl/fih/c-efm/purchase-order/receive-purchase-order/1.0/receive-purchase-order-request.xsd'.
Retrieving schema at '1.0/receive-purchase-order-reply.xsd', relative to
'file:/home/hoffmanb/ax/wsdl/fih/c-efm/purchase-order/receive-purchase-order/'.
Jan 16, 2007 1:39:58 PM org.apache.axis2.xmlbeans.CodeGenerationUtility
$Axis2EntityResolver resolveEntity
INFO: Resolving schema with publicId [urn:/fih/1.0] and systemId
[/fih/1.0/fih-header.xsd]
Jan 16, 2007 1:39:58 PM org.apache.axis2.xmlbeans.CodeGenerationUtility
$Axis2EntityResolver resolveEntity
INFO: Resolving schema with publicId [urn:/fih/c-efm/purchase-order/1.0]
and systemId [/1.0/receive-purchase-order-request.xsd]
Jan 16, 2007 1:39:58 PM org.apache.axis2.xmlbeans.CodeGenerationUtility
$Axis2EntityResolver resolveEntity
INFO: Resolving schema with publicId [urn:/fih/c-efm/purchase-order/1.0]
and systemId [/1.0/receive-purchase-order-reply.xsd]
Jan 16, 2007 1:39:58 PM org.apache.axis2.xmlbeans.CodeGenerationUtility
$Axis2EntityResolver resolveEntity
INFO: Resolving schema with publicId
[http://www.w3.org/2000/09/xmldsig#] and systemId
[/http:/www.w3.org/TR/2002/REC-xmldsig-core-20020212/xmldsig-core-schema.xsd]
Jan 16, 2007 1:39:58 PM org.apache.axis2.xmlbeans.CodeGenerationUtility
$Axis2EntityResolver resolveEntity
INFO: Resolving schema with publicId
[http://schemas.xmlsoap.org/ws/2004/08/addressing] and systemId
[/http:/schemas.xmlsoap.org/ws/2004/08/addressing]
Jan 16, 2007 1:39:58 PM org.apache.axis2.xmlbeans.CodeGenerationUtility
$Axis2EntityResolver resolveEntity
INFO: Resolving schema with publicId [http://www.fih.org/XML/WD0] and
systemId [/1.0/LimitedPurchaseOrder.xsd]
Exception in thread "main"
org.apache.axis2.wsdl.codegen.CodeGenerationException:
java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
at
org.a

Sending MTOM attachments from Axis2 client

[Nathan Kuroczycki]

Hi,

I am trying to send the request XML with the binary within an MTOM
attachment. However, the code below sends the binary inline with the rest of
the xml request. My understanding from the Axis2 examples is that by
enabling MTOM, the binary will be sent as a referenced attachment. Is there
something that I'm not doing?

Thanks,
Nathan

ServiceClient service = *new* ServiceClient();

Options options = *new* Options();

options.setTo(*new* EndpointReference(*URL*));

options.setAction("urn:update");

options.setProperty(Constants.Configuration.*ENABLE_MTOM*, Constants.*
VALUE_TRUE*);

service.setOptions(options);

*try* {

OMFactory fac = OMAbstractFactory.*getOMFactory*();

OMNamespace omNs = fac.createOMNamespace("catalog", "");

OMElement up = fac.createOMElement("in0", omNs);

FileDataSource fds = *new* FileDataSource("file.xml");

DataHandler dataHandler = *new* DataHandler(fds);

OMText textData = fac.createOMText(dataHandler, *true*);

textData.setOptimize(*true*);

up.addChild(textData);

//OMElement res = service.sendReceive(up);

//service.fireAndForget(up);

service.sendRobust(up);

}

*catch*(Exception error) {

error.printStackTrace();

}

WS-SECURITY WITH SAML2 TOKENS

[Evaristo José Camarero]

Hi:

Does Axis2 with rampart module support SAML2 Security
Tokens?

Regards,

Evaristo





__ 
LLama Gratis a cualquier PC del Mundo. 
Llamadas a fijos y móviles desde 1 céntimo por minuto. 
http://es.voice.yahoo.com

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

Size of responses. Databinding choice: none vs adb.

[Morgante Thomas]

I've generated, for the same wsdl two clients. Using none as databinding
for the first and adb for the second.
With the none I can't manage to deal with responses larger than 4000B I
get error message like "Attempted read on closed stream" and I couldn't
go any farther. 
With the second it all works fine.
Has anybody experienced something similar? What databinding are you
using?
I choose initially none because I thought it would bee more efficient
and reliable, more "low level". I suppose I was wrong and the default
choice was the correct one.


CONFIDENTIALITY NOTICE

This message and its attachments are addressed solely to the persons above and 
may contain confidential information. If you have received the message in 
error, be informed that any use of the content hereof is prohibited. Please 
return it immediately to the sender and delete the message. Should you have any 
questions, please contact us by replying to [EMAIL PROTECTED]

Thank you

www.telecomitalia.it




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

[Axis2] [rampart] Problems using rampart

[Sebastian Roschke]

Hi everybody,

I have a problem using rampart in axis2. I just have configured the
axis2-client.xml this way, that it should use rampart. At the moment I
have no configuration for the rampart module at all. While using the
client api to invoke a soap request, I get the following exceptions:

org.apache.axis2.AxisFault: Error in extracting message properties;
nested exception is:
org.apache.rampart.RampartException: Error in extracting message
properties
at
org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:65)
at org.apache.axis2.engine.Phase.invoke(Phase.java:381)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:518)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:651)
at
org.apache.axis2.description.OutOnlyAxisOperationClient.execute(OutOnlyAxisOperation.java:353)
at
skid.messaging.ws.client.client.MessagingClientServiceStub.addClient(MessagingClientServiceStub.java:126)
at skid.messaging.client.ClientControl.main(ClientControl.java:55)
Caused by: org.apache.rampart.RampartException: Error in extracting
message properties
at
org.apache.rampart.RampartMessageData.(RampartMessageData.java:294)
at org.apache.rampart.MessageBuilder.build(MessageBuilder.java:56)
at
org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:59)
... 6 more
Caused by: org.apache.ws.security.WSSecurityException: Error in
converting SOAP Envelope to Document; nested exception is:
org.apache.axiom.om.OMException: javax.xml.stream.XMLStreamException
at
org.apache.rampart.util.Axis2Util.getDocumentFromSOAPEnvelope(Axis2Util.java:121)
at
org.apache.rampart.RampartMessageData.(RampartMessageData.java:146)
... 8 more
Caused by: org.apache.axiom.om.OMException:
javax.xml.stream.XMLStreamException
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:199)
at org.apache.axiom.om.impl.dom.NodeImpl.build(NodeImpl.java:469)
at
org.apache.axiom.om.impl.dom.DocumentImpl.build(DocumentImpl.java:476)
at
org.apache.rampart.util.Axis2Util.getDocumentFromSOAPEnvelope(Axis2Util.java:107)
... 9 more
Caused by: javax.xml.stream.XMLStreamException
at
org.apache.axiom.om.impl.llom.OMStAXWrapper.updateLastNode(OMStAXWrapper.java:952)
at
org.apache.axiom.om.impl.llom.OMStAXWrapper.next(OMStAXWrapper.java:913)
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:116)
... 12 more

This exception is thrown when invoking the first request on the stub. I
can find the following link concerning that problem:
http://www.mail-archive.com/axis-dev@ws.apache.org/msg25582.html


As proposed in this post I should check wether the soap message includes
MIME parts. I used MIME parts in former times, but at the moment I
disabled all MTOM related things.

Do you have any suggestions concernings this problem? Is it a known
problem or a bug?




signature.asc
Description: OpenPGP digital signature

RE: SocketTimeOutException

[Punnoose, Roshan]

Haha, yeah. Actually, my socket timeout wasn't happening because of the 
SO_TIMEOUT param, it was happening because of the 
Options.setTimeoutInMillis(...) timeout, which is defaulted at 30 seconds. So 
after setting this, everything was ok.

Roshan Punnoose
Phone: 301-497-6039

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, January 16, 2007 5:18 PM
To: axis-user@ws.apache.org
Subject: Re: SocketTimeOutException

What kind of web service method invocation do you use? Void or with some 
returning type? I experienced this problem only with void (so client was 
waiting for some background confirmation and timeout expired), in that case I 
guess there is no really working solution. Try adding parameter SO_TIMEOUT into 
the axis2.xml (but it won´t help). You can take a look at my (I guess two days 
old) post called "Any real solution to Socket Timeout" or something like this. 
You can also try to use calling with returning object (I used String which 
indicates success...) than you can just throw this object away.. I hope it 
helps. But I am sure that uninstallation of internet security tools is NOT a 
good solution :)

__
> Od: [EMAIL PROTECTED]
> Komu: axis-user@ws.apache.org, "Jernigan, TieSha" <[EMAIL PROTECTED]>
> CC: axis-user@ws.apache.org
> Datum: 16.01.2007 20:24
> Předmět: Re: SocketTimeOutException 
>
>I had the same problem :
>you can try to update timeout value in axis.xml.
>But for me the problem was fixed to uninstall my security internet tools
>(stopping firewall was not enough ...)
>
>
>
>Quoting "Jernigan, TieSha" <[EMAIL PROTECTED]>:
>
>> When running my Axis2 Client, after about 20-30 seconds I get the
>> following exception. My system does not recover from this exception. I
>> am assuming that when the exception occurs the socket gets closed, so I
>> never get a response back from my server. Is there a way that I can
>> increase the timeout? Or are there any other suggestions on how to fix
>> the problem?
>>
>>
>>
>> ERROR espace.services.galelite.client.BaseWebServiceClient  - Server
>> responded with the Exception[Read timed out; nested exception is:
>>
>> java.net.SocketTimeoutException: Read timed out; nested
>> exception is:
>>
>> org.apache.axis2.AxisFault: Read timed out; nested
exception
>> is:
>>
>> java.net.SocketTimeoutException: Read timed out]
>>
>> [2007.01.16 at 13:35:01 EST] Server responded with the Exception[Read
>> timed out; nested exception is:
>>
>> java.net.SocketTimeoutException: Read timed out; nested
>> exception is:
>>
>> org.apache.axis2.AxisFault: Read timed out; nested
exception
>> is:
>>
>> java.net.SocketTimeoutException: Read timed out]
>>
>>
>
>
>
>-
>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]

BEGIN:VCARD
VERSION:2.1
N:Punnoose;Roshan
FN:Punnoose, Roshan
ADR;WORK:;2115
LABEL;WORK:2115
EMAIL;PREF;INTERNET:[EMAIL PROTECTED]
REV:20050413T183207Z
END:VCARD
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: wsdl2java generates incorrect/incomplete code

[R Bruce Hoffman]

Sure... sorry.

Also, when using xmlbeans binding, I get the following error:

 Using AXIS2_HOME:   /usr/local/axis2
 Using JAVA_HOME:   /usr/lib/jvm/java-1.5.0-sun
Retrieving schema at '../../../../fih/1.0/fih-header.xsd', relative to
'file:/home/hoffmanb/ax/wsdl/fih/c-efm/purchase-order/receive-purchase-order/'.
Retrieving schema at
'http://www.w3.org/TR/2002/REC-xmldsig-core-20020212/xmldsig-core-schema.xsd', 
relative to 'file:/home/hoffmanb/ax/wsdl/fih/1.0/fih-header.xsd'.
Retrieving schema at
'http://schemas.xmlsoap.org/ws/2004/08/addressing/', relative to
'file:/home/hoffmanb/ax/wsdl/fih/1.0/fih-header.xsd'.
Retrieving schema at '1.0/receive-purchase-order-request.xsd', relative
to
'file:/home/hoffmanb/ax/wsdl/fih/c-efm/purchase-order/receive-purchase-order/'.
Retrieving schema at 'LimitedPurchaseOrder.xsd', relative to
'file:/home/hoffmanb/ax/wsdl/fih/c-efm/purchase-order/receive-purchase-order/1.0/receive-purchase-order-request.xsd'.
Retrieving schema at '1.0/receive-purchase-order-reply.xsd', relative to
'file:/home/hoffmanb/ax/wsdl/fih/c-efm/purchase-order/receive-purchase-order/'.
Jan 16, 2007 1:39:58 PM org.apache.axis2.xmlbeans.CodeGenerationUtility
$Axis2EntityResolver resolveEntity
INFO: Resolving schema with publicId [urn:/fih/1.0] and systemId
[/fih/1.0/fih-header.xsd]
Jan 16, 2007 1:39:58 PM org.apache.axis2.xmlbeans.CodeGenerationUtility
$Axis2EntityResolver resolveEntity
INFO: Resolving schema with publicId [urn:/fih/c-efm/purchase-order/1.0]
and systemId [/1.0/receive-purchase-order-request.xsd]
Jan 16, 2007 1:39:58 PM org.apache.axis2.xmlbeans.CodeGenerationUtility
$Axis2EntityResolver resolveEntity
INFO: Resolving schema with publicId [urn:/fih/c-efm/purchase-order/1.0]
and systemId [/1.0/receive-purchase-order-reply.xsd]
Jan 16, 2007 1:39:58 PM org.apache.axis2.xmlbeans.CodeGenerationUtility
$Axis2EntityResolver resolveEntity
INFO: Resolving schema with publicId
[http://www.w3.org/2000/09/xmldsig#] and systemId
[/http:/www.w3.org/TR/2002/REC-xmldsig-core-20020212/xmldsig-core-schema.xsd]
Jan 16, 2007 1:39:58 PM org.apache.axis2.xmlbeans.CodeGenerationUtility
$Axis2EntityResolver resolveEntity
INFO: Resolving schema with publicId
[http://schemas.xmlsoap.org/ws/2004/08/addressing] and systemId
[/http:/schemas.xmlsoap.org/ws/2004/08/addressing]
Jan 16, 2007 1:39:58 PM org.apache.axis2.xmlbeans.CodeGenerationUtility
$Axis2EntityResolver resolveEntity
INFO: Resolving schema with publicId [http://www.fih.org/XML/WD0] and
systemId [/1.0/LimitedPurchaseOrder.xsd]
Exception in thread "main"
org.apache.axis2.wsdl.codegen.CodeGenerationException:
java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:224)
at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32)
at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)
Caused by: java.lang.RuntimeException:
java.lang.reflect.InvocationTargetException
at
org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLBeansExtension.java:92)
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:177)
... 2 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLBeansExtension.java:82)
... 3 more
Caused by: java.lang.RuntimeException: org.apache.xmlbeans.XmlException:
http://schemas.xmlsoap.org/ws/2004/08/addressing/:61:1: error:
cvc-enumeration-valid: string value 'none' is not a valid enumeration
value for type of processContents attribute in xs:wildcard
at
org.apache.axis2.xmlbeans.CodeGenerationUtility.processSchemas(CodeGenerationUtility.java:242)
... 8 more
Caused by: org.apache.xmlbeans.XmlException:
http://schemas.xmlsoap.org/ws/2004/08/addressing/:61:1: error:
cvc-enumeration-valid: string value 'none' is not a valid enumeration
value for type of processContents attribute in xs:wildcard
at
org.apache.xmlbeans.impl.schema.SchemaTypeSystemCompiler.compile(SchemaTypeSystemCompiler.java:225)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.xmlbeans.XmlBeans.compileXmlBeans(XmlBeans.java:667)
at
org.apache.axis2.xmlbeans.CodeGenerationUtility.processSchemas(CodeGenerationUtility.java:160)
... 8 more




On Wed, 2007-01-17 a

RE: Unsubscribing

[Javier Kohen]

El mié, 17-01-2007 a las 11:09 +0100, Kedar, Shahar escribió:
> That’s the easy and yet the improper way. I wanted to know if there’s
> a more formal (and working) way.

Maybe you subscribed with a different address? Can you double check what
address the mailing list daemon is sending you the e-mails to? Theat
information should be buried within headers of the e-mails you receive
from the list.

> 
>  
> 
> Shahar.
> 
>  
> 
>
> __
> From: biswadip saha [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, January 16, 2007 2:17 PM
> To: axis-user@ws.apache.org
> Subject: Re: Unsubscribing
> 
> 
>  
> 
> block axis-user@ws.apache.org
> 
> On 1/16/07, Kedar, Shahar <[EMAIL PROTECTED]> wrote: 
> 
> Hi,
> 
>  
> 
> I'm trying to unsubscribe from the mailing list, but when I try to
> confirm it I get an error that the address I'm trying to send it to
> does not exist. 
> 
> Any suggestion will be helpful.
> 
>  
> 
> Thanks,
> 
> Shahar
> 
> 
> 
> 
> 
> -- 
> ##
> Sr. Software Developer 
> +919899566690
> ##
> 
> 
> 
> 
>   o o o o o o o . . .   __ 
> o  _   ||| 
>   .][__n_n_|DD[  _  | | 
> >(|__|_[_]_|| 
> _/oo O oo`  ooo   ooo  'o!o!o  o!o!o` 
> -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
> 

-- 
Javier Kohen <[EMAIL PROTECTED]>
ICQ: blashyrkh #2361802
Jabber: [EMAIL PROTECTED]


signature.asc
Description: Esta parte del mensaje está firmada	digitalmente

[AXIS2]Classloader error while using Hibernate with AXIS2.

[Hemanth, Yamini \(MSAS Sys Dev IBD\)]

Hi All,
 
 
I am using Hibernate with AXIS2 . My application runs stand-alone from
Eclipse.However, when I try deploying it as a service on Tomcat, the
class-loader is unable to load the xml files related to Hibernate.
THis was because AXIS will load the service in its own classloader.
One of my team-member suggested that I should make a jar of all the xml
files,class files and place it in
/webapps/axis/WEB-INF/lib.
Previously:
1.Built all the classfiles, xml input  files, services.xml,manifest.mf,
wsdl file into an .aar file 
2.Placed the .aar file in /webapps/axis/WEB-INF/services
folder.
 
 
 
Now:
1.Created a jar of all the classfiles, xml input  files
2.Placed the jar file in  /webapps/axis/WEB-INF/lib folder.
3.Built the services.xml,manifest.mf, wsdl file into an .aar file 
4.Placed the .aar file in /webapps/axis/WEB-INF/services
folder.
 
Now, I am able to use Hibernate to connect to the database and the
relevant files are also being loaded by classloader.
 
But my query is why should I place the jar containing service specific
files in the /WEB-INF/lib which will make the jar available to all the
services.
Is there any other way to get this working..
 
 
Please give your inputs on the same.
 
 
 
 
 
Regards,
 
Yamini


NOTICE: If received in error, please destroy and notify sender. Sender does not 
intend to waive confidentiality or privilege. Use of this email is prohibited 
when received in error.

Axis2 Programmatic Deployment

[Angel Todorov]

Hi all,

I saw that there is no way to deploy a service programmatically in
Axis2. Is that the case? Only building the AxisService object instance
is possible through the buildService method of the deploymentEngine,
but this doesn't help much. The doDeploy() method checks an array of
WSArchives , which are loaded through ArchiveFileData.

I am more interested in deploying a service without having any AAR
archive on the file system, but some other repository (a third party
app or a database for instance).

Thanks for the feedback.

Best Regards,
Angel

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

RE: Unsubscribing

[Kedar, Shahar]

That's the easy and yet the improper way. I wanted to know if there's a
more formal (and working) way.

 

Shahar.

 



From: biswadip saha [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, January 16, 2007 2:17 PM
To: axis-user@ws.apache.org
Subject: Re: Unsubscribing

 

block axis-user@ws.apache.org

On 1/16/07, Kedar, Shahar <[EMAIL PROTECTED]> wrote: 

Hi,

 

I'm trying to unsubscribe from the mailing list, but when I try to
confirm it I get an error that the address I'm trying to send it to does
not exist. 

Any suggestion will be helpful.

 

Thanks,

Shahar




-- 
##
Sr. Software Developer 
+919899566690
##




  o o o o o o o . . .   __ 
o  _   ||| 
  .][__n_n_|DD[  _  | | 
>(|__|_[_]_|| 
_/oo O oo`  ooo   ooo  'o!o!o  o!o!o` 
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 

Re: SocketTimeOutException

[Michele Mazzucco]

Please try to have a look here
http://wso2.org/library/230

Hope this helps,
Michele

On 16 Jan 2007, at 19:11, Jernigan, TieSha wrote:

When running my Axis2 Client, after about 20-30 seconds I get the  
following exception. My system does not recover from this  
exception. I am assuming that when the exception occurs the socket  
gets closed, so I never get a response back from my server. Is  
there a way that I can increase the timeout? Or are there any other  
suggestions on how to fix the problem?




ERROR espace.services.galelite.client.BaseWebServiceClient  -  
Server responded with the Exception[Read timed out; nested  
exception is:


java.net.SocketTimeoutException: Read timed out; nested  
exception is:


org.apache.axis2.AxisFault: Read timed out; nested  
exception is:


java.net.SocketTimeoutException: Read timed out]

[2007.01.16 at 13:35:01 EST] Server responded with the Exception 
[Read timed out; nested exception is:


java.net.SocketTimeoutException: Read timed out; nested  
exception is:


org.apache.axis2.AxisFault: Read timed out; nested  
exception is:


java.net.SocketTimeoutException: Read timed out]

Re: Axis2 1.1.1 with XMLBeans as the Data binding framework.

[Paul Fremantle]

Sriram

Please can you raise a JIRA?

Paul

On 1/17/07, Sriram Vaidyanathan <[EMAIL PROTECTED]> wrote:

Paul,
 I switched from Axis2 1.1.1 to Axis21.1 and tried to build with the 
xsd:include and it worked without any issues. So this seems to be a problem 
with Axis2 1.1.1. So should a JIRA be filed this in Axis2 1.1.1?

Also, if I go ahead and upgrade to Axis2 1.1 instead of Axis2 1.1.1 for my 
project, are there any issues with 1.1 that I need to be aware of before making 
the upgrade.

Appreciate your help so far. Thanks.

Thanks,
Sriram Vaidyanathan
Software Engineer - Java
Copart Auto Auctions, Inc.
4665 Business Center Drive
Fairfield, CA 94534
www.copart.com 
(707) 639-5248

-Original Message-
From: Paul Fremantle [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 16, 2007 10:11 PM
To: axis-user@ws.apache.org
Subject: Re: Axis2 1.1.1 with XMLBeans as the Data binding framework.

Sriram

You are right. I managed to recreate your problem. I think there is a
bug in the XMLBeans databinding.

Try using xsd:import instead of include:

http://www.sample.com/test"; />

Paul

On 1/17/07, Sriram Vaidyanathan <[EMAIL PROTECTED]> wrote:
> Hi Paul,
>
> Thanks for the response.
>
> If I remove the SampleService.xsd from the folder, then I get the expection 
as you posted.  See [1] below.
>
> But if I have the file present, then I get a different version of the same 
exception. See [2] below.  So, I am wondering if I have the file present, is it 
hiding some other problem. ?
>
>
>
>
> [1]
> Running AXIS Tool WSDL2Java with Axis2 Home as  C:\axis2-1.1.1
>[delete] Deleting directory C:\cvs\aps\cieca\wsdl\xmlbeans_gen_src
>  [java] Retrieving schema at 'SampleService.xsd', relative to 
'file:/C:/cvs/aps/sample/wsdl/src/main/config/'.
>  [java] Exception in thread "main" 
org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL
>  [java] at 
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerationEngine.java:114)
>  [java] at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32)
>  [java] at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)
>  [java] Caused by: javax.wsdl.WSDLException: WSDLException (at 
/wsdl:definitions/wsdl:types/xsd:schema[2]): faultCode=OTHER_ERROR: An error 
occurred trying to resolve schema referenced at 'SampleService.xsd', relative to 
'file:/C:/cvs/aps/sample/wsdl/src/main/config/'.: java.io.FileNotFoundException: 
This file was not found: 
file:/C:/cvs/aps/sample/wsdl/src/main/config/SampleService.xsd
>  [java] at com.ibm.wsdl.xml.WSDLReaderImpl.parseSchema(Unknown Source)
>  [java] at com.ibm.wsdl.xml.WSDLReaderImpl.parseSchema(Unknown Source)
>  [java] at com.ibm.wsdl.xml.WSDLReaderImpl.parseTypes(Unknown Source)
>  [java] at com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(Unknown 
Source)
>  [java] at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
>  [java] at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
>  [java] at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
>  [java] at 
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.readInTheWSDLFile(CodeGenerationEngine.java:276)
>  [java] at 
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerationEngine.java:97)
>
>
> [2]
>
> [INFO] Executing tasks
>  [echo] Running AXIS Tool WSDL2Java with Axis2 Home as  C:\axis2-1.1.1
>[delete] Deleting directory C:\cvs\aps\sample\wsdl\xmlbeans_gen_src
>  [java] Retrieving schema at 'SampleService.xsd', relative to 
'file:/C:/cvs/aps/sample/wsdl/src/main/config/'.
>  [java] Jan 16, 2007 9:31:48 PM 
org.apache.axis2.xmlbeans.CodeGenerationUtility$Axis2EntityResolver resolveEntity
>  [java] INFO: Resolving schema with publicId [null] and systemId 
[\SampleService.xsd]
>  [java] Exception in thread "main" 
org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeException: 
java.lang.reflect.InvocationTargetException
>  [java] at 
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:224)
>  [java] at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32)
>  [java] at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)
>  [java] Caused by: java.lang.RuntimeException: 
java.lang.reflect.InvocationTargetException
>  [java] at 
org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLBeansExtension.java:92)
>  [java] at 
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:177)
>  [java] ... 2 more
>  [java] Caused by: java.lang.reflect.InvocationTargetException
>  [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>  [java] at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>  [java] at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(Delegat

[AXIS 1.x - WSS4J] - HTTPs or Secure HTTP

[José Ferreiro]

Hi!
Could someone tell me if HTTPs or Secure HTTP is supported by Axis 1.x and
WSS4J?

Thank you.