date:20080428

Re: The WS Crazy Train!

2008-04-28 Thread Brennan Spies

Scott,

That's a tall order. There's lots to say about this space, and it won't be 
contained in one web page. Can't help you with the Xanax, but I can give you 
the brief tour of WS in Java. Here goes...

1. At the high level, your first decision is SOAP vs. REST. REST implies POX 
(plain old XML)--though it's not necessarily the case, that's the way the 
majority of RESTful services are developed. SOAP is just a message format, but 
all of the WS-* standards (and there's a lot of them) and WSDL (at least until 
v.2.0) revolve entirely around using SOAP; hence the perceived complexity 
because there's more to learn. REST has less structure, so it can be simpler 
when developing simple web services; however, if you have other requirements, 
such as security or policy, going with REST could be more difficult and 
error-prone than SOAP. It's over-simplifying a bit, but the distinction can be 
summed up as "go with the standards" in SOAP or "roll your own" with REST. 
Taking a look at some of the more popular web services from Google, Amazon, 
etc. may give you a better feeling for this.

2. Your second decision is going to be which Web Services stack to use. In 
Java, the major ones are Apache Axis 2.0, Apache CXF, Spring Web Services, and 
the JAX-WS reference implementation (on java.net). You'll have to match their 
features against your requirements to see which one fits you best. There's a 
fair amount of overlap in features (and even in the 3rd party libs they use), 
but there are significant differences as well. I'd recommend not using Axis 1.0 
at this stage, since it is about 4-5 times slower than the newer stacks under 
load.

3. JAXB is simply a framework for XML-Java binding, one among many: JiBX, XML 
Beans, Castor, ADB, etc. Which one you use may be decided by which one(s) the 
stack in #2 you choose supports (you'll choose JAXB, for example, if you use 
Sun's JAX-WS reference implementation), but all except JAX-WS RI support more 
than one binding framework.

