java.lang.Date is most definitely not deprecated, only the constructors
from various date/time component values are deprecated. If you're
working with a Calendar instance you can call the getTime() method of
the Calendar to get the Date value corresponding to the current
date/time set on the Ca
Dennis,
Thanks for your detailed reply. It looks like,
java.lang.date is depricated. Do you have any other
suggestion or work around you can offer.
Thanks
--Ugo
--- Ugo Enyioha <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Is it possible to map the java.util.Calender class
> with JibX. I've been tryin
A Calendar unfortunately doesn't have an automatic representation in XML
terms. Many Java frameworks use Calendar instances to represent schema
dateTime types, but this is actually inaccurate - Calendar has a time
zone, which dateTime does not (it can be written out with an offset from
UTC, but
Hi,
Is it possible to map the java.util.Calender class
with JibX. I've been trying to to automatically create
a binding file using the binding tools, but I keep
getting errors with this type.
Appreciate the help.
Thanks.
__
Do You Yahoo!?
Tired
Looks like you got an empty request message. You might want to try
monitoring the communications to see exactly what's being sent between
the client and the server. I use TcpMon for this purpose (part of the
Apache Axis distribution), though there are many similar tools.
- Dennis
[EMAIL PROT
You might also check just what Java you're running, with "java
-version". Some distributions only supply the old open source JVM (name
escapes me) out of the box.
- Dennis
Mocky Habeeb wrote:
Sounds like a problem with BCEL. I'd double check your bcel.jar to make
sure that it is present in
Check the last paragraph of
http://jibx.sourceforge.net/tutorial/binding-collects.html#ids and the
linked http://jibx.sourceforge.net/extras.html#ididref I think that
gives you what you need.
- Dennis
Ross Bagley wrote:
I'm trying to map an object model to XML that happens to have multiple
Yes, this is a known problem with RC0 on Windows. It's been fixed in CVS
for some time, so if you can get the code from there and build you
should be fine.
Sorry for not updating the status page on this - I keep thinking I'll
have RC1 out any day, so it never quite seems worth the effort. I'll
Seems like it shouldn't be too hard. You'd need a Java object for the
condition, which has the comparison value and a reference to the
operator (which I assume is going to be optional, since otherwise you'd
always have an infinite tree). Then the binding would be something like
this:
