sample code: using java.util.Date instead of java.util.Calendar

2003-06-01 Thread Stu Halloway \(DevelopMentor\)
Hi, In response to "ow"s request for java.util.Date <-> xsd:dateTime conversion, I have written an Axis sample that uses a custom generator in WSDL2Java to bind dateTime to java.util.Date instead of java.util.Calendar. You can download the sample set at [1], the sample is called StaffLocator. Not

consuming doc literal

2003-06-01 Thread Marc E.
All, Until now, I've worked solely with RPC style web services using AXIS. Now, I need to consume several doc/literal web services. Does AXIS provide all of the tools I'll need to consume these, or should I look elsewhere, perhaps WSIF? And do I only need the WSDL for these services? Or do I need

Re: WSDL2Java

2003-06-01 Thread Reto Badertscher
Anne, thanks a lot for your help. After studying XMS schema and Cape Clears wsdleditor i managed to get java classes generated from Axis wsdl2Java. But one more questions arises: Why are my referenced elements generated with an underscore as a prefix e.g. --> generates _BANK_ADDRESS.java When

Re: Best practices question

2003-06-01 Thread Anne Thomas Manes
Many of the commercial Java implementations (WASP, GLUE, Cape Clear, XMLBus) autogenerate the schema, WSDL, and UDDI documents for you also. There's no reason why we can't do the same in Axis. Any volunteers? Anne - Original Message - From: "Mark Galbreath" <[EMAIL PROTECTED]> To: <[EMAIL

consuming doc literal

2003-06-01 Thread Marc E.
All, Until now, I've worked solely with RPC style web services using AXIS. Now, I need to consume several doc/literal web services. Does AXIS provide all of the tools I'll need to consume these, or should I look elsewhere, perhaps WSIF? And do I only need the WSDL for these services? Or do I need

RE: Best practices question

2003-06-01 Thread Mark Galbreath
What really needs to happen is the availability of tools that auto-generate the XML schema, WSDL, and UDDI documents so developers don't have to waste time learning and implementing a technology that does not return benefit relative to amount of effort. These documents are tedious to produce at be

RE: Best practices question

2003-06-01 Thread Ted Neward
The thing that many developers (IMHO) will find more complicated about doc/literal as opposed to an rpc/encoded scenario as its done today is that types must (for all intents and purposes) be specified in schema, rather than in Java (or C#, or whatever your "source" language is). That requires you