4. XML Schema is the standard way of defining XML types in SOAP/WSDL, but there 
are others. In WSDL 1.2 and 2.0, for example, you 
can(http://www.w3.org/TR/wsdl20-altschemalangs/) use Relax NG, but--practically 
speaking--XML Schema rules the roost here.

5. Most WS frameworks (from #2) support two basic styles of development: 
top-down (write WSDL, generate Java--WSDL2Java, for instance) and bottom-up 
(generate WSDL and other artifacts from your Java code). I prefer the first, 
but bottom up may be simpler if you are just starting out, esp. if you already 
have code that you are adding a web service to. JSR-181 (JAX-WS) is 
particularly nice for this approach, since you just add annotations to your 
existing code.

6.  If you must buy a book, don't buy anything that's been published more than 
a year ago. The landscape has changed a lot in the last year or two. One of my 
favorites, "J2EE Web Services" by Richard Monson-Haefel, is already 
out-of-date. 

Well, that's it for the nickel tour. The brush strokes are pretty broad here, 
but I hope I've given you a better idea.

Brennan
  - Original Message - 
  From: [EMAIL PROTECTED] 
  To: axis-user@ws.apache.org 
  Sent: Monday, April 28, 2008 4:37 PM
  Subject: The WS Crazy Train!


  Can someone either provide me a URL for xanax or a site that explains the 
interplay between SOAP/JAXB/WSDL/Schema/blah, blah, yada. yada? I am trying to 
figure out what is actually necessary to produce & consume web services in Java 
and I am hearing that many of these technologies are optional!  In fact, today 
it was decided that WSDL2Java produced too many artifacts and that writing web 
services could be much simpler.  How do RESTful web services play into this 
mix, and what are the pros/cons to the permutations of ws stacks?  I would 
gladly throw down my AMEX if someone can recommend a good book/resource that 
might clear this confusion.

  Peace,
  -- 
  Scott
  [EMAIL PROTECTED]

RE: org.apache.axis2.AxisFault: HTTP Transport error : '501' - 'Not Implemented' message

2008-04-28 Thread Pinaki Chandrasekhar

Thanks Daniel.
I shall try out your recommendations and let you know where I am.
Regards,
Pinaki

-Original Message-
From: Daniel Hagen [mailto:[EMAIL PROTECTED]
Sent: Sunday, April 27, 2008 8:07 PM
To: axis-user@ws.apache.org
Subject: Re: org.apache.axis2.AxisFault: HTTP Transport error : '501' -
'Not Implemented' message


Hi Pinaki,

this looks like a HTTP issue to me where the SQUID Proxy between client
and server does have a problem with the Chunked Transfer Encoding the
client uses in conjunction with a HTTP POST request.

Squid's support for Chunked Transfer Encoding when communicating with
the client is incomplete; I have seen the exact behaviour you described
for HTTP PUT requests but was unaware that this also is the case for
HTTP POST.

Maybe you could try to convince your webservice client not to use
Chunked Transfer Encoding but to
- either close the HTTP connection after each request (which can be a
performance problem when you are making many requests in a short time frame)
- or send a Content-Length along with the request

Another workaround would be to disable the use of a proxy if your
environment allows you to connect to the Webservice server directly.

Best regards

Daniel

Pinaki Chandrasekhar schrieb:
> Hello Friends,
> I have been trying to figure out the problem for a few days and really
need
> some help.
> My j2ee application integrates with IPX gateway for Short messaging
service.
> This is implemented as a WebService by IPX and they provided me with thge
> precompiled client stub files ( compiled using axis 2.1.1.1)
> I am new to web services and axis. I went through all the installation and
> tutorial successfully with a helloworld ws example and the axis2userguide
> example that is provided.
> However I am stuck when I try integrating with my existing j2ee
application.
> My j2ee app is the client for the web service and I compiled it
successfully
> with the client stubs set on the classpath. But I keep getting this error
> whenever it needs to send the message:
> org.apache.axis2.AxisFault: HTTP Transport error : '501' - 'Not
Implemented'
>
> I have the server logs here for your reference.
>
> I may be messing  things up in configuring the whole app on the server
with
> axis 2
>
> I am using the Jboss-4.0.3Sp1 as the server and also have axis2 installed
on
> the same machine with the AXIS2_HOME set properly. I also have the
axis.war
> file deployed on the server.
>
> Please, can someone help when to rectify the problem.
>
> Thanks in advance,
>
> pc
>
>
>
> this is the server log when I send a short code through my phone. It goes
to
> the iPX gateway who reroute it back to my application. It seems like the
> message is all getting prepared and throws up an error while about to
send.
>
> 2008-04-23 10:31:15,769 INFO [ReceiveSMSServlet] Receive SMS Message
>
> 2008-04-23 10:31:15,769 DEBUG [ReceiveSMSServlet] SMS
Received:1208917875769
>
> 2008-04-23 10:31:15,769 DEBUG [ReceiveSMSServlet] IPX
Receive --->TimeStamp
> : 20080423 04:32:44
>
> 2008-04-23 10:31:15,769 DEBUG [ReceiveSMSServlet] IPX Receive --->Operator
:
> DiGi
>
> 2008-04-23 10:31:15,769 DEBUG [ReceiveSMSServlet] IPX
Receive --->MessageId
> : 1-1703551585
>
> 2008-04-23 10:31:15,769 DEBUG [ReceiveSMSServlet] IPX Receive --->Message
:
> Store fs 009
>
> 2008-04-23 10:31:15,769 DEBUG [ReceiveSMSServlet] IPX
> Receive --->DestinationAddress : 32088
>
> 2008-04-23 10:31:15,769 DEBUG [ReceiveSMSServlet] IPX
> Receive --->OriginatorAddress : 60169063492
>
> 2008-04-23 10:31:15,769 DEBUG [ReceiveSMSServlet] Local
> Context.PROVIDER_URL: java.naming.provider.url
>
> 2008-04-23 10:31:15,779 INFO [ContentControllerBean] get content for
> requestCode = fs 009
>
> 2008-04-23 10:31:15,779 DEBUG
> [org.jboss.ejb.plugins.cmp.jdbc.JDBCEJBQLQuery.Content#findByKeyword]
> Executing SQL: SELECT DISTINCT t0_c.ContentId, t0_c.Keyword, t0_c.Tariff,
> t0_c.Type, t0_c.Title, t0_c.Status, t0_c.creationDate FROM content t0_c
> WHERE (t0_c.Keyword = ?)
>
> 2008-04-23 10:31:15,789 DEBUG
> [org.jboss.ejb.plugins.cmp.jdbc.JDBCLoadRelationCommand.Content] load
> relation SQL: SELECT content.StoreId, store.Name, store.Status,
> store.mobileNumber, store.freeRequestCount FROM content content, store
store
> WHERE (content.StoreId=store.StoreId) AND ((content.ContentId=?))
>
> 2008-04-23 10:31:15,799 DEBUG
> [org.jboss.ejb.plugins.cmp.jdbc.JDBCEJBQLQuery.Media#findByContent]
> Executing SQL: SELECT DISTINCT t0_m.MediaId, t0_m.fileSize, t0_m.fileName,
> t0_m.Height, t0_m.Width FROM media t0_m, content t1_m_content WHERE
> ((t1_m_content.ContentId=?) AND t0_m.ContentId=t1_m_content.ContentId)
>
> 2008-04-23 10:31:15,809 DEBUG
> [org.jboss.ejb.plugins.cmp.jdbc.JDBCEJBQLQuery.Store#findStore] Executing
> SQL: SELECT DISTINCT t0_s.StoreId FROM store t0_s WHERE (t0_s.StoreId = ?)
>
> 2008-04-23 10:31:15,819 DEBUG
> [org.jboss.ejb.plugins.cmp.jdbc.JDBCEJBQLQuery.Setting#findSetting]
> Executing SQL: SELECT t0_s.SettingId, t0_s.SmsServerPassword,
> t0_

The WS Crazy Train!

2008-04-28 Thread stanlick

Can someone either provide me a URL for xanax or a site that explains the
interplay between SOAP/JAXB/WSDL/Schema/blah, blah, yada. yada? I am trying
to figure out what is actually necessary to produce & consume web services
in Java and I am hearing that many of these technologies are optional!  In
fact, today it was decided that WSDL2Java produced too many artifacts and
that writing web services could be much simpler.  How do RESTful web
services play into this mix, and what are the pros/cons to the permutations
of ws stacks?  I would gladly throw down my AMEX if someone can recommend a
good book/resource that might clear this confusion.

Peace,
-- 
Scott
[EMAIL PROTECTED]

xmlschema simpleContent for ADB

2008-04-28 Thread searl

Hi,

I'm trying to use some existing schema xsd,
with the wsdl2java utility and ADB,
that contains the following:

  

  Name or code with an (optional) authority.  Text
token.  
  If the codeSpace attribute is present, then its value should identify
a dictionary, thesaurus 
  or authority for the term, such as the organisation who assigned the
value, 
  or the dictionary from which it is taken.  
  A text string with an optional codeSpace attribute. 


  

  

  

I'm getting:
 [java] Caused by: org.apache.axis2.schema.SchemaCompilationException:
Unsupported content Simple Content !

Has anyone done any work in the ADB lately to handle SimpleContent?

leon

-- 
Leon S. Searl, Software Research Engineer
Information and Telecommunication Technology Center, University of Kansas
Nichols Hall, 2335 Irving Hill Road, Lawrence, KS 66045-7612
Ph: 785-864-7820 Fax: 785-864-0387
http://www.ittc.ku.edu


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

RE: java.lang.NoSuchMethodError: javax.xml.namespace.QName

2008-04-28 Thread Cooper, Jeremy

Make sure that you don't have the weblogic jar in your classpath.
Weblogic ships a different version of the QName class

From: Anthony Bull [mailto:[EMAIL PROTECTED] 
Sent: Monday, April 28, 2008 1:48 PM
To: axis-user@ws.apache.org
Subject: Re: java.lang.NoSuchMethodError: javax.xml.namespace.QName

Hi Peter, 

I'm not positive on it, but I seem to remember getting this error when I
used a different version of the addressing/rampart modules with a
specific version of Axis 2.

E.g.  Axis 2 1.3 and rampart 1.2 and addressing 1.2.  

Changing all modules are jars to be for the same release of Axis 2 fixed
it up.

Rajesh, Peter (CLAIMS, WIP) wrote: 

Hi, 

In the java client, to invoke an Axis2 webservice, when we try to create
the ConfigurationContext as below, 

ConfigurationContext ctx =
ConfigurationContextFactory.createConfigurationContextFromFileSystem("C:
/Test/build/client_repository", null);

Below exception is thrown, 

java.lang.NoSuchMethodError:
javax.xml.namespace.QName.(Ljava/lang/String;Ljava/lang/String;Lja
va/lang/String;)V 

Please advice. 

Thanks & Regards, 

Peter Rajesh

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

*

-- 

Anthony
- 
Anthony Bull
Senior Developer
Black Coffee Software Ltd
PO Box 10-192 The Terrace
Wellington, New Zealand

[EMAIL PROTECTED]
Ph  +64 4 472 8818
Fax +64 4 472 8811
- 
www.bcsoft.co.nz
--- 
This email may contain confidential or privileged information, 
and is intended for use only by the addressee, or addressees. 
If you are not the intended recipient please advise the sender 
immediately and do not copy, use or disclose the contents to 
any other person or organisation.
Black Coffee Software Ltd accepts no responsibility for viruses 
received with this email, or to any changes made to the original 
content. Any views or opinions expressed in this email may be
personal to the sender and are not necessarily those of Black 
Coffee Software Ltd.
--- 

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

The information contained in this message and any accompanying attachments may 
contain privileged, private and/or confidential information protected by state 
and federal law.  Penalties may be assessed for unauthorized use and/or 
disclosure.  This message and any attachments are intended for the designated 
recipient only.  If you have received this information in error, please notify 
the sender immediately and return or destroy the information.

This e-mail transmission and any attachments are believed to have been sent 
free of any virus or other defect that might affect any computer system into 
which it is received and opened. It is, however, the recipient's responsibility 
to ensure that the e-mail transmission and any attachments are virus free, and 
the sender accepts no responsibility for any damage that may in any way arise 
from their use.

Re: java.lang.NoSuchMethodError: javax.xml.namespace.QName

2008-04-28 Thread Anthony Bull

Title: java.lang.NoSuchMethodError: javax.xml.namespace.QName




Hi Peter, 

I'm not positive on it, but I seem to remember getting this error when
I used a different version of the addressing/rampart modules with a
specific version of Axis 2.

E.g.  Axis 2 1.3 and rampart 1.2 and addressing 1.2.  

Changing all modules are jars to be for the same release of Axis 2
fixed it up.

Rajesh, Peter (CLAIMS, WIP) wrote:

  
  
  
  Hi, 
  In the java client, to invoke an Axis2
webservice, when we try to create the ConfigurationContext as below,
  
  ConfigurationContext ctx =
ConfigurationContextFactory.createConfigurationContextFromFileSystem("C:/Test/build/client_repository",
null);
     
  Below exception is thrown, 
  java.lang.NoSuchMethodError:
javax.xml.namespace.QName.(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)V
  
  Please advice. 
  Thanks & Regards, 
  Peter Rajesh
  
  
*
This communication, including attachments, is
for the exclusive use of addressee and may contain proprietary,
confidential and/or privileged information. If you are not the intended
recipient, any use, copying, disclosure, dissemination or distribution
is
strictly prohibited. If you are not the intended recipient, please
notify
the sender immediately by return e-mail, delete this communication and
destroy all copies.
*
  



-- 

Anthony
- 
Anthony Bull
Senior Developer
Black Coffee Software Ltd
PO Box 10-192 The Terrace
Wellington, New Zealand
 
[EMAIL PROTECTED]
Ph  +64 4 472 8818
Fax +64 4 472 8811
- 
www.bcsoft.co.nz
--- 
This email may contain confidential or privileged information, 
and is intended for use only by the addressee, or addressees. 
If you are not the intended recipient please advise the sender 
immediately and do not copy, use or disclose the contents to 
any other person or organisation.
Black Coffee Software Ltd accepts no responsibility for viruses 
received with this email, or to any changes made to the original 
content. Any views or opinions expressed in this email may be
personal to the sender and are not necessarily those of Black 
Coffee Software Ltd.
--- 




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

Obtaining the connecting client IP in a CallbackHandler invoked by Rampart

2008-04-28 Thread Nate Roe


I'm trying to obtain the IP of the connecting client from within the 
CallbackHandler invoked by Rampart.

This can be obtained from messageContext.getProperty("REMOTE_ADDR") however 
MessageContext.getCurrentMessageContext() often (though not always) returns 
null.

>From my observations, it appears that the messageContext is null when the 
>client connects to the server, but the messageContext is populated when the 
>server responds to the client.

How can I reliably obtain the connecting client's IP?

Thanks,
Nate Roe

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

RE: Axis + Jetty disable chunking

2008-04-28 Thread Krystian Szczesny

No I am not using it.
I've got wsdl files, from which I have generated all the java code
[wsdl2java].
Then I have created a simple class with methods for each operation in a
service.
Then in my aar file I've got service.xml file in which my class is
listed as a ServiceClass and all the operations are listed.

I am not implementing any interface there etc. I am just returning
OMElement.

I must admit, I didn't write it so I might confuse some things.

I am using SOAP UI as a client for testing at the moment.

I've just found a way to get to a ServiceContext from my class and will
try to set the Chunked false options there.

> -Original Message-
> From: Michele Mazzucco [mailto:[EMAIL PROTECTED]
> Sent: 28 April 2008 17:39
> To: axis-user@ws.apache.org
> Subject: Re: Axis + Jetty disable chunking
> 
> 
> On 28 Apr 2008, at 16:46, Krystian Szczesny wrote:
> 
> > Thanks,
> > Krystian
> >
> >> -Original Message-
> >> From: Michele Mazzucco [mailto:[EMAIL PROTECTED]
> >> Sent: 28 April 2008 15:43
> >> To: axis-user@ws.apache.org
> >> Subject: RE: Axis + Jetty disable chunking
> >>
> >> On Mon, 2008-04-28 at 15:27 +0100, Krystian Szczesny wrote:
> >>> Hi Michele,
> >>>
> >>> I am trying to disable Chunking, so
> >>> chunked
> >>> won't help. I've been googling for other values of Transfer-
> Encoding
> >>> parameter but found none. From HTTP 1.1 specs I can see that this
> >>> parameter is for chunking only.
> >>
> >> Indeed by commenting out that line chunking should be disabled.
> > [Krystian Szczesny]  But client receives chunked response, so it's
> not
> > it
> >
> >>>
> >>> Where can I set
> >>> options.setProperty(HTTPConstants.CHUNKED, Boolean.FALSE);
> >>> ?
> >>>
> >>> I've looked through my auto generated stubs and there are no
> options
> >>> there.
> >>
> >> Should be something similar to:
> >> stub.getOptions().setProperty(...)
> > [Krystian Szczesny]  No there's nothing like that. My methods are
> > called
> > with xml message as a parameter (OMElement).
> 
> So you're using a ServiceClient object. Dind't you say you're not
> using it?
> 
> options.setProperty(...);
> sender.setOptions(options);
> 
> 
> >
> >>
> >>> Correct me if I'm wrong but isn't this for client only?
> >>
> >> Yes, it is.
> >> http://wso2.org/library/209
> >> http://wso2.org/library/230
> >>
> >>> Like I've said earlier, I can't change client code.
> >>
> >> Try to check this out
> >> http://www.mail-archive.com/axis-user@ws.apache.org/msg17471.html
> >>
> >> Finally, as last options, you can try this:
> >> - Let your service implement the Lifecycle interface
> >> - inside the init(ServiceContext context) method:
> >>
> >>
> > context.getConfigurationContext.setProperty
> > (HTTPConstants.CHUNKED,Boole
> >> an.FALSE);
> >>
> > [Krystian Szczesny]  Sorry Michele, but are you serious about that?
> It
> > looks a little bit like guessing... I am going to try it, but am
very
> > sceptical...
> 
> 
> I've used the Lifecycle interface, I've customized the configuration
> context, but I've never tried to enable/disable the chunking at
> runtime.
> 
> 
> Michele
> 
> >
> > Thanks anyway
> >
> >>
> >> Michele
> >>
> >>
> >>
> >>>
> >>> Best regards,
> >>> Krystian
> >>>
>  -Original Message-
>  From: Michele Mazzucco [mailto:[EMAIL PROTECTED]
>  Sent: 28 April 2008 15:07
>  To: axis-user@ws.apache.org
>  Subject: Re: Axis + Jetty disable chunking
> 
>  There's another parameter you can set:
> 
>  chunked
> 
>  You can also enable/disable it at runtime:
>  options.setProperty(HTTPConstants.CHUNKED, Boolean.FALSE);
> 
>  Michele
> 
> 
>  On 28 Apr 2008, at 12:14, Krystian Szczesny wrote:
> 
> > Hi,
> >
> > I've got an Axis2 1.3 deployed on Jetty 6.1.5.
> > I'm having some performance issues with this setup: response is
> > chunked and time between the chunks is about 60-70ms[!!!].
> > I wanted to disable the chunking so I've set my axis2.xml file
> > to
> > look like this:
> >
> >  >
> >
> >> class="org.apache.axis2.transport.http.CommonsHTTPTransportSender">
> >  >>> locked="true">HTTP/1.0
> > 
> >
> >  >
> >
> >> class="org.apache.axis2.transport.http.CommonsHTTPTransportSender">
> >  >>> locked="true">HTTP/1.0
> > 
> >
> > Unfortunately I am still receiving HTTP/1.1 chunked responses.
> >
> > Have you got any idea about what to set to disable chunking?
> > I am not using Axis2 client so forget about setting the options
> >> :/
> >
> > I spoke with folks from Jetty support mailing list and they've
> >> told
> > me, that Jetty will send chunked response if it doesn't know the
> > content length at the time of sending the message.
> >
> > If the settings I've pasted above were working, then I guess
> >> Jetty
> > would receive a full message so it should know the content
> >> length.
> >

Axis2 + HTTPS

2008-04-28 Thread SGruverman

We are providing Axis2(1.3) services using Tomcat (5.5).
I understand that Tomcat and Axis2 can both be configured to handle HTTPS.

Do I need to configure it in both or just one?
What are the advantages of having Tomcat handle SSL rather than Axis2?

I've looked for an article that covers this but haven't found one - any
references to something would be great.

Thanks very much!

- Steve

__
Steve Gruverman
IntelliCare, Inc. | A Medco Health Solutions Company

500 Southborough Drive | South Portland ME 04106






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

Re: Axis + Jetty disable chunking

2008-04-28 Thread Michele Mazzucco



On 28 Apr 2008, at 16:46, Krystian Szczesny wrote:


Thanks,
Krystian


-Original Message-
From: Michele Mazzucco [mailto:[EMAIL PROTECTED]
Sent: 28 April 2008 15:43
To: axis-user@ws.apache.org
Subject: RE: Axis + Jetty disable chunking

On Mon, 2008-04-28 at 15:27 +0100, Krystian Szczesny wrote:

Hi Michele,

I am trying to disable Chunking, so
chunked
won't help. I've been googling for other values of Transfer-Encoding
parameter but found none. From HTTP 1.1 specs I can see that this
parameter is for chunking only.


Indeed by commenting out that line chunking should be disabled.

[Krystian Szczesny]  But client receives chunked response, so it's not
it



Where can I set
options.setProperty(HTTPConstants.CHUNKED, Boolean.FALSE);
?

I've looked through my auto generated stubs and there are no options
there.


Should be something similar to:
stub.getOptions().setProperty(...)
[Krystian Szczesny]  No there's nothing like that. My methods are  
called

with xml message as a parameter (OMElement).


So you're using a ServiceClient object. Dind't you say you're not  
using it?


options.setProperty(...);
sender.setOptions(options);







Correct me if I'm wrong but isn't this for client only?


Yes, it is.
http://wso2.org/library/209
http://wso2.org/library/230


Like I've said earlier, I can't change client code.


Try to check this out
http://www.mail-archive.com/axis-user@ws.apache.org/msg17471.html

Finally, as last options, you can try this:
- Let your service implement the Lifecycle interface
- inside the init(ServiceContext context) method:


context.getConfigurationContext.setProperty 
(HTTPConstants.CHUNKED,Boole

an.FALSE);


[Krystian Szczesny]  Sorry Michele, but are you serious about that? It
looks a little bit like guessing... I am going to try it, but am very
sceptical...



I've used the Lifecycle interface, I've customized the configuration  
context, but I've never tried to enable/disable the chunking at runtime.



Michele



Thanks anyway



Michele





Best regards,
Krystian


-Original Message-
From: Michele Mazzucco [mailto:[EMAIL PROTECTED]
Sent: 28 April 2008 15:07
To: axis-user@ws.apache.org
Subject: Re: Axis + Jetty disable chunking

There's another parameter you can set:

chunked

You can also enable/disable it at runtime:
options.setProperty(HTTPConstants.CHUNKED, Boolean.FALSE);

Michele


On 28 Apr 2008, at 12:14, Krystian Szczesny wrote:


Hi,

I've got an Axis2 1.3 deployed on Jetty 6.1.5.
I'm having some performance issues with this setup: response is
chunked and time between the chunks is about 60-70ms[!!!].
I wanted to disable the chunking so I've set my axis2.xml file

to

look like this:


class="org.apache.axis2.transport.http.CommonsHTTPTransportSender">


locked="true">HTTP/1.0




class="org.apache.axis2.transport.http.CommonsHTTPTransportSender">


locked="true">HTTP/1.0



Unfortunately I am still receiving HTTP/1.1 chunked responses.

Have you got any idea about what to set to disable chunking?
I am not using Axis2 client so forget about setting the options

:/


I spoke with folks from Jetty support mailing list and they've

told

me, that Jetty will send chunked response if it doesn't know the
content length at the time of sending the message.

If the settings I've pasted above were working, then I guess

Jetty

would receive a full message so it should know the content

length.


Am I missing something here?

Best regards,
Krystian

P.s.
Sorry for the crap below, I can't disable it for external

messages


--
Krystian Szczesny
This e-mail and any attachments are confidential and may also be
legally
privileged and/or copyright material of Intec Telecom Systems

PLC

(or its
affiliated companies). If you are not an intended or authorised
recipient
of this e-mail or have received it in error, please delete it
immediately
and notify the sender by e-mail. In such a case, reading,

reproducing,

printing or further dissemination of this e-mail or its contents

is

strictly
prohibited and may be unlawful.
Intec Telecom Systems PLC does not represent or warrant that an
attachment
hereto is free from computer viruses or other defects. The

opinions

expressed in this e-mail and any attachments may be those of the
author and
are not necessarily those of Intec Telecom Systems PLC.





---

--

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

Re: NullPointerException when invoking Axis

2008-04-28 Thread SDev


Hi Anne,

Thanks for your quick response. :) I tried with Axis 1.4 but with no luck.
There seems to be some problem with the deserialising but it would be good
to know what element it referes to or some more detailed information.

Best wishes
Kerstin


Anne Thomas Manes wrote:
> 
> You must upgrade to at least Axis 1.3 (1.4 is preferable) if you want
> to use "wrapped" style.
> 
> Anne
> 
> On Fri, Apr 25, 2008 at 11:08 AM, SDev <[EMAIL PROTECTED]> wrote:
>>
>>  Hi,
>>
>>  I'm using Axis 1.2.1. I've auto generated a web service which created a
>> wsdl
>>  that was clattered with references to
>>  http://schemas.xmlsoap.org/soap/encoding/. Since
>>  http://schemas.xmlsoap.org/soap/encoding/ is not supported by WS-I I
>> changed
>>  in the wsdd from:
>>
>>  
>>
>>  to
>>
>>  >  use="literal">
>>
>>  This created the wsdl below without this namespace:
>>
>>  
>>  >  targetNamespace="http://se/rsv/at/art/arendelager/AtAlArendeLagerWS";
>>  xmlns:apachesoap="http://xml.apache.org/xml-soap";
>>  xmlns:impl="http://se/rsv/at/art/arendelager/AtAlArendeLagerWS";
>>  xmlns:intf="http://se/rsv/at/art/arendelager/AtAlArendeLagerWS";
>>  xmlns:tns1="http://arendelager.art.at.rsv.se";
>>  xmlns:tns2="http://base.er.rsv.se";
>>  xmlns:tns3="http://akthanterare.akt.at.rsv.se";
>>  xmlns:tns4="http://arendeplan.art.at.rsv.se";
>>  xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
>>  xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/";
>>  xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
>>  
>>   
>>   >  targetNamespace="http://arendelager.art.at.rsv.se";
>>  xmlns="http://www.w3.org/2001/XMLSchema";>
>>http://akthanterare.akt.at.rsv.se"/>
>>http://base.er.rsv.se"/>
>>http://xml.apache.org/xml-soap"/>
>>> namespace="http://se/rsv/at/art/arendelager/AtAlArendeLagerWS"/>
>>http://arendeplan.art.at.rsv.se"/>
>>
>> 
>>  
>>   
>>  
>> 
>>
>>
>> 
>>  
>>   
>>  
>> 
>>
>>
>> 
>>  
>>   
>>  
>> 
>>
>>
>> 
>>  
>>   
>>>  type="xsd:string"/>
>>   
>>  
>> 
>>
>>
>> 
>>  
>>   
>>> type="impl:AtAlArendeId"/>
>>   
>>  
>> 
>>
>>
>> 
>>
>>   
>>   >  targetNamespace="http://base.er.rsv.se";
>>  xmlns="http://www.w3.org/2001/XMLSchema";>
>>http://akthanterare.akt.at.rsv.se"/>
>>http://xml.apache.org/xml-soap"/>
>>> namespace="http://se/rsv/at/art/arendelager/AtAlArendeLagerWS"/>
>>http://arendelager.art.at.rsv.se"/>
>>http://arendeplan.art.at.rsv.se"/>
>>
>> 
>>  
>>  
>>  
>>  
>>  
>>  
>>  
>>  
>>  
>> 
>>
>>
>> 
>>  
>>  >  type="tns2:ErMessageHeader"/>
>>  
>> 
>>
>>   
>>   >  targetNamespace="http://akthanterare.akt.at.rsv.se";
>>  xmlns="http://www.w3.org/2001/XMLSchema";>
>>http://base.er.rsv.se"/>
>>http://xml.apache.org/xml-soap"/>
>>> namespace="http://se/rsv/at/art/arendelager/AtAlArendeLagerWS"/>
>>http://arendelager.art.at.rsv.se"/>
>>http://arendeplan.art.at.rsv.se"/>
>>
>> 
>>  
>>   
>>
>>   
>>  
>> 
>>
>>
>> 
>>  
>>   
>>  
>> 
>>
>>   
>>   >  targetNamespace="http://se/rsv/at/art/arendelager/AtAlArendeLagerWS";
>>  xmlns="http://www.w3.org/2001/XMLSchema";>
>>http://akthanterare.akt.at.rsv.se"/>
>>http://base.er.rsv.se"/>
>>http://xml.apache.org/xml-soap"/>
>>http://arendelager.art.at.rsv.se"/>
>>http://arendeplan.art.at.rsv.se"/>
>>
>> 
>>  
>>   
>>
>>
>>
>>   
>>  
>> 
>>
>>
>> 
>>  
>>   
>>>  type="tns1:AtAlArendeIntressentPK"/>
>>
>>   
>>  
>> 
>>
>>
>> 
>>  
>>   
>>  
>> 
>>
>>
>> 
>>  
>>   
>>  
>> 
>>
>>
>> 
>>  >  type="xsd:anyType"/>
>> 
>>
>>
>> 
>>  
>>   
>>
>>   
>>  
>> 
>>
>>
>> 
>>  
>>   
>>
>>
>>
>>
>>>  type="tns1:AtAlArendeIngivare"/>
>>>  type="impl:ArrayOf_xsd_anyType"/>
>>>  type="impl:ArrayOf_xsd_anyType"/>
>>>  type="tns4:AtApArendeTypsId"/>
>>
>>
>>
>>
>>
>>>  type="impl:ArrayOf_xsd_anyType"/>
>>
>>
>>
>>
>>   
>>  
>> 
>>
>>
>> 
>>  
>>   
>>
>>   
>>  
>> 
>>
>>
>> 
>>  
>>   
>>  
>> 
>>
>>   
>>   >  targetNamespace="http://xml.apache.org/xml-soap";
>>  xmlns="http://www.w3.org/2001/XMLSchema";>
>>http://akthanterare.akt.at.rsv.se"/>
>>http://base.er.rsv.se"/>
>>> namespace="http://se/rsv/at/art/arendelager/AtAlArendeLagerWS"/>
>>http://arendelager.art.at.rsv.se"/>
>>http://arendeplan.art.at.rsv.se"/>

java.lang.NoSuchMethodError: javax.xml.namespace.QName

2008-04-28 Thread Rajesh, Peter (CLAIMS, WIP)

Hi, 

In the java client, to invoke an Axis2 webservice, when we try to create
the ConfigurationContext as below, 

ConfigurationContext ctx =
ConfigurationContextFactory.createConfigurationContextFromFileSystem("C:
/Test/build/client_repository", null);

   
Below exception is thrown, 

java.lang.NoSuchMethodError:
javax.xml.namespace.QName.(Ljava/lang/String;Ljava/lang/String;Lja
va/lang/String;)V 

Please advice. 

Thanks & Regards, 

Peter Rajesh



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

RE: Axis + Jetty disable chunking

2008-04-28 Thread Krystian Szczesny

Thanks,
Krystian

> -Original Message-
> From: Michele Mazzucco [mailto:[EMAIL PROTECTED]
> Sent: 28 April 2008 15:43
> To: axis-user@ws.apache.org
> Subject: RE: Axis + Jetty disable chunking
> 
> On Mon, 2008-04-28 at 15:27 +0100, Krystian Szczesny wrote:
> > Hi Michele,
> >
> > I am trying to disable Chunking, so
> > chunked
> > won't help. I've been googling for other values of Transfer-Encoding
> > parameter but found none. From HTTP 1.1 specs I can see that this
> > parameter is for chunking only.
> 
> Indeed by commenting out that line chunking should be disabled.
[Krystian Szczesny]  But client receives chunked response, so it's not
it

> >
> > Where can I set
> > options.setProperty(HTTPConstants.CHUNKED, Boolean.FALSE);
> > ?
> >
> > I've looked through my auto generated stubs and there are no options
> > there.
> 
> Should be something similar to:
> stub.getOptions().setProperty(...)
[Krystian Szczesny]  No there's nothing like that. My methods are called
with xml message as a parameter (OMElement).

> 
> > Correct me if I'm wrong but isn't this for client only?
> 
> Yes, it is.
> http://wso2.org/library/209
> http://wso2.org/library/230
> 
> > Like I've said earlier, I can't change client code.
> 
> Try to check this out
> http://www.mail-archive.com/axis-user@ws.apache.org/msg17471.html
> 
> Finally, as last options, you can try this:
> - Let your service implement the Lifecycle interface
> - inside the init(ServiceContext context) method:
> 
>
context.getConfigurationContext.setProperty(HTTPConstants.CHUNKED,Boole
> an.FALSE);
> 
[Krystian Szczesny]  Sorry Michele, but are you serious about that? It
looks a little bit like guessing... I am going to try it, but am very
sceptical...

Thanks anyway

> 
> Michele
> 
> 
> 
> >
> > Best regards,
> > Krystian
> >
> > > -Original Message-
> > > From: Michele Mazzucco [mailto:[EMAIL PROTECTED]
> > > Sent: 28 April 2008 15:07
> > > To: axis-user@ws.apache.org
> > > Subject: Re: Axis + Jetty disable chunking
> > >
> > > There's another parameter you can set:
> > >
> > > chunked
> > >
> > > You can also enable/disable it at runtime:
> > > options.setProperty(HTTPConstants.CHUNKED, Boolean.FALSE);
> > >
> > > Michele
> > >
> > >
> > > On 28 Apr 2008, at 12:14, Krystian Szczesny wrote:
> > >
> > > > Hi,
> > > >
> > > > I've got an Axis2 1.3 deployed on Jetty 6.1.5.
> > > > I'm having some performance issues with this setup: response is
> > > > chunked and time between the chunks is about 60-70ms[!!!].
> > > > I wanted to disable the chunking so I've set my axis2.xml file
to
> > > > look like this:
> > > >
> > > >  > > >
> > > >
> class="org.apache.axis2.transport.http.CommonsHTTPTransportSender">
> > > >  > locked="true">HTTP/1.0
> > > > 
> > > >
> > > >  > > >
> > > >
> class="org.apache.axis2.transport.http.CommonsHTTPTransportSender">
> > > >  > locked="true">HTTP/1.0
> > > > 
> > > >
> > > > Unfortunately I am still receiving HTTP/1.1 chunked responses.
> > > >
> > > > Have you got any idea about what to set to disable chunking?
> > > > I am not using Axis2 client so forget about setting the options
> :/
> > > >
> > > > I spoke with folks from Jetty support mailing list and they've
> told
> > > > me, that Jetty will send chunked response if it doesn't know the
> > > > content length at the time of sending the message.
> > > >
> > > > If the settings I've pasted above were working, then I guess
> Jetty
> > > > would receive a full message so it should know the content
> length.
> > > >
> > > > Am I missing something here?
> > > >
> > > > Best regards,
> > > > Krystian
> > > >
> > > > P.s.
> > > > Sorry for the crap below, I can't disable it for external
> messages
> > > >
> > > > --
> > > > Krystian Szczesny
> > > > This e-mail and any attachments are confidential and may also be
> > > > legally
> > > > privileged and/or copyright material of Intec Telecom Systems
PLC
> > > > (or its
> > > > affiliated companies). If you are not an intended or authorised
> > > > recipient
> > > > of this e-mail or have received it in error, please delete it
> > > > immediately
> > > > and notify the sender by e-mail. In such a case, reading,
> > > reproducing,
> > > > printing or further dissemination of this e-mail or its contents
> is
> > > > strictly
> > > > prohibited and may be unlawful.
> > > > Intec Telecom Systems PLC does not represent or warrant that an
> > > > attachment
> > > > hereto is free from computer viruses or other defects. The
> opinions
> > > > expressed in this e-mail and any attachments may be those of the
> > > > author and
> > > > are not necessarily those of Intec Telecom Systems PLC.
> > >
> > >
> > >
---
> --
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> >
-
> > To unsubscribe, e-mail: [EMAIL PROT

Re: Axis2 cluster not working on Amazon EC2

2008-04-28 Thread Jeff Tomas

Azeez:
When will this be available in Axis2? Any time soon?

Jeff

On Wed, Apr 23, 2008 at 6:50 PM, Afkham Azeez <[EMAIL PROTECTED]> wrote:

> Hi Jeff,
> Axis2 clustering does not work on EC2 at the moment. This is because the
> Group Membership Protocol (GMP) uses multicast based member discovery.
> However, when you start two nodes on EC2, generally, the IP is randomly
> assigned by Amazon from a list of available IPs, unless you use elastic IPs.
> Even if elastic IPs are used, you cannot request for a specific IP address,
> hence it is difficult to get the two IPs such that they belong to the same
> multicast domain. Anyway, Amazon disallows multicasting at the moment.
>
> We are investigating whether we can use some other mechanism for group
> membership management.
>
> HTH
> Azeez
>
>
> On Sun, Apr 20, 2008 at 2:52 PM, Jeff Tomas <[EMAIL PROTECTED]>
> wrote:
>
> > We are planning to use Axis2 for a deployment on Amazon EC2. I have
> > created an AMI containing an Axis2 instance which is configured for
> > clustering. I have specified a group name. I started two instances of this
> > AMI, and on this AMIs I started an Axis2 instance each. However, I found
> > that these Axis2 nodes cannot communicate with each other. I have enabled
> > the cluster section in my axis2.xml file. Is there any other configuration
> > that needs to be set to enable clustering? Any help is highly appreciated.
> >
> > Thanks in advance
> > Jeff
> >
>
>
>
> --
> Thanks
> Afkham Azeez
>
> http://azeez78.blogspot.com
> http://www.wso2.org
> GPG Fingerprint: 643F C2AF EB78 F886 40C9 B2A2 4AE2 C887 665E 0760

OptimizedMimeSerialization

2008-04-28 Thread superrafcio

Hi,

I'am using version 1.3 of Axix 2 project with addressing (1.3), rahas (1.3), 
rampart (1.3) and sandesha2 (1.3) modules. I've generated client class using 
WSDL which was generated based on web service working under MS WCF. When 
application starts it notifies me that:

[DEBUG] can't find any module to process 
{http://schemas.xmlsoap.org/ws/2004/09/policy/optimizedmimeserialization}OptimizedMimeSerialization
 type assertions
[DEBUG] can't find any module to process 
{http://www.w3.org/2006/05/addressing/wsdl}UsingAddressing type assertions

what is wrong? I'm unable to connect to the existing WS (described by this WSDL)

Rafal

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

RE: Axis + Jetty disable chunking

2008-04-28 Thread Michele Mazzucco

On Mon, 2008-04-28 at 15:27 +0100, Krystian Szczesny wrote:
> Hi Michele,
> 
> I am trying to disable Chunking, so 
> chunked
> won't help. I've been googling for other values of Transfer-Encoding
> parameter but found none. From HTTP 1.1 specs I can see that this
> parameter is for chunking only.

Indeed by commenting out that line chunking should be disabled.
> 
> Where can I set 
> options.setProperty(HTTPConstants.CHUNKED, Boolean.FALSE);
> ?
> 
> I've looked through my auto generated stubs and there are no options
> there. 

Should be something similar to:
stub.getOptions().setProperty(...)

> Correct me if I'm wrong but isn't this for client only?

Yes, it is.
http://wso2.org/library/209
http://wso2.org/library/230

> Like I've said earlier, I can't change client code.

Try to check this out
http://www.mail-archive.com/axis-user@ws.apache.org/msg17471.html

Finally, as last options, you can try this:
- Let your service implement the Lifecycle interface
- inside the init(ServiceContext context) method:

context.getConfigurationContext.setProperty(HTTPConstants.CHUNKED,Boolean.FALSE);


Michele



> 
> Best regards,
> Krystian
> 
> > -Original Message-
> > From: Michele Mazzucco [mailto:[EMAIL PROTECTED]
> > Sent: 28 April 2008 15:07
> > To: axis-user@ws.apache.org
> > Subject: Re: Axis + Jetty disable chunking
> > 
> > There's another parameter you can set:
> > 
> > chunked
> > 
> > You can also enable/disable it at runtime:
> > options.setProperty(HTTPConstants.CHUNKED, Boolean.FALSE);
> > 
> > Michele
> > 
> > 
> > On 28 Apr 2008, at 12:14, Krystian Szczesny wrote:
> > 
> > > Hi,
> > >
> > > I've got an Axis2 1.3 deployed on Jetty 6.1.5.
> > > I'm having some performance issues with this setup: response is
> > > chunked and time between the chunks is about 60-70ms[!!!].
> > > I wanted to disable the chunking so I've set my axis2.xml file to
> > > look like this:
> > >
> > >  > >
> > > class="org.apache.axis2.transport.http.CommonsHTTPTransportSender">
> > >  locked="true">HTTP/1.0
> > > 
> > >
> > >  > >
> > > class="org.apache.axis2.transport.http.CommonsHTTPTransportSender">
> > >  locked="true">HTTP/1.0
> > > 
> > >
> > > Unfortunately I am still receiving HTTP/1.1 chunked responses.
> > >
> > > Have you got any idea about what to set to disable chunking?
> > > I am not using Axis2 client so forget about setting the options :/
> > >
> > > I spoke with folks from Jetty support mailing list and they've told
> > > me, that Jetty will send chunked response if it doesn't know the
> > > content length at the time of sending the message.
> > >
> > > If the settings I've pasted above were working, then I guess Jetty
> > > would receive a full message so it should know the content length.
> > >
> > > Am I missing something here?
> > >
> > > Best regards,
> > > Krystian
> > >
> > > P.s.
> > > Sorry for the crap below, I can't disable it for external messages
> > >
> > > --
> > > Krystian Szczesny
> > > This e-mail and any attachments are confidential and may also be
> > > legally
> > > privileged and/or copyright material of Intec Telecom Systems PLC
> > > (or its
> > > affiliated companies). If you are not an intended or authorised
> > > recipient
> > > of this e-mail or have received it in error, please delete it
> > > immediately
> > > and notify the sender by e-mail. In such a case, reading,
> > reproducing,
> > > printing or further dissemination of this e-mail or its contents is
> > > strictly
> > > prohibited and may be unlawful.
> > > Intec Telecom Systems PLC does not represent or warrant that an
> > > attachment
> > > hereto is free from computer viruses or other defects. The opinions
> > > expressed in this e-mail and any attachments may be those of the
> > > author and
> > > are not necessarily those of Intec Telecom Systems PLC.
> > 
> > 
> > -
> > 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]

[SOLUTION] - Is it possible to use interop (JAVA<->Microsoft) with x.509 Token profile? Response -> YES!

2008-04-28 Thread José Ferreiro

Dear newsgroup list,

I would like to share with you that it is possible to achieve *interoperability
*with the following combination of software for the x.509 Token profile:

*Goal: *server side fully developped using java. The secured web service
must be accessed by java or microsoft secured clients using x.509 Token
profile .

*Server side*: axis 1.4, wss4j 1.5.3, java jdk1.6.0_05 (keytool), tomcat 4.1
(I used tomcat 4.1 bcse it is faster for the test purposes)
*Java client side*: axis 1.4, wss4j 1.5.3
*Microsoft client side*: dotnet framework 2.0 and Web Services Enhancements
3.0 (WSE 3.0)
*Operating System*: XP with SP2
*Development software*: Microsoft Visual Studio 2005 and Eclipse Europe.

*Conversion jks to pfx *(PKCS #12): Version of OpenSSL 0.9.8g 19 Oct 2007.
This step is necessary to interoperate with the microsoft keystore.

I posted a small blog with some snapshots from my test environment:
http://magnot.blogspot.com/2008/04/secure-web-services-interoperability.html

Hope this helps!

Jose Ferreiro

RE: Axis + Jetty disable chunking

2008-04-28 Thread Krystian Szczesny

Hi Michele,

I am trying to disable Chunking, so 
chunked
won't help. I've been googling for other values of Transfer-Encoding
parameter but found none. From HTTP 1.1 specs I can see that this
parameter is for chunking only.

Where can I set 
options.setProperty(HTTPConstants.CHUNKED, Boolean.FALSE);
?

I've looked through my auto generated stubs and there are no options
there. Correct me if I'm wrong but isn't this for client only?
Like I've said earlier, I can't change client code.

Best regards,
Krystian

> -Original Message-
> From: Michele Mazzucco [mailto:[EMAIL PROTECTED]
> Sent: 28 April 2008 15:07
> To: axis-user@ws.apache.org
> Subject: Re: Axis + Jetty disable chunking
> 
> There's another parameter you can set:
> 
> chunked
> 
> You can also enable/disable it at runtime:
> options.setProperty(HTTPConstants.CHUNKED, Boolean.FALSE);
> 
> Michele
> 
> 
> On 28 Apr 2008, at 12:14, Krystian Szczesny wrote:
> 
> > Hi,
> >
> > I've got an Axis2 1.3 deployed on Jetty 6.1.5.
> > I'm having some performance issues with this setup: response is
> > chunked and time between the chunks is about 60-70ms[!!!].
> > I wanted to disable the chunking so I've set my axis2.xml file to
> > look like this:
> >
> >  >
> > class="org.apache.axis2.transport.http.CommonsHTTPTransportSender">
> > HTTP/1.0
> > 
> >
> >  >
> > class="org.apache.axis2.transport.http.CommonsHTTPTransportSender">
> > HTTP/1.0
> > 
> >
> > Unfortunately I am still receiving HTTP/1.1 chunked responses.
> >
> > Have you got any idea about what to set to disable chunking?
> > I am not using Axis2 client so forget about setting the options :/
> >
> > I spoke with folks from Jetty support mailing list and they've told
> > me, that Jetty will send chunked response if it doesn't know the
> > content length at the time of sending the message.
> >
> > If the settings I've pasted above were working, then I guess Jetty
> > would receive a full message so it should know the content length.
> >
> > Am I missing something here?
> >
> > Best regards,
> > Krystian
> >
> > P.s.
> > Sorry for the crap below, I can't disable it for external messages
> >
> > --
> > Krystian Szczesny
> > This e-mail and any attachments are confidential and may also be
> > legally
> > privileged and/or copyright material of Intec Telecom Systems PLC
> > (or its
> > affiliated companies). If you are not an intended or authorised
> > recipient
> > of this e-mail or have received it in error, please delete it
> > immediately
> > and notify the sender by e-mail. In such a case, reading,
> reproducing,
> > printing or further dissemination of this e-mail or its contents is
> > strictly
> > prohibited and may be unlawful.
> > Intec Telecom Systems PLC does not represent or warrant that an
> > attachment
> > hereto is free from computer viruses or other defects. The opinions
> > expressed in this e-mail and any attachments may be those of the
> > author and
> > are not necessarily those of Intec Telecom Systems PLC.
> 
> 
> -
> 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]

Formatting request style

2008-04-28 Thread Erik Wheeler

Hello all:

I'm trying to use a web service, but getting errors because Axis is
formatting the request with a multiRef.

The request is going out on the wire as:


http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>

http://schemas.xmlsoap.org/soap/encoding/";
xmlns:ns1="http://tempuri.org/SatuitWebService/SatuitCRM_XML_API";>
user
password


http://schemas.xmlsoap.org/soap/encoding/";
xsi:type="xsd:int"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";>44548




This fails with:

System.Web.Services.Protocols.SoapException: Server was unable to read
request. ---> System.InvalidOperationException: There is an error in XML
document (1, 514). ---> System.FormatException: Input string was not in
a correct format.

However, when I format the request manually without the multiRef and
submit (on the command line with 'wget') it works. In other words, it
works when the "Ibuskey" value above is instead like this:

  44548


The WSDL is at:
https://www2.satuitcrm.com/dwight/satuitcrm_XML_api.asmx?WSDL



I'm assuming that this is an issue of service style. But shouldn't it
use the style attribute from the "GetBusiness" operation? It starts
with:

  
  http://tempuri.org/SatuitWebService/SatuitCRM_XML_API/GetBus
iness" style="document"/>


Here's my test code:

import org.apache.axis.client.Call;
import org.apache.axis.client.Service;
import javax.xml.rpc.ParameterMode;

public class TestClient {
  public static void main(String[] args) {
try {
String endpoint =
"https://www2.satuitcrm.com/dwight/satuitcrm_XML_api.asmx";;
String methodName = "GetBusiness";
String namespace =
"http://tempuri.org/SatuitWebService/SatuitCRM_XML_API";;

Service service = new Service();
Call call = (Call) service.createCall();

call.setTargetEndpointAddress(new
java.net.URL(endpoint));

call.setOperationName(new
javax.xml.namespace.QName(namespace, methodName));


call.setSOAPActionURI("http://tempuri.org/SatuitWebService/SatuitCRM_XML
_API/GetBusiness");

call.addParameter(new javax.xml.namespace.QName(namespace,
"strUID"), 
new
javax.xml.namespace.QName("http://www.w3.org/2001/XMLSchema";, "string"),
ParameterMode.IN);

call.addParameter(new javax.xml.namespace.QName(namespace,
"strPWD"), 
new
javax.xml.namespace.QName("http://www.w3.org/2001/XMLSchema";, "string"),
ParameterMode.IN);

call.addParameter(new javax.xml.namespace.QName(namespace,
"Ibuskey"), 
new
javax.xml.namespace.QName("http://www.w3.org/2001/XMLSchema";, "int"),
ParameterMode.IN);

call.setReturnType(new javax.xml.namespace.QName(namespace,
"GetBusinessResult"), java.lang.String.class);

System.out.println(call.toString());
String ret = (String) call.invoke(new Object[] { "user",
"password" , (new
Integer(44548)) });

System.out.println(ret);
} catch (Exception e) {
System.err.println(e.toString());
}
}
}


Thanks for any suggestions you may have.

Regards,

Erik Wheeler

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

Re: Axis + Jetty disable chunking

2008-04-28 Thread Michele Mazzucco


There's another parameter you can set:

chunked

You can also enable/disable it at runtime:
options.setProperty(HTTPConstants.CHUNKED, Boolean.FALSE);

Michele


On 28 Apr 2008, at 12:14, Krystian Szczesny wrote:


Hi,

I’ve got an Axis2 1.3 deployed on Jetty 6.1.5.
I’m having some performance issues with this setup: response is  
chunked and time between the chunks is about 60-70ms[!!!].
I wanted to disable the chunking so I’ve set my axis2.xml file to  
look like this:


  
class="org.apache.axis2.transport.http.CommonsHTTPTransportSender">

HTTP/1.0


  
class="org.apache.axis2.transport.http.CommonsHTTPTransportSender">

HTTP/1.0


Unfortunately I am still receiving HTTP/1.1 chunked responses.

Have you got any idea about what to set to disable chunking?
I am not using Axis2 client so forget about setting the options :/

I spoke with folks from Jetty support mailing list and they’ve told  
me, that Jetty will send chunked response if it doesn’t know the  
content length at the time of sending the message.


If the settings I’ve pasted above were working, then I guess Jetty  
would receive a full message so it should know the content length.


Am I missing something here?

Best regards,
Krystian

P.s.
Sorry for the crap below, I can’t disable it for external messages

--
Krystian Szczesny
This e-mail and any attachments are confidential and may also be  
legally
privileged and/or copyright material of Intec Telecom Systems PLC  
(or its
affiliated companies). If you are not an intended or authorised  
recipient
of this e-mail or have received it in error, please delete it  
immediately

and notify the sender by e-mail. In such a case, reading, reproducing,
printing or further dissemination of this e-mail or its contents is  
strictly

prohibited and may be unlawful.
Intec Telecom Systems PLC does not represent or warrant that an  
attachment

hereto is free from computer viruses or other defects. The opinions
expressed in this e-mail and any attachments may be those of the  
author and

are not necessarily those of Intec Telecom Systems PLC.



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

Axis + Jetty disable chunking

2008-04-28 Thread Krystian Szczesny

Hi,

 

I've got an Axis2 1.3 deployed on Jetty 6.1.5.

I'm having some performance issues with this setup: response is chunked
and time between the chunks is about 60-70ms[!!!].

I wanted to disable the chunking so I've set my axis2.xml file to look
like this:

 



HTTP/1.0



 



HTTP/1.0



 

Unfortunately I am still receiving HTTP/1.1 chunked responses.

 

Have you got any idea about what to set to disable chunking?

I am not using Axis2 client so forget about setting the options :/

 

I spoke with folks from Jetty support mailing list and they've told me,
that Jetty will send chunked response if it doesn't know the content
length at the time of sending the message.

 

If the settings I've pasted above were working, then I guess Jetty would
receive a full message so it should know the content length.

 

Am I missing something here?

 

Best regards,

Krystian

 

P.s.

Sorry for the crap below, I can't disable it for external messages

 

-- 

Krystian Szczesny
This e-mail and any attachments are confidential and may also be legally 
privileged and/or copyright material of Intec Telecom Systems PLC (or its 
affiliated companies).  If you are not an intended or authorised recipient 
of this e-mail or have received it in error, please delete it immediately 
and notify the sender by e-mail. In such a case, reading, reproducing, 
printing or further dissemination of this e-mail or its contents is strictly 
prohibited and may be unlawful. 
Intec Telecom Systems PLC does not represent or warrant that an attachment 
hereto is free from computer viruses or other defects. The opinions 
expressed in this e-mail and any attachments may be those of the author and 
are not necessarily those of Intec Telecom Systems PLC.

Errors when deploying a multi-port service using Transport Listener/Receiver.

2008-04-28 Thread Sanjay Vivek

Hi all,

I'm trying to deploy a multi-port webservice (i.e. deploy the same
service on 2 different ports) and thus far I've done the following:

1) add each and every separate port as transport listeners and transport
receivers in axis2.xml on the service side as shown below:


   8081


   8082





 HTTP/1.1
 chunked


 HTTP/1.1
 chunked



2) Add the transport tag to the services.xml as shown below:


httpbasic



httpwssec




However, I get the following exceptions when I try to deploy the
service. Any help or guidance on what I should be doing would be greatly
appreciated. Cheers. 

Regards
--
Sanjay Vivek

28-Apr-2008 11:14:34 org.apache.catalina.core.StandardWrapperValve
invoke
SEVERE: Allocate exception for servlet AxisServlet
java.io.CharConversionException: Invalid UTF-8 middle byte 0x3f (at char
#2840, byte #-1)
at
com.ctc.wstx.io.UTF8Reader.reportInvalidOther(UTF8Reader.java:310)
at com.ctc.wstx.io.UTF8Reader.read(UTF8Reader.java:208)
at com.ctc.wstx.io.ReaderSource.readInto(ReaderSource.java:84)
at
com.ctc.wstx.io.BranchingReaderSource.readInto(BranchingReaderSource.jav
a:57)
at
com.ctc.wstx.sr.StreamScanner.loadMore(StreamScanner.java:967)
at com.ctc.wstx.sr.StreamScanner.getNext(StreamScanner.java:738)
at
com.ctc.wstx.sr.BasicStreamReader.nextFromProlog(BasicStreamReader.java:
1995)
at
com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1069)
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:1
53)
at
org.apache.axiom.om.impl.llom.OMDocumentImpl.getOMDocumentElement(OMDocu
mentImpl.java:130)
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.getDocumentElement(StAXOM
Builder.java:359)
at org.apache.axis2.util.XMLUtils.toOM(XMLUtils.java:568)
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.WarBasedAxisConfigurator.(WarBasedAxis
Configurator.java:146)
at
org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServle
t.java:500)
at
org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:420)
at
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.jav
a:1161)
at
org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:8
06)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv
e.java:129)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv
e.java:175)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java
:128)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java
:102)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.
java:109)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:2
63)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:84
4)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(
Http11Protocol.java:584)
at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:595)
28-Apr-2008 11:14:40 org.apache.catalina.core.StandardWrapperValve
invoke
SEVERE: Allocate exception for servlet AxisServlet
java.io.CharConversionException: Invalid UTF-8 middle byte 0x3f (at char
#2840, byte #-1)
at
com.ctc.wstx.io.UTF8Reader.reportInvalidOther(UTF8Reader.java:310)
at com.ctc.wstx.io.UTF8Reader.read(UTF8Reader.java:208)
at com.ctc.wstx.io.ReaderSource.readInto(ReaderSource.java:84)
at
com.ctc.wstx.io.BranchingReaderSource.readInto(BranchingReaderSource.jav
a:57)
at
com.ctc.wstx.sr.StreamScanner.loadMore(StreamScanner.java:967)
at com.ctc.wstx.sr.StreamScanner.getNext(StreamScanner.java:738)
at
com.ctc.wstx.sr.BasicStreamReader.nextFromProlog(BasicStreamReader.java:
1995)
at
com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1069)
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:1
53)
at
org.apache.axiom.om.impl.llom.OMDocumentImpl.getOMDocumentElement(OMDocu
mentImpl.java:130)
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.getDocumentElement(StAXOM
Builder.java:359)
at org.apache.axis2.util.XMLUtils.toOM(XMLUtils.java:568)
at
org.apache.axis2.deployment.DescriptionBuilder.buildOM(DescriptionBuilde
r.java:96)
at
org.apache.axis2.deployment.

Re: Fwd: Axis2 ADB Binding - Compiling All Schema

2008-04-28 Thread lucky

Deepal,
Thanks for looking into my problem. It will not be possible to share all the
aar files and schema. Because of size as well as confidentiality issue :(.
However its crucial for me to have a  better deployment and change
management strategy then we have currently. We are soon going in production
and may encounter problems if we have any changes in schema in future.

If it doesn't sound redundent and you can spare some time, here is again my
problem -

- There are 12 .aar files one for each Web-Service.
- Some of the schemas used by these WSs are common(base.xsd, common.xsd) and
then there are XSDs related to each Web Service(WSDL). For A.wsdl -> A.xsd
etc..in some rare cases A.wsdl refers B.xsd also.A.xsd, B.xsd tc refer to
base.xsd, common.xsd.

- I am using ADB binding while doing WSDL2java. But I guess only referred
schema from that WSDL gets compiled to classes. So for each WSDL, when I do
wsdl2Java there is difference in generated classes. I want to compile all
the schema in one go and put that in lib as a jar. So that whenever schema
changes I can compile it and test all services. In current arrangement I
will need to do WSDL2java again to generate classes for changed schema.
- I also tried XSD2java but again it only generated the classes for schema
which is being referred by the schema on which I am doing xsd2java.

Is there any way I can compile all the schema using ADB binding,
irrespective of whether it is being referred to or not? I can then do
WSDL2java only to get skeleton and inline schema and keep already genrated
classes from external schema as a jar to be referrd to by all skeletons.

On Mon, Apr 28, 2008 at 10:57 AM, Deepal jayasinghe <[EMAIL PROTECTED]>
wrote:

>
>  Hi Deepal,
> > Can you/your team kindly provide your valuable suggestion on following.
> >
> Is there any possibility of looking at your service aar file , then I can
> give your better answer for that.
>
> > Also in one of your replies you mentioned that Axis2 book is soon to
> > come. How fr is that soon :)
> >
> Will take maximum of two months :)
>
> Thank you!
> Deepal
>
> > Thanks a lot
> >
> >
> > -- Forwarded message --
> > From: *searl* <[EMAIL PROTECTED] >
> > Date: Fri, Apr 25, 2008 at 1:32 AM
> > Subject: Re: Axis2 ADB Binding - Compiling All Schema
> > To: axis-user@ws.apache.org 
> >
> >
> > Hi,
> >
> > This is something that I've wanted also.
> >
> > leon
> >
> > On Thu, 24 Apr 2008 17:35:00 +0530, lucky <[EMAIL PROTECTED]  > [EMAIL PROTECTED]>> wrote:
> > > HI,
> > > I am encountering one issue regarding the deployment of my web
> > services.
> > I
> > > a
> > > have a number of WSDL files.Corresponding to each WSDL file I have an
> > XSD
> > > which has schemas directly used in that WSDL.
> > >
> > > So say for WSDl A.wsdl I have A.xsd.; B.wsdl , B.xsd and so on. these
> > > xsd's
> > > intern refer to Base.xsd and some other XSDs.
> > > So base.xsd and other Xsds are common among all Web-Services. In some
> > rare
> > > cases A.wsdl may also refer to B.xsd.
> > >
> > > Problem -
> > > For each WSDL2Java I get a set of classes from Schema which I bundle
> > with
> > > that Web-Service.
> > > I am not able to get the classses for complete schema in one go. I
> > tried
> > > XSD2Java as well but there if I do it for A.xsd, I get classes for all
> > > referred schema's but not B.xsd etc if they are not referred to from
> > > A.xsd.
> > >
> > > How can I compile the whole schema in one go, irrespective of whether
> > they
> > > refer to each other or not and use that as a library for all my
> > > Web-Services.I am using ADB binding.
> > >
> > > Is there something obvious in Axis2 that I am missing? If any one
> > knows
> > > the
> > > solution kindly assist.
> > >
> > > Thanks for your time.
> > --
> > Leon S. Searl, Software Research Engineer
> > Information and Telecommunication Technology Center, University of
> > Kansas
> > Nichols Hall, 2335 Irving Hill Road, Lawrence, KS 66045-7612
> > Ph: 785-864-7820 Fax: 785-864-0387
> > http://www.ittc.ku.edu
> >
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: Axis2 and wsdl- Exception thrown when client attempting connection to SimpleHTTPServer

2008-04-28 Thread Upul Godage

Hi,

In the conf/axis2.xml there is a parameter commented out. Change it to the
required path and try like this.
/

Upul

Re: question about CommonHTTPTransportSender

2008-04-28 Thread Upul Godage

Like the "http" transport sender, there is an "https" transport sender
defined in the axis2.xml. You may need to set the key stores.

Upul


On Mon, Apr 28, 2008 at 1:06 PM, mathieu fabre <[EMAIL PROTECTED]> wrote:

> Hi,
>
> I work on a webapp and i use Axis2 to expose my services.
>
> my webapp is managed by jetty (like tomcat but lightweight).
> Jetty listen on port 8443 with HTTPS (SSL) and on port 8080 with HTTP (no
> SSL)
> I wrote a little client which create a RPCServiceClient to send a request.
>
> Here a piece of code :
>
> //Create an empty configuration context
> config =
> ConfigurationContextFactory.createConfigurationContextFromFileSystem(null,
> null);
> // Create a transport out description
> TransportOutDescription transpOut = new
> TransportOutDescription(Constants.TRANSPORT_HTTP);
> transpOut.addParameter(new Parameter(HTTPConstants.PROTOCOL_VERSION,
> "HTTP/1.1"));
> //create the HTTP sender
> CommonsHTTPTransportSender sender = new CommonsHTTPTransportSender();
> //initialize the sender
> sender.init(config, transpOut);
> transpOut.setSender(sender);
> config.getAxisConfiguration().addTransportOut(transpOut);
> //create the RPCServiceClient
> RPCServiceClient serviceClient = new RPCServiceClient(config, null);
> Options options = serviceClient.getOptions();
> EndpointReference targetEPR = new EndpointReference(url);
> options.setTo(targetEPR);
> 
> run the request with invokeBlocking
> 
>
> with HTTP, it work correctly, but i don't know what to do in order to use
> HTTPS
> The server does not expect to authenticate the client for the moment.
> If i try to view the wsd of on of my services with mozilla, it's working
> (i accept the certificate)
> So i would like to do the same in the code
>
> Do you know what i must do ...?
>
> Thanks,
>
> Mat
>

Axis2 and wsdl- Exception thrown when client attempting connection to SimpleHTTPServer

2008-04-28 Thread svaens


Hi all,

I am trying at the moment to develop an Axis2 server, and test it with a
client.
The server is to provide a soap wsdl service, returning an object request.

I have generated server code and client code using axis2's wsdl2java tool,
and all seemed fine.
The server I created using this generated code seems to work, so far as i
can tell, as I can connect to it through a browser.
For example, using the browser I can connect to it via:
http://localhost:/services/PersonInfo
and it gives me a page showing 'Deployed Services', listing the operations
available.
but the funny thing is here that it seems to auto-direct me to another url:
http://localhost:/axis2/services/ which I have not specified.
For the server I am using the axis2 supplied SimpleHTTPServer. Here is the
complete code excluding the actual generated code:

public class EmbeddedAxis2Server {
public static void main(String[] args) throws Exception {
ConfigurationContext context = ConfigurationContextFactory.
createConfigurationContextFromFileSystem(null, null);
AxisService service =
   
AxisService.createService(caps.integration.rhos.dk.schema.astraiaservice._2008._04._15.PersonInfo.class.getName(),
context.getAxisConfiguration());
context.getAxisConfiguration().addService(service);
SimpleHTTPServer server = new SimpleHTTPServer(context, );
server.start();
}
}

I can even call the published operation using the browser, via the url:

http://localhost:/axis2/services/PersonInfo/getPersonInfo

and pass in arguments using the usual form variables syntax.

HOWEVER!! My problem is (and maybe it is related to the url redirect
strangeness I mentioned above, or maybe not), that my coded client is not
able to connect.

I generated the client stubs also using wsdl2java, and call the functions...
but I get this show stopping exception:

org.apache.axis2.AxisFault: The service cannot be found for the endpoint
reference (EPR) 127.0.0.1/services/PersonInfo
 
at
org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:486)
at
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:343)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:389)
at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211)
at
org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
at
caps.integration.rhos.dk.schema.astraiaservice._2008._04._15.PersonInfoStub.getPersonInfo(PersonInfoStub.java:142)
at com.astraia.axisclient.Client.getPersonInfo(Client.java:44)
at com.astraia.axisclient.Client.main(Client.java:23)


