Re: Best Practice

Hi again Tony...   I can see this thread evolved since yesterday...fine discussion :-)   In this particular aspect, I prefer to work from Java. The way I see it, I'm developing some business functionality, that might be usable in many ways, not just as a web service. In developing the busine

Q. client side response flow handler

I have a question about client side response flow handlers. Is it possible for a client side response flow handler to add properties to the message context and have the client retrieve those properties? Seems basic, but it does not work for me. I have seen one other posting on the list about th

RE: Best Practice

You refactor without changing the interface/WSDL to your service?! A WSDL artifact published to external consumers is a contract of sort, it is not something easily changed after the fact. If you need to refactor either wait for WS-Versioning (not created yet but sure to come); or create a new W

Re: Best Practice

Be code centric as opposed to WSDL centric. With Axis we can expose our code in a relatively easy manner without the need of creating a WSDL first which is perfect. Anne Thomas Manes wrote: I'm thinking about reusability. Picture yourself a couple of years from now when your company has a few

Re: Best Practice

Yes, and with apologies for not including more helpful information first time around. [1] - http://ws.apache.org/ws-fx/wss4j/ Jim Murphy Mindreef, Inc. Vikas Phonsa wrote: Jim, Could u direct to some resources about WS Security that possibly have some examples related to Axis . I googled about se

RE: Best Practice

http://ws.apache.org/ws-fx/wss4j/ wss4j is Apache's stab at ws-security. It looks like a first run, but it doesn provide support for username tokens, encrypting/signing, etc. -Original Message- From: Vikas Phonsa [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 16, 2004 5:59 PM To: [EM

Re: Signal to noise ratio in Soap is very high

Can someone describe what the "slow part of web services is"? If you think its the verbosity of XML I suspect your not measuring it against alternatives. The fact is unless your message payload is very large the size of the XML body matters little in your overall performance - over broadband.

RE: Best Practice

Jim, Could u direct to some resources about WS Security that possibly have some examples related to Axis . I googled about security and authorization in web services but there is just too much information and it is kinda hard to select an approach to follow. Thanks -Original Message- Fro

RE: Best Practice

I'm thinking about reusability. Picture yourself a couple of years from now when your company has a few thousand services deployed. Like most companies you have about half dozen or so data structures that represent customer information. And now you want to find services that use a particular "cus

RE: Best Practice

I'm thinking about reusability. Picture yourself a couple of years from now when your company has a few thousand services deployed. Like most companies you have about half dozen or so data structures that represent customer information. And now you want to find services that use a particular "cus

Re: Best Practice

Joe Plautz wrote: Yes it was. It's something the carries application specific information as well as customer and user specific information. It's not great by any means, but it doesn't allow access either. But, by doing it this way, I've tried to keep the services as more of one time shots. Not

Issues using AdminClientTask in a Maven plugin

