date:20071031

Re: [Axis2] Axis2 Release Restructuring

2007-10-31 Thread Amila Suriarachchi

On 11/1/07, Lawrence Mandel <[EMAIL PROTECTED]> wrote:
>
> Hi Amila,
>
> Thanks for summarizing the conversation. I take it your summary is for the
> Axis2 server bundle that's been discussed. Two issues:
>
> 1. Will the 5 Axis2 jars be rolled up into a single Axis2-server jar as
> has been requested and discussed?


No. we are not going to shift as five modules.
It going to be only three.
1. minimal distribution
2. full distribution
3. tools distribution

the difference between minimal and full is that minimal distribution
contains jars required
for only basic set of use cases(as I have given earlier). It has both client
and server jars.

2. You listed
> woden-impl-dom-1.0-incubating-20071018.161106-2.jar
> Woden has an Axiom based implementation that I thought was contributed to
> support Axis2.

So is this an optional jar?

Is the Axiom implementation not in use in Axis2?


Axis2 uses the axiom. What I asked is, whether it is necessary to shif doom
implementation as well.

Amila.

Thanks,
>
> Lawrence
>
>
>
>
> "Amila Suriarachchi" <[EMAIL PROTECTED]>
> 11/01/2007 12:16 AM
> Please respond to
> axis-dev@ws.apache.org
>
>
> To
> axis-dev@ws.apache.org
> cc
>
> Subject
> Re: [Axis2] Axis2 Release Restructuring
>
>
>
>
>
>
> So shall we first conclue what should be included into the minimal
> distribution?
>
> I would like to discribe the minimal distribution as follows,
> It inclues the minimal set of jars which some one needs to creates a
> webservice
> using either
> 1. Contract first approach
>  here we going to provide only the default data binding support
> 2. Code first approach
>  POJO support
>
> and access them using the generated stub or
> RPCService client. Here he can use addressing since it is a basic we
> service spec and only with http transport.
>
> So the minimal distribution contains the following features
> 1. Codegen support with adb
> 2. POJO support
> 3. MTOM (when we includes the axiom and axis2 kernal anyway we get this)
> 4. Addressing
> 5. Samples ( only for above features)
>
> is this enogh or is there any thing to add or remove?
>
> As I guess here are the jars we need for that,
>
> Axis2 jars
> 1. axis2-adb-codegen-SNAPSHOT.jar
> 2. axis2-adb-SNAPSHOT.jar
> 3. axis2-codegen-SNAPSHOT.jar
> 4. axis2-java2wsdl-SNAPSHOT.jar
> 5. axis2-kernel-SNAPSHOT.jar
>
> ws  jars
> 1. axiom-api-20071017.164440-781.jar
> 2. axiom-impl-20071017.164440-780.jar (
> (do we need axiom-dom-20071017.164440-780.jar?)
> 3. neethi-20071017.164823-761.jar
> 4. woden-api-1.0-incubating-20071018.161106-2.jar
> 5. woden-impl-dom-1.0-incubating-20071018.161106-2.jar
> 6. wsdl4j-1.6.2.jar
> 7. XmlSchema-SNAPSHOT.jar
>
> other jars
> 1. activation-1.1.jar
> 2. annogen-0.1.0.jar
> 3. backport-util-concurrent-2.2.jar
> 4. commons-codec-1.3.jar
> 5. commons-fileupload-1.1.1.jar
> 6. commons-httpclient-3.0.1.jar
> 7. commons-io-1.2.jar
> 8. commons-logging-1.1.jar
> 9. geronimo-annotation_1.0_spec-1.1.jar
> 10. geronimo-stax-api_1.0_spec-1.0.jar
> 11. httpcore-4.0-alpha5.jar
> 12. httpcore-nio-4.0-alpha5.jar
> 13. httpcore-niossl-4.0-alpha5.jar
> 14. jalopy-1.5rc3.jar
> 15. jaxen-1.1.1.jar
> 16. jettison-1.0-RC1.jar
> 17. log4j-1.2.14.jar
> 18. stax-api-1.0.1.jar
> 19. wstx-asl-3.2.1.jar
> 20. xalan-2.7.0.jar
> 21. xercesImpl-2.8.1.jar
> 22. xml-apis-1.3.03.jar
>
> Are there any thing to add or remove?
> Here any way 34 jars are there. and we have left 24 jars.
>
> thanks,
> Amila.
>
> On 10/30/07, Eran Chinthaka <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Amila Suriarachchi wrote:
>
> >
> > I have misunderstood the thing.
> > you mean
> > 1. minimal distribution with
> >server,client and kernal
> > 2. full distribution with
> >minmal + optional
> > 3. Tools distribution with
> >tools
>
> Exactly yes. I am not sure whether we need to expand full distro also in
> to two. Are we releasing all the modules with our current standard distro.
>
>
> > what I want to say is that we need a proper boundry definition about
> > what should goes to minimal distribution.
> > with some logical reasoning. Otherwise we have to discuss this again
> > when implementing.
>
> Agreed. That is why I made this a proposal rather than a vote :). We
> discussed this packaging issues couple of times and changed packaging
> couple of time. When Axis2 evolves and we get more insight in to user
> experience, we might want to change ourselves to cater for this
> requirements. I myself found it bit difficult/confused to use Axis2 once
> as a user. That is why I am proposing sth like this.
>
> Yes, let's discuss about this. And we might also want to revise this
> once the next release manager (Amila will it be you ;) ) try to
> implement this packaging proposal.
>
> So are we agreed to this three level distro?
>
> Thanks,
> Chinthaka
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.6 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DB

Re: [Axis2] WS-policy client support

2007-10-31 Thread Sanka Samaranayke


Hi,

One work around would be to use the ServiceClient instead of using a generated stub and attach the equivalent standard policy of that proprietary policy expreesion. 


You may also have to set username and password in options.

e.g.