Here is the client code (excluding generated stub)

public static void getPersonInfo(){
try
{   
ConfigurationContext context =
ConfigurationContextFactory.createConfigurationContextFromFileSystem(null,
null);
PersonInfoStub stub =new PersonInfoStub(context);
 
GetPersonInfoIn req =new GetPersonInfoIn();
req.setCivilRegistrationIdentifier("CIV123");
req.setHospitalCode("HOS123");
req.setRequestId("123");
req.setUserName("sean");

GetPersonInfoOut res = stub.getPersonInfo(req);
System.out.println(res.toString());
 
} catch(Exception e){ e.printStackTrace();  
System.out.println("\n\n\n");  }
}


If anyone has any idea of what this problem is about, I would love to hear
about it!
Kind Regards,
svaens



-- 
View this message in context: 
http://www.nabble.com/Axis2-and-wsdl--Exception-thrown-when-client-attempting-connection-to-SimpleHTTPServer-tp16934147p16934147.html
Sent from the Axis - User mailing list archive at Nabble.com.


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

question about CommonHTTPTransportSender

2008-04-28 Thread mathieu fabre

Hi,

I work on a webapp and i use Axis2 to expose my services.

my webapp is managed by jetty (like tomcat but lightweight).
Jetty listen on port 8443 with HTTPS (SSL) and on port 8080 with HTTP (no
SSL)
I wrote a little client which create a RPCServiceClient to send a request.