Hi, I am new to both axis and Maven, so if there is an easier route to do what follows, advice is very welcomed. I ran into some issues while adding a "deploy" goal to the sourceforge axis maven plugin from sourceforge (http://maven-plugins.sourceforge.net/) The main issue is that maven pass

Re: Best Practice

Anand Natrajan wrote: So what's my approach? Much as there is talk about writing WSDLs first, I prefer generating them automatically. I can do all the refactoring I want in my Java code and trust the java2wsdl generator to generate non-import WSDLs. So how do you keep you clients from breaking when

Re: HTTP sessions

This is a class that you can generate and handle a http session af a client: import org.apache.axis.MessageContext; import org.apache.axis.transport.http.HTTPConstants; import javax.servlet.http.HttpServletRequest; import javax.servlet.http.HttpSession; public class AxisPartnerInfo { p

HTTP sessions

Hi, Could anybody point towards a resource that teaches how to handle HTTP sessions in web services using Axis? Thanks Vikas

Re: Best Practice

Yes it was. It's something the carries application specific information as well as customer and user specific information. It's not great by any means, but it doesn't allow access either. But, by doing it this way, I've tried to keep the services as more of one time shots. Not as something that

RE: Best Practice

Hi Joe, Thanks for your answer. Could you elaborate a little bit about the authentication object? Was that part of the SOAP message? Thanks Vikas -Original Message- From: Joe Plautz [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 16, 2004 1:09 PM To: [EMAIL PROTECTED] Subject: Re: Bes

Re: Best Practice

I think at a minimum, you use https. For actual authorization, I've had to create a home brew of sorts because of the way we store use information. This forces clients to send an authentication object as part of the message. There seem to be much more elegant solutions involving headers and suc

Re: WSDL4J version bundled with Axis 1.2-beta3

Hmmm, not so clear to me, but I understand now... Apache Axis1.2 is using the latest CVS source versus an official release of WSDL4J. Thanks for you help. Davanum Srinivas

RE: Signal to noise ratio in Soap is very high

For the client side: http://www.osmoticweb.com/axis-soap-compression.htm also described in the previous link http://www.osmoticweb.com/soap-compression-howto.htm Christophe > -Original Message- > From: Vy Ho [mailto:[EMAIL PROTECTED] > Sent: Tuesday, November 16, 2004 3:29 PM > To: [EMAIL

Re: Signal to noise ratio in Soap is very high

I read an article about Fast Web Services... but I think there was no new development since then. http://java.sun.com/developer/technicalArticles/WebServices/fastWS/ > > Thank you for the responses. I think it's possible to achieve > interoperability and small foot print. It's just Soap was

Re: Signal to noise ratio in Soap is very high

Thank you for the link. Apache Tomcat already support server side gzip compression. I only need to do this on the client side. There's also free source code for doing the servlet that does the compression (very straight forward, because java already supply the gzip compression stream library

Re: Signal to noise ratio in Soap is very high

Thank you for the responses. I think it's possible to achieve interoperability and small foot print. It's just Soap was designed lousy in this particular aspect. When saying if speed matters, I think most of the apps that has some kind of communication, speed does matter. I think there shou

Re: WSDL4J version bundled with Axis 1.2-beta3

Hmmm, I thought the message was very clear...we made no changes...we picked up a cvs snapshot from their cvs and the diff was the diff from their 1.4 version till the day we picked up the sources. -- dims On Tue, 16 Nov 2004 13:03:03 -0700, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > Th

Re: WSDL4J version bundled with Axis 1.2-beta3

Thanks. Just for clarification, is this a fix that was made locally by Apache? If so, do you know if it was reported back to IBM? Davanum Srinivas

RE: Best Practice

I would appreciate if someone could comment on the security and authorization aspects of the web services. What is everybody using in that regard? Thanks Vikas -Original Message- From: Joe Plautz [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 16, 2004 10:59 AM To: [EMAIL PROTECTED]

Re: WSDL4J version bundled with Axis 1.2-beta3

see http://cvs.apache.org/viewcvs.cgi/ws-axis/java/lib/ On Tue, 16 Nov 2004 12:37:52 -0700, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > The wsdl4j.jar that has is bundled with Axis1.2-beta3 has a META-INF/ > MANIFEST.MF stating that it is WSDL4J v1.5. From where was this obtained? > IBM

WSDL4J version bundled with Axis 1.2-beta3

The wsdl4j.jar that has is bundled with Axis1.2-beta3 has a META-INF/ MANIFEST.MF stating that it is WSDL4J v1.5. From where was this obtained? IBM's site only lists version 1.4, and CVS makes no mention to a version 1.5. The manifest content is: Manifest-Version: 1.0 Ant-Version: Apache Ant

Re: Best Practice

The two-step process is actually necessary to delineate server-side stuff and client-side stuff. In fact, there are three broad steps really: 1. Generate WSDL from the classes - interface generation. 2. Generate WSDD and server-side skeletons from the WSDL - deployment description. 3. Generate c

Using keep alive to increase performance

I was looking for a way to increase performance, because it seems the server is topped off at around 100 request per seconds. Searching for information about keep alive seem not be so easy. But at the end, I get it to work by doing this: 1) Download the commons-httpclient at apache.org 2) Add

Re: Signal to noise ratio in Soap is very high

I second that... And would just add that you might want to think about when your application is just too 'chatty' for SOAP... -pc On Tue, 16 Nov 2004 08:48:30 -0900, Elaine Nance <[EMAIL PROTECTED]> wrote: > SOAP is not designed to create compact dataflows. It is designed > for interoperability

Re: Best Practice

I'll try and be more positive next time. I was trying to be impartial ;-) I do agree that the developer doesn't have to deal much with the WSDD. Using the ant axis tasks should be a best practice. It does automate a lot of stuff that doesn't need to be dealt with. I would actually go farther an

RE: Signal to noise ratio in Soap is very high

Check http://www.osmoticweb.com/soap-compression-howto.htm Christophe > -Original Message- > From: Vy Ho [mailto:[EMAIL PROTECTED] > Sent: Tuesday, November 16, 2004 12:11 PM > To: [EMAIL PROTECTED] > Subject: Re: Signal to noise ratio in Soap is very high > > > Searching around, I foun

Re: Best Practice

I agree with Joe's analysis overall, but I would be a bit more positive about approach #2. In this approach, you generate a Java class and use that you deploy your service. That's Joe's preferred approach and mine as well. However, the developer really doesn't have to diddle with WSDDs... or even

Re: Best Practice

Yeah, it's pretty sparse to find something that states that something is the best approach. Actually, there isn't anything, but I digress. There are a couple of choices and there isn't any advocacy in any particular direction. Which is probably best because you really can do almost anything you

RE: Best Practice

While I understand the attraction to factor out common definitions into a separate schema file, I am a bit conflicted about the use of schema files within a WSDL for describing a service. If your WSDL imports a schema, you can no longer hand out a single file to your customers and ask them to gene

Re: Best Practice

Hi, Due to a few issues generating the WSDL files from java code (in the area of custom exceptions mostly) I personal found the following approach suited me best. We already had the business class we wanted to expose as a web service so I originaly generated the WSDL from the java class. I the

Re: Signal to noise ratio in Soap is very high

SOAP is not designed to create compact dataflows. It is designed for interoperability and, because it is XML, extensibility. IMHO, I would *not* use SOAP for purely internal processes if speed or stream size matters (where faster/smaller) is better. In that case I would go strictly with a sock

Antwort: Re: Antwort: axis & new ws-addressing / ws-eventing

Hi Stefan You're right that WS-Addressing (W3C) is not yet supported but the spec 2004/03 before submission to W3C (ns "http://schemas.xmlsoap.org/ws/2004/03/addressing";) I'd suggest to use the earlier spec published by Microsoft, IBM and others instead of the one of W3C. The spec from W3C isn't

Re: Best Practice

Thanks, Joe. I've had a quick glance through the mailing list, back a year, but couldn't find anything obvious, in the best practice area. In this particular aspect, I prefer to work from Java. The way I see it, I'm developing some business functionality, that might be usable in many ways, not j

Re: Signal to noise ratio in Soap is very high

Searching around, I found this article: http://www-106.ibm.com/developerworks/webservices/library/ws-sqzsoap.html#code2 This basically add gzip to both end of the connection so that things gets smaller in the stream. The concept seems to be good. Is something Axis already implemented, so that I

Re: Signal to noise ratio in Soap is very high

What I meant is the signal to noise ratio is very low.

Re: Antwort: axis & new ws-addressing / ws-eventing

Hi oliver, Oliver Wulff wrote: Hi Stefan IBM does provide the Emerging Technologies Toolkit which implements WS-* (emerging specs). AFAIK, IBM is pushing WS-Notification (OASIS) more and WS-Eventing is pushed by Microsoft, TIBCO and BEA. Similar implementations are provided by Microsoft with Web S

Re: Best Practice

Funny you should ask this question. When I asked it about 6 months ago it spawned a week long thread that, in my opinion never reached a conclusion. But, this is what I gathered from it. There are three schools of thought when it comes to creating Axis web services. 1) Start with a WSDL and gene

Signal to noise ratio in Soap is very high

I look at a message send back from the server to a client in Axis, and was very surprised that most of the text is not the data that I need to send, but declaration and long namspaces. Is it possible to reduce these down and still comply with Soap? Thanks, vh

Re: Antwort: axis & new ws-addressing / ws-eventing

http://ws.apache.org/ws-fx/addressing/ On Tue, 16 Nov 2004 16:34:10 +0100, Oliver Wulff <[EMAIL PROTECTED]> wrote: > Hi Stefan > > IBM does provide the Emerging Technologies Toolkit which implements WS-* > (emerging specs). AFAIK, IBM is pushing WS-Notification (OASIS) more and > WS-Eventing is

Antwort: axis & new ws-addressing / ws-eventing

Hi Stefan IBM does provide the Emerging Technologies Toolkit which implements WS-* (emerging specs). AFAIK, IBM is pushing WS-Notification (OASIS) more and WS-Eventing is pushed by Microsoft, TIBCO and BEA. Similar implementations are provided by Microsoft with Web Service Enhancements (WSE). My

axis & new ws-addressing / ws-eventing

hi, i just wonder if someone of you has experience with WS-Addressing[1] / WS-Eventing[2] and Axis. Or do you know someone that has worked with it. Especially, using the provided WSDL files with this Specs and is there any experience with the new WS-Addressing EndpointReferences made? I'm writi

Re: Cannot run AdminClient

could you please show me, how you are doing that ? Which one that you would like me to show? How I run the Admin locally in the WEB-INF? Or the way I run the AdminClient? For the Admin, first I copy all class files for the webservice into the class folder inside WEB-INF. Next, copy the the d

Axis, SwA and Basic Profile 1.1

Hi, Does Axis 1.1 and its wsdl2java tool support SwA and/or attachement-related-stuff in Basic Profile 1.1 ? Regards, -R

Re: Does axis 1.2 comply with JDK 5.0 (1.5)

I got the thing to work now with regard to this enum problem. Thank you all. vh.

Re: Best Practice

Thanx for sharing this info.   It makes sence in respect of generation of proxies in the different IDEs/tools   /Henrik - Original Message - From: Anne Thomas Manes To: [EMAIL PROTECTED] Sent: Tuesday, November 16, 2004 3:17 PM Subject: RE: Best Practice T

RE: Best Practice

Technically, an “import” is importing a namespace, not the schema or WSDL file that creates the namespace. The WS-I Basic Profile says that you must not coerce (i.e., change) the namespace name during import: 5.1.9 Namespace Coercion Namespace coercion on wsdl:import is disallowed by the

RE: Best Practice

Technically, an “import” is importing a namespace, not the schema or WSDL file that creates the namespace. The WS-I Basic Profile says that you must not coerce (i.e., change) the namespace name during import: 5.1.9 Namespace Coercion Namespace coercion on wsdl:import is disallowed by the

Problem with SOAPElement

Hi,   i try to write an webservice, which gets two input-parameter, one String and one Datahandler. I put the String as an Element in the body an the Datahandler as an attachment to the message. But my Service says every time, that the String has no value.   Here is my code: Client: public

Re: Best Practice

Hi again Anne.   Nope. No need for these WSDL imports..I was mixing things up...posts are done on a pure "brain dump" basis..   - Original Message - From: Anne Thomas Manes To: [EMAIL PROTECTED] Sent: Tuesday, November 16, 2004 2:58 PM Subject: RE: Best Practice

RE: Best Practice

I was a little confused by your import structure – I wouldn’t expect to use at all. My suggestion is as follows:   Define standalone element schema (what you call type-schema).   Define standalone input/output message schema (what you call message-schema).  

RE: Best Practice

I was a little confused by your import structure – I wouldn’t expect to use at all. My suggestion is as follows:   Define standalone element schema (what you call type-schema).   Define standalone input/output message schema (what you call message-schema).  

Re: Best Practice

Hi Anne   Thanx for your fantastic reply/comments on this post. They really makes sence.   Actually I used your suggestions already (maybe without knowing it ??!) on a small-sized project where I only had one xsd file for all types. The whole "domain model" in one file.   BTW, do you know th

RE: Best Practice

Typically I prefer not to use a bunch of different schemas with a service (e.g., one schema for each element and type). In order to reference an element (or type) from one schema (a) in another schema (b), you must explicitly import the (a) schema (and define a namespace declaration) into t

RE: Best Practice

Typically I prefer not to use a bunch of different schemas with a service (e.g., one schema for each element and type). In order to reference an element (or type) from one schema (a) in another schema (b), you must explicitly import the (a) schema (and define a namespace declaration) into t

Re: Best Practice

Alright..I'll keep going :-)   You nearly answered your question yourself.   The different between 1) and 2) is that it is defined in two separate schemas (files). That way SOAPscope doesn't "throw up" (guess not, haven't tried it), because your are importing from a schema to a schema   You

Re: Best Practice

Thanks, Henrik. That's the sort of thing I'm after. I couldn't quite work out the difference between 1 and 2, though. In 1, you are defining the messages for the service methods and this naturally includes the parameters of the methods. In 2, it seems you're doing the same thing again (except for

handeling call timeout exception

Hi We are using synchronous client to invoke the server API. There is setTimeout method allows change socket timeout. We like to use this to enable cancel operation for invoked call. something like the following :         call.setTimeout( 1000 ); boolean shouldContin

Re: Best Practice

Hi Tony   I have a few...Some on this list might disagree, but it is always nice with a discussion.   I have done this, on several projects, and it works very well, especially for interop. The main point is: Use Schemas   1. Define a schema for each message you want your webservice to process

Re: Best Practice

Thanks, Nikki. We have a standard of complying to Basic Profile 1.0, for interoperability but, on top of that, I'm looking for generally accepted good ways of doing stuff during development of web services servers and clients. Beyond BP 1, are there useful ways to structure WSDL and type definiti

Re: Does axis 1.2 comply with JDK 5.0 (1.5)

- pick up the nightly On Tue, 16 Nov 2004 10:03:06 +0100, WAJSBERG Julien RD-BIZZ <[EMAIL PROTECTED]> wrote: > Vy Ho a écrit : > > > > > Also, unzip the axis.jar file, I do not see the package there either. > > It's only on the CVS trunk : > http://cvs.apache.org/viewcvs.cgi/ws-axis/java/src/

Re: Best Practice

Hi Tony Not sure what you're after in particular, For W3C's efforts in this area see links from http://www.w3.org/2002/ws/ For OASIS efforts see http://www.oasis-open.org/specs/index.php For Axis there is the userguide, this list & if you search the archives of this list for "books" you may find

Re: Best Practice

Does no one have, or have knowledge of, any best practice in the web service arena? I'm looking for a set of hints and tips, rather than a 800 page book. Tony Does anyone know of a published set of best practices, both for web services in general and Axis in particular? I've scoured the Net and

RE: does anyone have complex serialization working?

John, Read the "Array of Objects in Axis and .NET interop" thread. It sums it up quite well. In my postings there, I pointed out one of the causes this doesn't work in detail. So far there's no response by the developers, unfortunately. We found however, that it works using RPC/encoded (Thanks

Re: Cannot run AdminClient

Vy Ho wrote: This is really strange isn't it? Followed some instruction on the web, I was able to generate deployed information directly in the config file (run Admin in the WEB-INF). This method modify the config file directly, and not using the web interface. This works for the attachment

creating wsdl-file

Hi,   i just have a look on the examples on the ws.apache.org/axis-homepage and tryed to create an wsdl-file with axis for the service. To do so, i started the Axis-Servlet and clicked on the link corresponding to the EchoAttachmentsService. The answer of axis was:  WSDLException: faultCode=

http://xml.apache.org/xml-soap Namespace

Is there a XML Schema for the following namespace? http://xml.apache.org/xml-soap WSDL generated by Axis uses this namespache and I would like to take a look at it... thanks patric

Re: Does axis 1.2 comply with JDK 5.0 (1.5)

Vy Ho a écrit : Also, unzip the axis.jar file, I do not see the package there either. It's only on the CVS trunk : http://cvs.apache.org/viewcvs.cgi/ws-axis/java/src/org/apache/axis/constants/ You must either : - wait for the next Axis release - checkout the CVS version -- Julien

Re: web services security and authentication

Hi, Maybe your web service is using a SOAP binding over HTTP (that's true in most cases). If you know about HTTP, it supports some way of authentification (Basic, Digest...). Axis frontend is usually a servlet so you can configure your J2EE container (WebSphere in your case) to protect that res