Hi,
Based on the documentation, it appears that xsd:dateTime is mapped to
java.util.Calendar. Why is that? Wouldn't java.util.Date make more sense?
Thanks
__
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.c
No. java.util.Date has been deprecated since JDK 1.1 - take a look at the
API.
Mark
-Original Message-
From: ow [mailto:[EMAIL PROTECTED]
Sent: Friday, May 30, 2003 10:03 AM
To: [EMAIL PROTECTED]
Subject: java.util.Calendar - Why?
Hi,
Based on the documentation, it appears that xsd:d
Looking at the 1.4.1_02 doc, Date is not deprecated. It does have a deprecated
constructor and some deprecated methods, but the class itself is not deprecated.
-Original Message-
From: Mark Galbreath [mailto:[EMAIL PROTECTED]
Sent: Friday, May 30, 2003 9:20 AM
To: [EMAIL PROTECTED]
Subje
--- Mark Galbreath <[EMAIL PROTECTED]> wrote:
> No. java.util.Date has been deprecated since JDK 1.1 - take a look at the
> API.
>
> Mark
That is certainly not true. Contrary to some people's beliefs, java.util.Date
is alive and well in the latest JDK ;-)
_
http://www.pankaj-k.net/WSOverSSL/WSOverSSL-HOWTO.html
> -Original Message-
> From: Skubal, Judy [mailto:[EMAIL PROTECTED]
> Sent: Friday, May 30, 2003 6:31 AM
> To: '[EMAIL PROTECTED]'
> Subject: SOAP over SSL
>
>
>
> Hi everyone,
>
> I have a very simple soap client that is currently
Thanks a bunch
-Judy
-Original Message-
From: KUMAR,PANKAJ (HP-Cupertino,ex1) [mailto:[EMAIL PROTECTED]
Sent: Friday, May 30, 2003 11:43 AM
To: '[EMAIL PROTECTED]'
Subject: RE: SOAP over SSL
http://www.pankaj-k.net/WSOverSSL/WSOverSSL-HOWTO.html
> -Original Message-
> From:
We do this because it is specified in the JAX-RPC 1.0 spec (See section 4.2.1)
Thanks,
dims
--- ow <[EMAIL PROTECTED]> wrote:
> --- Mark Galbreath <[EMAIL PROTECTED]> wrote:
> > No. java.util.Date has been deprecated since JDK 1.1 - take a look at the
> > API.
> >
> > Mark
>
> That is certainl
http://java.sun.com/xml/downloads/jaxrpc.html#jaxrpcspec1
--- Davanum Srinivas <[EMAIL PROTECTED]> wrote:
> We do this because it is specified in the JAX-RPC 1.0 spec (See section 4.2.1)
>
> Thanks,
> dims
>
> --- ow <[EMAIL PROTECTED]> wrote:
> > --- Mark Galbreath <[EMAIL PROTECTED]> wrote:
>
Title: where is the deployment informationn coming from when we run AdminClient with -l local list
Could anybody tell me where the deployment descriptor is stored when we deploy a wsdd file using
java org.apache.axis.client.AdminClient -llocal://
I don't see the local copy of server-conf
yeah, right. You have one constructor and 2 methods. Real useful, dude.
-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Friday, May 30, 2003 11:53 AM
To: [EMAIL PROTECTED]
Subject: RE: java.util.Calendar - Why?
http://java.sun.com/xml/downloads/jaxrpc.html#ja
bullshit
-Original Message-
From: ow [mailto:[EMAIL PROTECTED]
Sent: Friday, May 30, 2003 10:34 AM
To: [EMAIL PROTECTED]
Subject: RE: java.util.Calendar - Why?
--- Mark Galbreath <[EMAIL PROTECTED]> wrote:
> No. java.util.Date has been deprecated since JDK 1.1 - take a look at
> the A
Come on, guys! Why the issue - every constructor except the default is
deprecated; every method except toString() is deprecated. The JavaDoc tells
you to use Calendar instead. Are you that obtuse?
Mark
-Original Message-
From: Rudolph, Troy [mailto:[EMAIL PROTECTED]
Sent: Friday, May
Mark Galbreath wrote:
Come on, guys! Why the issue - every constructor except the default is
deprecated; every method except toString() is deprecated. The JavaDoc tells
you to use Calendar instead. Are you that obtuse?
setTime() and getTime() are also not deprecated. It appears that all
this
Mark,
Apache Axis implements JAX-RPC 1.0 Spec. We cannot release a version of Axis if we
don't pass the
TCK (http://www.jcp.org/en/resources/tdk) for JAX-RPC 1.0. The specification states
that
xsd:dataTime be mapped to java.util.Calendar. If you have a problem with the spec,
there is a
JAXRPC-I
- Original Message -
>
> Looks like it's time to break down and buy a copy of XML Spy! Its wsdl
> editor and schema valudation would've probably caught these things...
>
XML Spy can catch broken QNames, which was the primary problem with the
original WSDL. Omniopera can too (use its "Fin
When I try to connect to service with an https URL, I get this error:
java.lang.NoClassDefFoundError: COM/rsa/jsafe/y
at com.sun.net.ssl.internal.ssl.Handshaker.a([DashoPro-V1.2-120198])
at
com.sun.net.ssl.internal.ssl.ClientHandshaker.a([DashoPro-V1.2-120198])
at
com.sun.n
--- James Black <[EMAIL PROTECTED]> wrote:
> setTime() and getTime() are also not deprecated. It appears that all
> this should be used for is for these two methods, other than that Date
> is deprecated.
If you look more carefully you'll discover other non-deprecated methods. Date
is not depr
--- Davanum Srinivas <[EMAIL PROTECTED]> wrote:
>
> Apache Axis implements JAX-RPC 1.0 Spec. We cannot release a version of Axis
> if we don't pass the
> TCK (http://www.jcp.org/en/resources/tdk) for JAX-RPC 1.0. The specification
> states that
> xsd:dataTime be mapped to java.util.Calendar. If y
Anne,
this file is closely as possible to SAP generated ones.
- WSDLEditor from Cape Cleare reports 'Error: WSDL Text is invalid' with no
further indication where at was is wrong
- when running WSDL2Java i receive the error:
"java.io.IOException: Element RETURN is referenced but not defined. .
Hi Jim,
<<
It does seem to complicate the 'set up' of the call from the client side
when you use doc/literal. Doesn't the client have to manually construct
the
XML message to be passed to the server in the case of a doc/literal
service
call (when the xsd types required by the doc/literal service
Hi,
I am using Axis1.1RC2 on the client side. It seems
that the server isn't accepting the encoding for null-
Integers . It always
returns a NumberFormatExeption.
Using the BeanSerializer, is there any way to send
instead of
Integers . ???
thanks,
Simon
.
On Fri, 2003-05-30 at 13:58, ow wrote:
> --- Davanum Srinivas <[EMAIL PROTECTED]> wrote:
> >
> > Apache Axis implements JAX-RPC 1.0 Spec. We cannot release a version of Axis
> > if we don't pass the
> > TCK (http://www.jcp.org/en/resources/tdk) for JAX-RPC 1.0. The specification
> > states that
>
Reto,
It's a namespace qualification problem. (I used OmniOpera to find the
problem.)
You must provide namespace qualifiers for the elements referenced in the in
and out type definitions:
Anne
- Original Message -
From: "Reto Badertsche
Stu,
Thanks for the reply.
Someone on this forum mentioned that doc/literal web services actually scale
better than RPC/encoded services. Is this true? I dont see you could make
that generic of a statement given all of the implementations of web service
toolkits out there...
-Original Me
And those methods are reproduced in Calendar. Reading "Java in a Nutshell,"
2d addition 2 years ago, Flannigan pointed out that the Date class was
poorly conceived and worse implemented.
Mark
-Original Message-
From: James Black [mailto:[EMAIL PROTECTED]
Sent: Friday, May 30, 2003 1:00
The schema processor is complaining that the element RETURN in no namespace
is referenced but not defined. You have only defined tns:RETURN.
1. You should decide whether the elements in your schema's target namesapce
are qualified or not (must be mentioned by namespace prefix). Look up the
attr
I'm not sure I can do what I want to do and in frustration
am hoping someone on this list can help me.
I'm trying to use Axis as a client to a complex schema-defined
web service. I have samples of the messages I should be
sending, but I can't seem to get very close using the message
format in Axi
--- Jess Sightler <[EMAIL PROTECTED]> wrote:
> Ahem... I would complain had they not chosen to use Calendar.
> Calendar.getTime() makes conversion to a Date object easy, and Calendar
> is much more powerful. Date doesn't support TimeZones very well at all.
Why force people who do not need the p
I have no problem with the spec. But others seem to
-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Friday, May 30, 2003 1:03 PM
To: [EMAIL PROTECTED]
Subject: RE: java.util.Calendar - Why?
Mark,
Apache Axis implements JAX-RPC 1.0 Spec. We cannot release
I just posted a message today complaining that I seem
to have no control over the namespace prefixes. As
usual, no responses... maybe you'll have better luck.
-- Fred B.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Friday, May 30, 2003 2:38 PM
To: [EMAIL P
what do you mean? The ns prefixes are completely arbitrary and you have
total control.
Mark
-Original Message-
From: Barrett, Fred [mailto:[EMAIL PROTECTED]
Sent: Friday, May 30, 2003 2:43 PM
To: '[EMAIL PROTECTED]'
Cc: [EMAIL PROTECTED]; '[EMAIL PROTECTED]'
Subject: RE: Doc/literal new
Hi Justin,
Download the ClassLocator utility [1], and install it both in your Axis
webapp and in some other webapp where SSL is working correctly.
Go to the webapp where things are working, and surf to ClassLocator.jsp
and enter "COM.rsa.jsafe.y" see where the class is being loaded from.
Then go
No, unfortunately, even if you carefully set the prefixes,
when you return the Document they are ignored and replaced
by ns1, ns2, etc. (I'm using message style -- see my post
earlier today.) Apparently it's not just me, as Ken is
reporting the same problem.
I'm not saying there's not a way to d
I thought I could solve my own problem by reading in the
complete XML document from the file system, but it isn't
working. The error message I get is probably misleading,
so I could use some help. What am I doing wrong?
I kept trimming things out of the XML file till I got it down
to:
http://www
Try this for your soap envelope namespace:
xmlns:env="http://schemas.xmlsoap.org/soap/envelope";
-- Fred B.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Friday, May 30, 2003 3:42 PM
To: [EMAIL PROTECTED]
Subject: Problem reading from file
I thought
I currently have a SOAP rpc over Http web service using Axis
in Tomcat. The object (called Dispatcher) implementing the service
communicates with other back end processes.
There now needs to be a pure HTTP service (using GET with
query strings on the URL) which would ideally be handled b
36 matches
Mail list logo