Options options = serviceClient.getOptions();
options.setUsername(..);
optoins.setPassword(..);

HTH,
Sanka



Anne Thomas Manes wrote:

That's a proprietary policy assertion language. It's supported only by
BEA products. Talk to BEA and convince them to add support for the
standard OASIS WS-SecurityPolicy.

Anne

On 10/31/07, Feng Lu <[EMAIL PROTECTED]> wrote:
  

Hello friends,

I am wondering whether Axis2 support WS-policy client? My WSDL server is
Weblogic and the WSDL has following WS-policy. I am not sure whether Axis2
will be able to handle WS-policy in such case. If it does, could anybody let
me know how to implement the client side support for this? Any special
handling in the stub genration?



- 


- http://www.bea.com/wls90/security/policy";>


- 


- http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#UsernameToken";>


  http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText";
/>
  
  
  
  

Thanks a lot for your help!

Frank
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com



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


  



--
Sanka Samaranayake
WSO2 Inc.

http://www.bloglines.com/blog/sanka
http://www.wso2.org/


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

Re: [Axis2] Axis2 Release Restructuring

2007-10-31 Thread Lawrence Mandel

Hi Amila,

Thanks for summarizing the conversation. I take it your summary is for the 
Axis2 server bundle that's been discussed. Two issues:

1. Will the 5 Axis2 jars be rolled up into a single Axis2-server jar as 
has been requested and discussed?
2. You listed
woden-impl-dom-1.0-incubating-20071018.161106-2.jar 
Woden has an Axiom based implementation that I thought was contributed to 
support Axis2. Is the Axiom implementation not in use in Axis2?

Thanks,

Lawrence

"Amila Suriarachchi" <[EMAIL PROTECTED]> 
11/01/2007 12:16 AM
Please respond to
axis-dev@ws.apache.org

To
axis-dev@ws.apache.org
cc

Subject
Re: [Axis2] Axis2 Release Restructuring

So shall we first conclue what should be included into the minimal 
distribution?

I would like to discribe the minimal distribution as follows,
It inclues the minimal set of jars which some one needs to creates a 
webservice 
using either 
1. Contract first approach
 here we going to provide only the default data binding support
2. Code first approach 
 POJO support

and access them using the generated stub or 
RPCService client. Here he can use addressing since it is a basic we
service spec and only with http transport.

So the minimal distribution contains the following features
1. Codegen support with adb
2. POJO support 
3. MTOM (when we includes the axiom and axis2 kernal anyway we get this)
4. Addressing
5. Samples ( only for above features)

is this enogh or is there any thing to add or remove?

As I guess here are the jars we need for that, 

Axis2 jars
1. axis2-adb-codegen-SNAPSHOT.jar
2. axis2-adb-SNAPSHOT.jar
3. axis2-codegen-SNAPSHOT.jar
4. axis2-java2wsdl-SNAPSHOT.jar
5. axis2-kernel-SNAPSHOT.jar

ws  jars
1. axiom-api-20071017.164440-781.jar 
2. axiom-impl-20071017.164440-780.jar (
(do we need axiom-dom-20071017.164440-780.jar?)
3. neethi-20071017.164823-761.jar
4. woden-api-1.0-incubating-20071018.161106-2.jar
5. woden-impl-dom-1.0-incubating-20071018.161106-2.jar 
6. wsdl4j-1.6.2.jar
7. XmlSchema-SNAPSHOT.jar

other jars
1. activation-1.1.jar
2. annogen-0.1.0.jar
3. backport-util-concurrent-2.2.jar
4. commons-codec-1.3.jar
5. commons-fileupload-1.1.1.jar 
6. commons-httpclient-3.0.1.jar
7. commons-io-1.2.jar
8. commons-logging-1.1.jar
9. geronimo-annotation_1.0_spec-1.1.jar
10. geronimo-stax-api_1.0_spec-1.0.jar
11. httpcore-4.0-alpha5.jar
12. httpcore-nio-4.0-alpha5.jar 
13. httpcore-niossl-4.0-alpha5.jar
14. jalopy-1.5rc3.jar
15. jaxen-1.1.1.jar
16. jettison-1.0-RC1.jar
17. log4j-1.2.14.jar
18. stax-api-1.0.1.jar
19. wstx-asl-3.2.1.jar
20. xalan-2.7.0.jar
21. xercesImpl-2.8.1.jar
22. xml-apis-1.3.03.jar

Are there any thing to add or remove?
Here any way 34 jars are there. and we have left 24 jars.

thanks,
Amila.

On 10/30/07, Eran Chinthaka <[EMAIL PROTECTED]> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Amila Suriarachchi wrote:

>
> I have misunderstood the thing.
> you mean
> 1. minimal distribution with
>server,client and kernal 
> 2. full distribution with
>minmal + optional
> 3. Tools distribution with
>tools

Exactly yes. I am not sure whether we need to expand full distro also in
to two. Are we releasing all the modules with our current standard distro. 

> what I want to say is that we need a proper boundry definition about
> what should goes to minimal distribution.
> with some logical reasoning. Otherwise we have to discuss this again
> when implementing. 

Agreed. That is why I made this a proposal rather than a vote :). We
discussed this packaging issues couple of times and changed packaging
couple of time. When Axis2 evolves and we get more insight in to user 
experience, we might want to change ourselves to cater for this
requirements. I myself found it bit difficult/confused to use Axis2 once
as a user. That is why I am proposing sth like this.

Yes, let's discuss about this. And we might also want to revise this 
once the next release manager (Amila will it be you ;) ) try to
implement this packaging proposal.

So are we agreed to this three level distro?

Thanks,
Chinthaka
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHJ09HjON2uBzUhh8RAoDSAJ9DKYjtCRqEU/jiQnMnKm7oF0UzzQCgqd5z
6SUmDsDsirjOF6j5WuAu9EA= 
=ZWKs
-END PGP SIGNATURE-

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