Here a piece of code :

//Create an empty configuration context
config =
ConfigurationContextFactory.createConfigurationContextFromFileSystem(null,
null);
// Create a transport out description
TransportOutDescription transpOut = new
TransportOutDescription(Constants.TRANSPORT_HTTP);
transpOut.addParameter(new Parameter(HTTPConstants.PROTOCOL_VERSION,
"HTTP/1.1"));
//create the HTTP sender
CommonsHTTPTransportSender sender = new CommonsHTTPTransportSender();
//initialize the sender
sender.init(config, transpOut);
transpOut.setSender(sender);
config.getAxisConfiguration().addTransportOut(transpOut);
//create the RPCServiceClient
RPCServiceClient serviceClient = new RPCServiceClient(config, null);
Options options = serviceClient.getOptions();
EndpointReference targetEPR = new EndpointReference(url);
options.setTo(targetEPR);

run the request with invokeBlocking


with HTTP, it work correctly, but i don't know what to do in order to use
HTTPS
The server does not expect to authenticate the client for the moment.
If i try to view the wsd of on of my services with mozilla, it's working (i
accept the certificate)
So i would like to do the same in the code

Do you know what i must do ...?

Thanks,

Mat

Re: The WS Crazy Train!

RE: org.apache.axis2.AxisFault: HTTP Transport error : '501' - 'Not Implemented' message