-- 
Amila Suriarachchi,
WSO2 Inc. 

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

Re: [Axis2] Axis2 Release Restructuring

2007-10-31 Thread Amila Suriarachchi

So shall we first conclue what should be included into the minimal
distribution?

I would like to discribe the minimal distribution as follows,
It inclues the minimal set of jars which some one needs to creates a
webservice
using either
1. Contract first approach
 here we going to provide only the default data binding support
2. Code first approach
 POJO support

and access them using the generated stub or
RPCService client. Here he can use addressing since it is a basic we
service spec and only with http transport.

So the minimal distribution contains the following features
1. Codegen support with adb
2. POJO support
3. MTOM (when we includes the axiom and axis2 kernal anyway we get this)
4. Addressing
5. Samples ( only for above features)

is this enogh or is there any thing to add or remove?

As I guess here are the jars we need for that,

Axis2 jars
1. axis2-adb-codegen-SNAPSHOT.jar
2. axis2-adb-SNAPSHOT.jar
3. axis2-codegen-SNAPSHOT.jar
4. axis2-java2wsdl-SNAPSHOT.jar
5. axis2-kernel-SNAPSHOT.jar

ws  jars
1. axiom-api-20071017.164440-781.jar
2. axiom-impl-20071017.164440-780.jar (
(do we need axiom-dom-20071017.164440-780.jar?)
3. neethi-20071017.164823-761.jar
4. woden-api-1.0-incubating-20071018.161106-2.jar
5. woden-impl-dom-1.0-incubating-20071018.161106-2.jar
6. wsdl4j-1.6.2.jar
7. XmlSchema-SNAPSHOT.jar

other jars
1. activation-1.1.jar
2. annogen-0.1.0.jar
3. backport-util-concurrent-2.2.jar
4. commons-codec-1.3.jar
5. commons-fileupload-1.1.1.jar
6. commons-httpclient-3.0.1.jar
7. commons-io-1.2.jar
8. commons-logging-1.1.jar
9. geronimo-annotation_1.0_spec-1.1.jar
10. geronimo-stax-api_1.0_spec-1.0.jar
11. httpcore-4.0-alpha5.jar
12. httpcore-nio-4.0-alpha5.jar
13. httpcore-niossl-4.0-alpha5.jar
14. jalopy-1.5rc3.jar
15. jaxen-1.1.1.jar
16. jettison-1.0-RC1.jar
17. log4j-1.2.14.jar
18. stax-api-1.0.1.jar
19. wstx-asl-3.2.1.jar
20. xalan-2.7.0.jar
21. xercesImpl-2.8.1.jar
22. xml-apis-1.3.03.jar

Are there any thing to add or remove?
Here any way 34 jars are there. and we have left 24 jars.

thanks,
Amila.

On 10/30/07, Eran Chinthaka <[EMAIL PROTECTED]> wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Amila Suriarachchi wrote:
>
> >
> > I have misunderstood the thing.
> > you mean
> > 1. minimal distribution with
> >server,client and kernal
> > 2. full distribution with
> >minmal + optional
> > 3. Tools distribution with
> >tools
>
> Exactly yes. I am not sure whether we need to expand full distro also in
> to two. Are we releasing all the modules with our current standard distro.
>
> > what I want to say is that we need a proper boundry definition about
> > what should goes to minimal distribution.
> > with some logical reasoning. Otherwise we have to discuss this again
> > when implementing.
>
> Agreed. That is why I made this a proposal rather than a vote :). We
> discussed this packaging issues couple of times and changed packaging
> couple of time. When Axis2 evolves and we get more insight in to user
> experience, we might want to change ourselves to cater for this
> requirements. I myself found it bit difficult/confused to use Axis2 once
> as a user. That is why I am proposing sth like this.
>
> Yes, let's discuss about this. And we might also want to revise this
> once the next release manager (Amila will it be you ;) ) try to
> implement this packaging proposal.
>
> So are we agreed to this three level distro?
>
> Thanks,
> Chinthaka
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.6 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFHJ09HjON2uBzUhh8RAoDSAJ9DKYjtCRqEU/jiQnMnKm7oF0UzzQCgqd5z
> 6SUmDsDsirjOF6j5WuAu9EA=
> =ZWKs
> -END PGP SIGNATURE-
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Amila Suriarachchi,
WSO2 Inc.

[jira] Created: (AXIS2-3319) engageModule for ContextMessage has wrong parameters

2007-10-31 Thread Martin Gainty (JIRA)

engageModule for ContextMessage has wrong parameters


 Key: AXIS2-3319
 URL: https://issues.apache.org/jira/browse/AXIS2-3319
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
Affects Versions: 1.3
 Environment: WinTel
4GB RAM
1 tera diskspace
JVM 1.5
Rampart 1.3
AXIS2 1.3

Reporter: Martin Gainty


attempting to change signature of isEngaged to take a String

compile.src:
[javac] Compiling 1 source file to F:\AXIS\axis2-1.3\samples\ut-over-https\b
uild\classes
[javac] F:\AXIS\axis2-1.3\samples\ut-over-https\src\org\apache\rampart\tomca
t\sample\Client.java:34: package javanet.staxutils does not exist
[javac] import javanet.staxutils.StAXSource;
[javac]  ^
[javac] F:\AXIS\axis2-1.3\samples\ut-over-https\src\org\apache\rampart\tomca
t\sample\Client.java:117: invokeRobust(javax.xml.namespace.QName,java.lang.Objec
t[]) in org.apache.axis2.rpc.client.RPCServiceClient cannot be applied to (java.
lang.String,java.lang.Object[])
[javac] serviceClient.invokeRobust("echo", opAddEntryArgs);
[javac]  ^
[javac] 2 errors

change parameter back to QName causes this error

java org.apache.rampart.tomcat.sample.Client

- Deploying module: rampart-1.1
- script module activated
Exception in thread "main" java.lang.NoSuchMethodError: org.apache.axis2.context
.MessageContext.isEngaged(Ljavax/xml/namespace/QName;)Z
at org.apache.rampart.handler.WSDoAllHandler.invoke(WSDoAllHandler.java:


73)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

Re: [Axis2] Proposal to chage the method signature of set/get documentation

2007-10-31 Thread keith chapman

We can have the setter method for both but not the getter.

So we can have

public void setDocumentation(String documentation);
but we cant have
public String getDocumentation(); cause we would already have public OMNode
getDocumentation();

Thanks,
Keith.

On 11/1/07, Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote:
>
> +1 that we'd be making the keep-the-simple-case-simple rule by losing the
> String method.
>
> Keith, what's the harm in having two methods? That is, do both.
>
> Sanjiva.
>
> Tom Jordahl wrote:
> > Removing String as an argument type seems like a bad idea to me for two
> > reasons:
> >
> >
> >
> > 1. Breaking API compatibility, if it is public, is not nice.
> >
> >
> >
> > 2. If I want to put a string there (which I think you are saying goes in
> > the  elements of the WSDL) you are making me create
> > another object.  Sure it's "easy", but it doesn't make me like the API
> > much.  I think putting a string in this element is the 90+% use case,
> > right?  Who is putting XML in here?  Is there a public WSDL that you can
> > point to that does this?
> >
> >
> >
> > --
> > Tom Jordahl
> >
> > 
> >
> > *From:* keith chapman [mailto:[EMAIL PROTECTED]
> > *Sent:* Friday, October 26, 2007 8:16 AM
> > *To:* axis-dev@ws.apache.org
> > *Subject:* Re: [Axis2] Proposal to chage the method signature of set/get
> > documentation
> >
> >
> >
> > +1 for changing getDocumentation to return OMNode (no deprecation, same
> > will have to go for setDocumentation). Although this is an API method
> > its mostly used from within for generating the WSDL.
> >
> > Thanks,
> > Keith.
> >
> > On 10/26/07, *Glen Daniels* <[EMAIL PROTECTED]
> > > wrote:
> >
> > Well, +1 except for the fact that you can't overload getDocumentation()
> > and just change the return type - so there's no way to deprecate that
> > one without adding another method like getDocumentationOM().  We could
> > either do that and avoid breaking existing stuff, or just change
> > getDocumentation() and accept the incompatible change.
> >
> > --Glen
> >
> > Sanjiva Weerawarana wrote:
> >>  +1.
> >>
> >>  keith chapman wrote:
> >> > Hi Devs,
> >> >
> >> > Currently the method signature for det/get documentation in
> >> > AxisDescriptio is as follows.
> >> >
> >> > public String getDocumentation();
> >> > public void setDocumentation(String documentation);
> >> >
> >> > As you can see it treats the documentation as a string. There are
> >> > occasions where the documentation can be XML though. If the
> >> > documentation is XML what we do currently is wrap it in CDATA tags.
> >> > This works, but its not the best sollution.
> >> >
> >> > I propose deprecating the above methods and introducing the following
> >> > methods which that documentation as an OMNode.
> >> >
> >> > public OMNode getDocumentation();
> >> > public void setDocumentation(OMNode documentation);
> >> >
> >> > This will enable us to set the documentation as an OMText or
> OMElement.
> >> >
> >> > If needed we can retain the old methods without deprecating them
> (Just
> >> > leave them as a convenience method), where they will call into the
> new
> >> > method.
> >> >
> >> > The above proposal is targeted at improving the wsdl served by Axis2.
> >> > With what we have currently documentation which is XML is wrapped in
> >> > CDATA tags in the WSDL.
> >> >
> >> > Thanks,
> >> > Keith.
> >> >
> >> > --
> >> > Keith Chapman
> >> > WSO2 Inc.
> >> > Oxygen for Web Services Developers.
> >> > http://wso2.org/
> >>
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > 
> > For additional commands, e-mail: [EMAIL PROTECTED]
> > 
> >
> >
> >
> >
> > --
> > Keith Chapman
> > WSO2 Inc.
> > Oxygen for Web Services Developers.
> > http://wso2.org/
> >
>
> --
> Sanjiva Weerawarana, Ph.D.
> Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
> Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
> Member; Apache Software Foundation; http://www.apache.org/
> Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Keith Chapman
WSO2 Inc.
Oxygen for Web Services Developers.
http://wso2.org/

Re: having the list of a remote axis2 services programmatically

2007-10-31 Thread Sanjiva Weerawarana

You need some beans that expose the admin functionality as services so 
that you can control it remotely. If you look at the source for WSO2 WSAS 
you can see how we do it - you can either use WSAS' directly for it or 
just copy the bits that you care about.


See: 
http://wso2.org/repos/wso2/trunk/wsas/java/modules/admin/src/org/wso2/wsas/admin/service/


In particular you probably want ServiceAdmin.java. If you look at the WSAS 
admin console you'll see how these services are used remotely.


http://wso2.org/projects/wsas/java

Sanjiva.

EL ALAMI wrote:

Hi everyone,

I have been trying to use the axis2 API to have the list of a remote 
axis2 services , but I can’t find a way to do it.


In a more specific description, I need to write a java function that 
takes as argument the axis2 url (or its repository or something like 
that) and returns the list of all the services correctly deployed on it.


 

I think that the AxisConfiguration.getServices() method is going to be 
used, but of course I still need to have of the AxisConfiguration of the 
remote engine.


Can anybody guide me through?

I appreciate your help;)



--
Sanjiva Weerawarana, Ph.D.
Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
Member; Apache Software Foundation; http://www.apache.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/

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

RE: having the list of a remote axis2 services programmatically

2007-10-31 Thread EL ALAMI

Thank you for your replay
But I still woder if there is any better way to do this?

Do you now how to use the getConfigurationContextFromURI to get the
ConfigurationContext from a remote axis using just its URL.
 I can get this, then I can get the AxisConfiguration, and then use the
getServices method.
Thanks again for your help.

-Message d'origine-
De : Eran Chinthaka [mailto:[EMAIL PROTECTED] 
Envoyé : mercredi 31 octobre 2007 18:01
À : axis-dev@ws.apache.org
Objet : Re: having the list of a remote axis2 services programmatically

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

If your remote Axis2 server is deployed using Axis2 war, then try
accessing http://:/axis2/services/listServices.
You will be returned an "html" which has the list of services together
with their endpoints.



EL ALAMI wrote:
> Hi everyone,
> 
> I have been trying to use the axis2 API to have the list of a remote
> axis2 services , but I can?t find a way to do it.
> 
> In a more specific description, I need to write a java function that
> takes as argument the axis2 url (or its repository or something like
> that) and returns the list of all the services correctly deployed on it.
> 
>  
> 
> I think that the AxisConfiguration.getServices() method is going to be
> used, but of course I still need to have of the AxisConfiguration of the
> remote engine.
> 
> Can anybody guide me through?
> 
> I appreciate your help;)
> 

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHKSU5jON2uBzUhh8RAj2wAKCzOtrnpCbAzUDADvze0ozoLR79rgCgk63/
N4jXDizstOK57WFPwKQLmX4=
=71GH
-END PGP SIGNATURE-

-
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: [Axis2] WS-policy client support

2007-10-31 Thread Anne Thomas Manes

That's a proprietary policy assertion language. It's supported only by
BEA products. Talk to BEA and convince them to add support for the
standard OASIS WS-SecurityPolicy.

Anne

On 10/31/07, Feng Lu <[EMAIL PROTECTED]> wrote:
>
> Hello friends,
>
> I am wondering whether Axis2 support WS-policy client? My WSDL server is
> Weblogic and the WSDL has following WS-policy. I am not sure whether Axis2
> will be able to handle WS-policy in such case. If it does, could anybody let
> me know how to implement the client side support for this? Any special
> handling in the stub genration?
>
>
>
> - 
>
>
> -  xmlns:wssp="http://www.bea.com/wls90/security/policy";>
>
>
> - 
>
>
> -  TokenType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#UsernameToken";>
>
>
>Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText";
> />
>   
>   
>   
>   
>
> Thanks a lot for your help!
>
> Frank
> __
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com

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

Re: having the list of a remote axis2 services programmatically

2007-10-31 Thread Eran Chinthaka

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

If your remote Axis2 server is deployed using Axis2 war, then try
accessing http://:/axis2/services/listServices.
You will be returned an "html" which has the list of services together
with their endpoints.



EL ALAMI wrote:
> Hi everyone,
> 
> I have been trying to use the axis2 API to have the list of a remote
> axis2 services , but I can?t find a way to do it.
> 
> In a more specific description, I need to write a java function that
> takes as argument the axis2 url (or its repository or something like
> that) and returns the list of all the services correctly deployed on it.
> 
>  
> 
> I think that the AxisConfiguration.getServices() method is going to be
> used, but of course I still need to have of the AxisConfiguration of the
> remote engine.
> 
> Can anybody guide me through?
> 
> I appreciate your help;)
> 

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHKSU5jON2uBzUhh8RAj2wAKCzOtrnpCbAzUDADvze0ozoLR79rgCgk63/
N4jXDizstOK57WFPwKQLmX4=
=71GH
-END PGP SIGNATURE-

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

Re: [Axis2] Proposal to chage the method signature of set/get documentation

2007-10-31 Thread Sanjiva Weerawarana

+1 that we'd be making the keep-the-simple-case-simple rule by losing the 
String method.


Keith, what's the harm in having two methods? That is, do both.

Sanjiva.

Tom Jordahl wrote:
Removing String as an argument type seems like a bad idea to me for two 
reasons:


 


1. Breaking API compatibility, if it is public, is not nice.

 

2. If I want to put a string there (which I think you are saying goes in 
the  elements of the WSDL) you are making me create 
another object.  Sure it’s “easy”, but it doesn’t make me like the API 
much.  I think putting a string in this element is the 90+% use case, 
right?  Who is putting XML in here?  Is there a public WSDL that you can 
point to that does this?


 


--
Tom Jordahl