The WS Crazy Train!

xmlschema simpleContent for ADB

RE: java.lang.NoSuchMethodError: javax.xml.namespace.QName

Re: java.lang.NoSuchMethodError: javax.xml.namespace.QName

Obtaining the connecting client IP in a CallbackHandler invoked by Rampart

RE: Axis + Jetty disable chunking

Axis2 + HTTPS

Re: Axis + Jetty disable chunking

Re: NullPointerException when invoking Axis

java.lang.NoSuchMethodError: javax.xml.namespace.QName

RE: Axis + Jetty disable chunking

Re: Axis2 cluster not working on Amazon EC2

OptimizedMimeSerialization

RE: Axis + Jetty disable chunking

[SOLUTION] - Is it possible to use interop (JAVA<->Microsoft) with x.509 Token profile? Response -> YES!

RE: Axis + Jetty disable chunking

Formatting request style

Re: Axis + Jetty disable chunking

Axis + Jetty disable chunking

Errors when deploying a multi-port service using Transport Listener/Receiver.

Re: Fwd: Axis2 ADB Binding - Compiling All Schema

Re: Axis2 and wsdl- Exception thrown when client attempting connection to SimpleHTTPServer

Re: question about CommonHTTPTransportSender

Axis2 and wsdl- Exception thrown when client attempting connection to SimpleHTTPServer

question about CommonHTTPTransportSender

27 matches

Site Navigation

Mail list logo

Footer information