*From:* keith chapman [mailto:[EMAIL PROTECTED]
*Sent:* Friday, October 26, 2007 8:16 AM
*To:* axis-dev@ws.apache.org
*Subject:* Re: [Axis2] Proposal to chage the method signature of set/get 
documentation


 

+1 for changing getDocumentation to return OMNode (no deprecation, same 
will have to go for setDocumentation). Although this is an API method 
its mostly used from within for generating the WSDL.


Thanks,
Keith.

On 10/26/07, *Glen Daniels* <[EMAIL PROTECTED] 
> wrote:


Well, +1 except for the fact that you can't overload getDocumentation()
and just change the return type - so there's no way to deprecate that
one without adding another method like getDocumentationOM().  We could
either do that and avoid breaking existing stuff, or just change
getDocumentation() and accept the incompatible change.

--Glen

Sanjiva Weerawarana wrote:

 +1.

 keith chapman wrote:
> Hi Devs,
>
> Currently the method signature for det/get documentation in
> AxisDescriptio is as follows.
>
> public String getDocumentation();
> public void setDocumentation(String documentation);
>
> As you can see it treats the documentation as a string. There are
> occasions where the documentation can be XML though. If the
> documentation is XML what we do currently is wrap it in CDATA tags.
> This works, but its not the best sollution.
>
> I propose deprecating the above methods and introducing the following
> methods which that documentation as an OMNode.
>
> public OMNode getDocumentation();
> public void setDocumentation(OMNode documentation);
>
> This will enable us to set the documentation as an OMText or OMElement.
>
> If needed we can retain the old methods without deprecating them (Just
> leave them as a convenience method), where they will call into the new
> method.
>
> The above proposal is targeted at improving the wsdl served by Axis2.
> With what we have currently documentation which is XML is wrapped in
> CDATA tags in the WSDL.
>
> Thanks,
> Keith.
>
> --
> Keith Chapman
> WSO2 Inc.
> Oxygen for Web Services Developers.
> http://wso2.org/



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

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






--
Keith Chapman
WSO2 Inc.
Oxygen for Web Services Developers.
http://wso2.org/



--
Sanjiva Weerawarana, Ph.D.
Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
Member; Apache Software Foundation; http://www.apache.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/

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

ExceptionInInitializerError when trying to create a new ServiceClient

2007-10-31 Thread Iyengar, Kumar

Hi all,

 

Has anyone seen this? It was working for me till I tried removing some
of the jar files that are part of axis2. After that I added the removed
ones back in and still get this error. I am using Axis2 1.3 and it is
generating this error when trying to create a ServiceClient.

 

Exception in thread "main" java.lang.ExceptionInInitializerError

  at org.apache.axis2.util.XMLUtils.toOM(XMLUtils.java:564)

  at
org.apache.axis2.deployment.DescriptionBuilder.buildOM(DescriptionBuilde
r.java:96)

  at
org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(AxisConfigB
uilder.java:79)

  at
org.apache.axis2.deployment.DeploymentEngine.populateAxisConfiguration(D
eploymentEngine.java:615)

  at
org.apache.axis2.deployment.FileSystemConfigurator.getAxisConfiguration(
FileSystemConfigurator.java:115)

  at
org.apache.axis2.context.ConfigurationContextFactory.createConfiguration
Context(ConfigurationContextFactory.java:64)

  at
org.apache.axis2.context.ConfigurationContextFactory.createConfiguration
ContextFromFileSystem(ConfigurationContextFactory.java:180)

  at
org.apache.axis2.client.ServiceClient.configureServiceClient(ServiceClie
nt.java:146)

  at
org.apache.axis2.client.ServiceClient.(ServiceClient.java:139)

  at
org.apache.axis2.client.ServiceClient.(ServiceClient.java:228)

  at
com.bmc.arsys.ws.client.WebServiceSoapClient.call(WebServiceSoapClient.j
ava:178)

  at
com.bmc.arsys.ws.client.WebServiceSoapClient.getTestWS(WebServiceSoapCli
ent.java:795)

  at
com.bmc.arsys.ws.client.WebServiceSoapClient.main(WebServiceSoapClient.j
ava:616)

Caused by: java.lang.IllegalStateException: No valid ObjectCreator
found.

  at
org.apache.axiom.om.util.StAXUtils$Pool.(StAXUtils.java:64)

  at org.apache.axiom.om.util.StAXUtils.(StAXUtils.java:88)

  ... 13 more

 

Any help is appreciated.

 

Thanks

 

-kumar

[jira] Created: (AXIS2-3318) Java2WSDL -p2n command line issue

2007-10-31 Thread Joy Kenneth Harry (JIRA)

Java2WSDL -p2n command line issue
-

 Key: AXIS2-3318
 URL: https://issues.apache.org/jira/browse/AXIS2-3318
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: Tools
Affects Versions: 1.3
 Environment: Windows XP, Eclipse europa
Reporter: Joy Kenneth Harry
Priority: Blocker
 Fix For: 1.3


If Java2WSDL's -p2n command line option is used as

-p2n "test.package urn:MyPackage"

Gives exception ***An error occured while generating codeString index out of 
range: -2***

It works fine if used in the following manner i.e COMMA between the pacakge 
name and namespace.
-p2n "test.package, urn:MyPackage" 

The command line usage text should be updated.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[Axis2] WS-policy client support

2007-10-31 Thread Feng Lu

Hello friends,

I am wondering whether Axis2 support WS-policy client? My WSDL server is 
Weblogic and the WSDL has following WS-policy. I am not sure whether Axis2 will 
be able to handle WS-policy in such case. If it does, could anybody let me know 
how to implement the client side support for this? Any special handling in the 
stub genration?

- 
- http://www.bea.com/wls90/security/policy";>
- 
- http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#UsernameToken";>
  http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText";
 /> 
  
  
  
  

Thanks a lot for your help!

Frank

__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com

having the list of a remote axis2 services programmatically

2007-10-31 Thread EL ALAMI

Hi everyone,

I have been trying to use the axis2 API to have the list of a remote axis2
services , but I can't find a way to do it.

In a more specific description, I need to write a java function that takes
as argument the axis2 url (or its repository or something like that) and
returns the list of all the services correctly deployed on it.

 

I think that the AxisConfiguration.getServices() method is going to be used,
but of course I still need to have of the AxisConfiguration of the remote
engine. 

Can anybody guide me through?

I appreciate your help;)

[jira] Assigned: (AXIS2-3315) Compile error in generated JUnit

2007-10-31 Thread Lahiru Sandakith (JIRA)


 [ 
https://issues.apache.org/jira/browse/AXIS2-3315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lahiru Sandakith reassigned AXIS2-3315:
---

Assignee: Amila Chinthaka Suriarachchi

Amila , can you please look in to this, Assigning to you.


> Compile error in generated JUnit
> 
>
> Key: AXIS2-3315
> URL: https://issues.apache.org/jira/browse/AXIS2-3315
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>  Components: codegen
>Affects Versions: 1.3
> Environment: Windows XP
>Reporter: Kathy Chan
>Assignee: Amila Chinthaka Suriarachchi
>
> Using Axis2 v1.3, when I issue the following:
> wsdl2java -uri Persondetails.wsdl -t
> to generate JUnit testcase for client,I got a PersondetailsTest.java 
> generated with compile error:
> public  void testStartgetPersonDetails() throws java.lang.Exception{
> wtp.PersondetailsStub stub = new wtp.PersondetailsStub();
>  
> stub.startgetPersonDetails(
>  ,
> new tempCallbackN1000C()
> );
>   
> }
> Note that there's a "," with no field in the call to 
> stub.startgetPersonDetails.
> Here's the Persondetails.wsdl used:
> http://wtp";
>   xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/";
>   xmlns:ns0="http://wtp/xsd";
>   xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/";
>   xmlns:http="http://schemas.xmlsoap.org/wsdl/http/";
>   xmlns:ns1="http://org.apache.axis2/xsd";
>   xmlns:xs="http://www.w3.org/2001/XMLSchema";
>   xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
>   xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
>   targetNamespace="http://wtp";>
>   
>   Please Type your service description here
>   
>   
>   http://wtp/xsd";
>   attributeFormDefault="qualified" 
> elementFormDefault="qualified"
>   targetNamespace="http://wtp/xsd";>
>   
>   
>   
>nillable="true"
>   type="xs:string" />
>   
>   
>   
>   
>   
>   
>nillable="true"
>   type="xs:string" />
>nillable="true"
>   type="xs:int" />
>nillable="true"
>   type="ns:Address" />
>nillable="true"
>   type="xs:string" />
>nillable="true"
>   type="xs:string" />
>nillable="true"
>   type="xs:string" />
>   
>   
>   
>   
>   
>   
>nillable="true"
>   type="xs:string" />
>  type="xs:string" />
>nillable="true"
>   type="xs:string" />
>  type="xs:string" />
>  type="xs:string" />
>nillable="true"
>   type="xs:string" />
>nillable="true"
>   type="xs:string" />
>   
>   
>   
>   
>   
>   
>/>
>   
>   
>   
>   
>   
>   
>  
> xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl";
>   message="axis2:getPersonDetailsMessage"
>   wsaw:Action="urn:getPersonDetails" />
>   
>   
>   
>  
> xmlns:

[Axis2] Services.xml is wrong but when the WSDL queried is corrected somewhere?

2007-10-31 Thread Dobri Kitipov

Hi everybody,
I am using Axis2 1.3 and rampart2 1.2.
I observed something interesting. I am using a custom tool to generate a
services.xml. This tool is under development so it did not works perfect at
the moment. I am testing the symmetric binding and have the following
services.xml generated:



  
Web Service HelloPojo
com.mycompany.wsstack.pojo.HelloPojo


  http://www.w3.org/2004/08/wsdl/in-out"/>


http://schemas.xmlsoap.org/ws/2004/09/policy"; xmlns:wsu="
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd
">
  

  http://schemas.xmlsoap.org/ws/2005/07/securitypolicy";>

  

  http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/Never";>

  
  

  

  
  http://schemas.xmlsoap.org/ws/2005/07/securitypolicy";>

  

  
  

  

  
  

  http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/Never";>

  
  

  

  

  
  http://schemas.xmlsoap.org/ws/2005/07/securitypolicy";>

  
  

  
  http://schemas.xmlsoap.org/ws/2005/07/securitypolicy";>

  
  http://ws.apache.org/rampart/policy";>
service
client

com.mycompany.wsstack.pwcb.PasswordCallbackHandler


  
JKS
service.jks
openssl
  


  
JKS
service.jks
openssl
  

  

  



  


You can see in bold that  is not correctly formed. it
has two opening and closing   tags. The second one
should be replaced by  tag. Another problem is that

block is set twice into the file.
THE interesting thing is that when I deploy the AAR at Tomcat 5.5.20 and
query the ?wsdl the policy in the wsdl returned is correct and obviously
fixed at some stage. Here is an excerpt from the wsdl that contains the
policy:

http://schemas.xmlsoap.org/ws/2004/09/policy";
xmlns:wsu="
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";
wsu:Id="User defined">


http://schemas.xmlsoap.org/ws/2005/07/securitypolicy";>



http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/Never";>



















http://schemas.xmlsoap.org/ws/2005/07/securitypolicy";>





http://schemas.xmlsoap.org/ws/2005/07/securitypolicy";>






In bold you can see that the  is somehow corrected and
normalized. Do you know where this happens?

Thank you in advance!
Dobri

Re: [AXIS2] WS-policy support

2007-10-31 Thread Sanka Samaranayke


Hi,

Once you generated the stub, you need to do the followings

1) Creating a stub instance providing a ConfigurationContext. The 
ConfigurationContext should point to a axis2 repository where it contains the 
Rampart module. It is necessary since Rampart module is responsible for 
interpreting any WS-Security policies.

e.g.
ConfigurationContext config = 
ConfigurationContextFactory.createConfigurationContextFromFileSystem("path-to-repository");
SampleStub stub = new SampleStub(config);

2) Set Username and Password

e.g.
ServiceClient serviceClient = stub._getServiceClient(co);

Options options = serviceClient.getOptions();
options.setUserName("username");
options.setPassword("password");

Now you should be able to use that stub instance to communicate with that particular Web service without any further configuration. 


HTH,
Sanka
   






[EMAIL PROTECTED] wrote:

Hi there,

Does Axis 2 version1.3 support WS-policy? If it does, does anybody have
sample codes for the Client support of how to use WS-policy?
Our current situation is we have WS service (WSDL) provided with WS-policy.
We are interested to use Axis2 for the client to talk to the WS but we are
not sure how to get through the WS-policy. So if anybody knows s=some
sample code (could be as sample of to set User name/passcode) would be
great!

Thanks in advance!

Feng


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


  



--
Sanka Samaranayake
WSO2 Inc.

http://www.bloglines.com/blog/sanka
http://www.wso2.org/


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

[jira] Commented: (AXIS2-3293) NPE in AxisEngine when trying to use TCP transport

2007-10-31 Thread Adrian Lang (JIRA)


[ 
https://issues.apache.org/jira/browse/AXIS2-3293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539023
 ] 

Adrian Lang commented on AXIS2-3293:


I got the same problem: 


import org.apache.axis2.Constants;
import org.apache.axis2.description.TransportOutDescription;
import org.apache.log4j.Appender;
import org.apache.log4j.ConsoleAppender;
import org.apache.log4j.Logger;
import org.apache.log4j.PatternLayout;

import pcograb.service_wsdl.ServiceStub;
import pcograb.service_wsdl.ServiceStub.GetImage;
import pcograb.service_wsdl.ServiceStub.GetImageResponse;


public class pcoGrabClient {
public static void main(String[] args) throws Exception {

Appender newAppender = new ConsoleAppender(new PatternLayout("%r [%t] 
%-5p %c - %m%n"));

Logger.getRootLogger().addAppender(newAppender);

ServiceStub stub = new ServiceStub("tcp://pcograbber:5000");
stub._getServiceClient().getOptions().setTransportOut(new 
TransportOutDescription(Constants.TRANSPORT_TCP));  

//Create the request
GetImage request = new GetImage();

//Invoke the service
GetImageResponse response = stub.getImage(request);

}
}




http://localhost:80/Service.wsdl";
 xmlns:tns="http://localhost:80/Service.wsdl";
 xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";
 xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/";
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
 xmlns:xsd="http://www.w3.org/2001/XMLSchema";
 xmlns:pcoGrab="http://tempuri.org/pcoGrab.xsd";
 xmlns:SOAP="http://schemas.xmlsoap.org/wsdl/soap/";
 xmlns:MIME="http://schemas.xmlsoap.org/wsdl/mime/";
 xmlns:DIME="http://schemas.xmlsoap.org/ws/2002/04/dime/wsdl/";
 xmlns:WSDL="http://schemas.xmlsoap.org/wsdl/";
 xmlns="http://schemas.xmlsoap.org/wsdl/";>



 http://tempuri.org/pcoGrab.xsd";
  xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";
  xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/";
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
  xmlns:xsd="http://www.w3.org/2001/XMLSchema";
  xmlns:pcoGrab="http://tempuri.org/pcoGrab.xsd";
  xmlns="http://www.w3.org/2001/XMLSchema";
  elementFormDefault="unqualified"
  attributeFormDefault="unqualified">
  http://schemas.xmlsoap.org/soap/encoding/"/>
  
  
   


   
  
  
  
   

 

   
  
  
  
   

 
 
 
 

   
  
  
  
   

 

   
  
 




 



 



 



 



 
  Service definition of function 
pcoGrab__getImage
  
  
 
 
  Service definition of function pcoGrab__setROI
  
  
 



 http://schemas.xmlsoap.org/soap/http"/>
 
  
  
 
  
  
 
  
 
 
  
  
 
  
  
 
  
 



 gSOAP 2.7.9d generated service definition
 
  http://localhost:80"/>
 





> NPE in AxisEngine when trying to use TCP transport
> --
>
> Key: AXIS2-3293
> URL: https://issues.apache.org/jira/browse/AXIS2-3293
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>  Components: client-api
>Affects Versions: 1.3
>Reporter: dror yaffe
>
> Here is the excpetion:
> java.lang.NullPointerException
>   at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:396)
>   at 
> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:374)
>   at 
> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211)
>   at 
> org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
>   at 
> org.tempuri.KongServerHttpEndpointStub.Send(KongServerHttpEndpointStub.java:184)
>   at org.tempuri.Main.doWork(Main.java:45)
>   at org.tempuri.Main.main(Main.java:57)
> client code:
>  public void doWork() throws Exception{
>  String 
> TARGET_END_POINT="tcp://127.0.0.1:8080/KongServerWebApplication/KongServerHttpEndpoint.asmx";
>   
>  KongServerHttpEndpointStub stub = new 
> KongServerHttpEndpointStub(TARGET_END_POINT);
>  EndpointReference target = new EndpointReference(TARGET_END_POINT);
> Options options = new Options();
> options.setTo(target);  
> options.setSenderTransport(Constants.TRANSPORT_TCP, cfg);
> options.setTransportInProtocol(Constants.TRANSPORT_TCP);
> TransportOutDescription x = new 
> TransportOutDescription(Constants.TRANSPORT_TCP);
> options.setTransportOut(x);
> stub._getServiceClient().setOptions(options);
>   
> 
> Send send = new Send();
>   KongMessage msg= new KongMessage();   
> send.setMessage(msg);
> SendResponse res = stub.Send(send);
> System.out.println("got res = "+res.getSendResult());
>  
>   }
> I used AXIS2 eclipse plugin code generator, here

Re: [Axis2] Axis2 Release Restructuring

Re: [Axis2] WS-policy client support

Re: [Axis2] Axis2 Release Restructuring

Re: [Axis2] Axis2 Release Restructuring

[jira] Created: (AXIS2-3319) engageModule for ContextMessage has wrong parameters

Re: [Axis2] Proposal to chage the method signature of set/get documentation

Re: having the list of a remote axis2 services programmatically

RE: having the list of a remote axis2 services programmatically

Re: [Axis2] WS-policy client support

Re: having the list of a remote axis2 services programmatically

Re: [Axis2] Proposal to chage the method signature of set/get documentation

ExceptionInInitializerError when trying to create a new ServiceClient

[jira] Created: (AXIS2-3318) Java2WSDL -p2n command line issue

[Axis2] WS-policy client support

having the list of a remote axis2 services programmatically

[jira] Assigned: (AXIS2-3315) Compile error in generated JUnit

[Axis2] Services.xml is wrong but when the WSDL queried is corrected somewhere?

Re: [AXIS2] WS-policy support

[jira] Commented: (AXIS2-3293) NPE in AxisEngine when trying to use TCP transport

19 matches

Site Navigation

Mail list logo

Footer information