This email is to inform you about the release of version '2.2.5.2' of 'Java
Serialization to XML' through freshmeat.net. All URLs and other useful
information can be found at

     http://freshmeat.net/projects/jsx/

The changes in this release are as follows:
Minor bugfixes.

Release focus:
6 - Minor bugfixes

Project added:
Tue, Oct 10th 2000 01:06 (5 years, 11 months ago)

Project description:
Java Serialization to XML (JSX) translates between Java and XML,
making it possible to search, test, profile, and audit your object
data with ordinary XML and text processing tools. Your data can be
migrated to new application versions, to C++, and to other
applications by transforming the XML. Unlike other Java XML
serializers, JSX is accurate for all objects.

Trove categories:
[Development Status  ] 5 - Production/Stable
[Environment         ] Console (Text Based), MacOS X, Other Environment,
Web Environment, Win32 (MS Windows)
[Intended Audience   ] Developers
[License             ] OSI Approved :: GNU General Public License (GPL),
Other/Proprietary License with Free Trial
[Programming Language] Java
[Topic               ] Communications, Database, Software Development,
Software Development :: Libraries, Software Development :: Libraries ::
Java Libraries, Software Development :: Object Brokering, System ::
Archiving, System :: Recovery Tools, Text Processing :: Markup :: XML

If you would like to cancel subscription to releases of this project,
login to freshmeat.net and choose 'home' from the personal menubar at the
top of the page. You'll be presented with a list of projects and
categories you're subscribed to in the right column, which you may cancel
by highlighting the project or category in question and clicking the
'delete' button.

Sincerely,
freshmeat.net

Hi Damien,

             [ cc'ed the mailing list - please reply there. ]

Thanks a lot for that - I'll disable it in the next release, and get
the new version to you before then.

The reason for this warning is because JSX needs to rely
on private implementation details of the JVM (not public
methods), which the JVM supplier could change without
warning.

But perhaps this warning is not really needed? It's never
actually helped find a bug, and it annoys people.

If there is a bug with a new JVM version, it will be
reported as such. In fact, these aspects of the JVM change
only rarely (only 3 different versions for Sun's JVM, since Java 1.2),
and any problem will be immediately apparent. I like the idea
of safety, in warning people that there *could* be a problem -
but problems will be apparent, anyway; unless an insidious bug,
which is not easily detected, anyway. In other words - this
warning doesn't  help detect those problems, anyway.

To rectify this, I will remove this check on JVM versions altogether.

Is that OK with you (and everyone else)?


cheers,
Brendan

PS: jsx-ideas@yahoogroups.com
[ cc'ed the mailing list - please reply there. ]

----- Original Message -----
From: "Damien Evans" <devans@...>
To: "Brendan Macmillan" <Brendan.Macmillan@...>
Sent: Thursday, September 14, 2006 7:17 AM
Subject: JSX on IBM 1.5 JVM


> Hi Brendan,
>
>
>
> We're getting this again after updating our JDK on AIX systems:
>
>
>
> INFO   | jvm 1    | 2006/09/13 03:08:51 | ---ATTENTION!---  JSX could
> not recognize your
>
> implementation of java, which is:
>
> INFO   | jvm 1    | 2006/09/13 03:08:51 |       implVendor="IBM
> Corporation"
>
> INFO   | jvm 1    | 2006/09/13 03:08:51 |       specVersion="1.5"
>
> INFO   | jvm 1    | 2006/09/13 03:08:51 |       implVersion="1.5.0"
>
> INFO   | jvm 1    | 2006/09/13 03:08:51 | In the meantime, JSX2 will try
> the standard im
>
> plementation for Java 1.4 - which will probably work
>
> INFO   | jvm 1    | 2006/09/13 03:08:51 | Please post the above
> information to: jsx-idea
>
> s@yahoogroups.com
>
> INFO   | jvm 1    | 2006/09/13 03:08:51 |  - in particular, please state
> whether the sta
>
> ndard implementation worked or not, for both writing and reading.
> Please do a few tests
>
> before you post.
>
> INFO   | jvm 1    | 2006/09/13 03:08:51 |
>
> INFO   | jvm 1    | 2006/09/13 03:08:51 |       If JSX's guess really
> does work, it can
>
> be fixed with:
>
> INFO   | jvm 1    | 2006/09/13 03:08:51 |       if
> (implVendor.equals("IBM Corporation")
>
> && specVersion.equals("1.5") && implVersion.equals("1.5.0"))
>
> INFO   | jvm 1    | 2006/09/13 03:08:51 |       magicName =
> "JSX.magic.MagicClass14"
>
>
>
> Things work fine so you can go ahead and add support for this JVM (if
> you haven't already).
>
>
>
> -- Damien
>
>
>
> Damien Evans
>
> Lead Architect
>
> TeraMedica Healthcare Technology
>
> 10400 Innovation Dr,
>
> Suite 200
>
> Milwaukee, WI 53226
>
> + 1 414 908 7723 office
>
> + 1 414 839 3568 cell
>
> devans@... <mailto:devans@...>
>
>
>
>
>
>

That works for me.

BTW, were you ever able to implement support for BEA JRockit?

  -- Damien

> -----Original Message-----
> From: Brendan Macmillan
> Sent: Wednesday, September 13, 2006 10:01 PM
> To: Damien Evans
> Cc: JSX-ideas@yahoogroups.com
> Subject: Re: JSX on IBM 1.5 JVM
>
> Hi Damien,
>
>             [ cc'ed the mailing list - please reply there. ]
>
> Thanks a lot for that - I'll disable it in the next release, and get
> the new version to you before then.
>
> The reason for this warning is because JSX needs to rely
> on private implementation details of the JVM (not public
> methods), which the JVM supplier could change without
> warning.
>
> But perhaps this warning is not really needed? It's never
> actually helped find a bug, and it annoys people.
>
> If there is a bug with a new JVM version, it will be
> reported as such. In fact, these aspects of the JVM change
> only rarely (only 3 different versions for Sun's JVM, since Java 1.2),
> and any problem will be immediately apparent. I like the idea
> of safety, in warning people that there *could* be a problem -
> but problems will be apparent, anyway; unless an insidious bug,
> which is not easily detected, anyway. In other words - this
> warning doesn't  help detect those problems, anyway.
>
> To rectify this, I will remove this check on JVM versions altogether.
>
> Is that OK with you (and everyone else)?
>
>
> cheers,
> Brendan
>
> PS: jsx-ideas@yahoogroups.com
> [ cc'ed the mailing list - please reply there. ]
>
> ----- Original Message -----
> From: "Damien Evans"
> To: "Brendan Macmillan"
> Sent: Thursday, September 14, 2006 7:17 AM
> Subject: JSX on IBM 1.5 JVM
>
>
> > Hi Brendan,
> >
> > We're getting this again after updating our JDK on AIX systems:
> >
> > INFO   | jvm 1    | 2006/09/13 03:08:51 | ---ATTENTION!---  JSX could
> > not recognize your implementation of java, which is:
> >
> > INFO   | jvm 1    | 2006/09/13 03:08:51 |       implVendor="IBM
> > Corporation"
> >
> > INFO   | jvm 1    | 2006/09/13 03:08:51 |       specVersion="1.5"
> >
> > INFO   | jvm 1    | 2006/09/13 03:08:51 |       implVersion="1.5.0"
> >
> > INFO   | jvm 1    | 2006/09/13 03:08:51 | In the meantime, JSX2 will try
> > the standard implementation for Java 1.4 - which will probably work
> >
> > INFO   | jvm 1    | 2006/09/13 03:08:51 | Please post the above
> > information to: jsx-ideas@yahoogroups.com
> >
> > INFO   | jvm 1    | 2006/09/13 03:08:51 |  - in particular, please state
> > whether the standard implementation worked or not, for both writing and
reading.
> > Please do a few tests before you post.
> >
> > INFO   | jvm 1    | 2006/09/13 03:08:51 |
> >
> > INFO   | jvm 1    | 2006/09/13 03:08:51 |       If JSX's guess really
> > does work, it can be fixed with:
> >
> > INFO   | jvm 1    | 2006/09/13 03:08:51 |       if
> > (implVendor.equals("IBM Corporation")
> > && specVersion.equals("1.5") && implVersion.equals("1.5.0"))
> >
> > INFO   | jvm 1    | 2006/09/13 03:08:51 |       magicName =
> > "JSX.magic.MagicClass14"
> >
> > Things work fine so you can go ahead and add support for this JVM (if
> > you haven't already).
> >
> > -- Damien
> >

> That works for me.
Great.

> BTW, were you ever able to implement support for BEA JRockit?

No.

From memory, I got hold of the source, but they didn't leave any
accidental hooks to access their serialization internals. It's a testiment
to how well-written and secure it is.

Of course, I'd be very happy to be proven wrong.

I'm sure BEA would provide hooks for access, if enough of their customers
requested it...

     - Brendan

jsx.org is back!

The story:
As you may recall, our old domain name of "jsx.org" was taken by the
registrar when we were 10 days late to renew.

We then shifted to "javaserializationtoxml.com", but of course even
though we announced the change here, many users expected us at
"jsx.org", and so it seemed that we were gone.

A couple of days ago, we managed to reacquire "jsx.org", and today it
has been set to refer to our site again - there may be propagation
delays before it is visible everywhere.

We will keep the long name "javaserializationtoxml.com" as well as
"jsx.org", so as not to cause further confusion.

We are taking steps to ensue we are not late in renewing again!


cheers,
Brendan Macmillan

Hi, (forwarded to mailing list)

You can pass in a classloader as the second arg to ObjectReader (first arg can
be InputStream or Reader):
http://jsx.org/docs/JSX/ObjectReader.html#ObjectReader(java.io.InputStream,%20ja\
va.lang.ClassLoader)
http://jsx.org/docs/JSX/ObjectReader.html#ObjectReader(java.io.Reader,%20java.la\
ng.ClassLoader)

Or, you can use setContextClassLoader on the current thread:
    
http://java.sun.com/j2se/1.4.2/docs/api/java/lang/Thread.html#setContextClassLoa\
der(java.lang.ClassLoader)
eg:
     Thread.currentThread().setContextClassLoader(myCL);

There's some discussion in the mailing list archives:
    
http://tech.groups.yahoo.com/group/JSX-ideas/msearch?query=setcontextclassloader\
&submit=Search&charset=ISO-8859-1


cheers,
Brendan

> I have one problem I might be able to resolve by using the -D option of java
> to change the default system class loader...the problem is that Jtest when
> running unit tests uses its own class loader but because the sun class
> loader is the default it means JSX uses Sun's but Jtest uses its own which
> means the same class is loaded twice and I get a class cast exception when
> casting an object i read from an xml file and pass as input to a junit test
> case.
>
> Is there any way for me to tell JSX to use a particular class loader apart
> from the default class loader?

Lets say for example I have:

class foo1 {
    String a;
    String b;
}

and I have literally hundreds of different objects of class foo1
serialised to different XML files. Now I need to modify class foo1 to
include a new attribute so its class definition is now:

class foo1 {
    String a;
    String b;
    String c;
}

What tools/approaches can I use to modify all of my XML files to
include the new attribute 'c' with a certain value say 'newattrvalue'.
  I need this tool to be fairly powerful but easy to use because we are
in a commercial environment and can add/remove complex attributes from
existing classes that are not of simple types String, int, boolean, etc.

Thanks,
Stephen

Hi Stephen,

> What tools/approaches can I use to modify all of my XML files to
> include the new attribute 'c' with a certain value
> say 'newattrvalue'.

You can modify XML with XSLT; tho here you may be better off doing it
within the class.

Both are discussed in the JSX manual:
http://jsx.org/pdf/JSXmanual.pdf



XSLT
----
The JSX manual (see above, or link at top of www.jsx.org/support.html)
has examples of accessing the JSX XML format in terms of classes and
fields (pp.20-25).


Within the class
----------------
But for this case, I would suggest putting this evolution code within
the classes themselves - this is because that is where the evolution
occurred in the first place, and the person making the change will
know what value to use.

JSX uses the same hooks as JOS (Java Object Serialization - standard
part of java, in java.io.*) for this kind of evolution. It enables
your objects to look at the fields that are in the stream, and if
something is missing, to supply the correct value. (you could also do
this by testing for null, 0 or false, but then you can't distinguish
between the field being absent, or the field being present and
actually having that value).

This is discussed on page 10 of the JSX manual - but because it is the
same as JOS, there are also several tutorials about it.
"serialPersistentFields" is probably the best search term for this.


> I need this tool to be fairly powerful but easy to use because
> we are in a commercial environment and can add/remove
> complex attributes from existing classes that are not of
> simple types String, int, boolean, etc.

Adding complex types is probably simpler to do within the classes.
You can also do it with XSLT and XML: I'd suggest generating the XML
you need (by writing code to create the object you need, and then
serializing it), and then writing an XSLT script to insert it into the
XML for each object of that class.

Deleting is automatic, because when reading, JSX silently discards a
value if its field does not appear in the current version of the class
(same as JOS).


cheers,
Brendan

--- In JSX-ideas@yahoogroups.com, "Stephen Kurlow" <skurlow@...> wrote:
>
> Lets say for example I have:
>
> class foo1 {
>    String a;
>    String b;
> }
>
> and I have literally hundreds of different objects of class foo1
> serialised to different XML files. Now I need to modify class foo1 to
> include a new attribute so its class definition is now:
>
> class foo1 {
>    String a;
>    String b;
>    String c;
> }
>
> What tools/approaches can I use to modify all of my XML files to
> include the new attribute 'c' with a certain value say 'newattrvalue'.
>  I need this tool to be fairly powerful but easy to use because we are
> in a commercial environment and can add/remove complex attributes from
> existing classes that are not of simple types String, int, boolean, etc.
>
> Thanks,
> Stephen
>

Hi Stephen,

> What tools/approaches can I use to modify all of my XML files to
> include the new attribute 'c' with a certain value
> say 'newattrvalue'.

You can modify XML with XSLT; tho here you may be better off doing it within the
class.

Both are discussed in the JSX manual:
http://jsx.org/pdf/JSXmanual.pdf



XSLT
----
The JSX manual (see above, or link at top of www.jsx.org/support.html)
has examples of accessing the JSX XML format in terms of classes and fields
(pp.20-25).


Within the class
----------------
But for this case, I would suggest putting this evolution code within the
classes themselves - this is because that is where the
evolution occurred in the first place, and the person making the change will
know what value to use.

JSX uses the same hooks as JOS (Java Object Serialization - standard part of
java, in java.io.*) for this kind of evolution. It
enables your objects to look at the fields that are in the stream, and if
something is missing, to supply the correct value. (you
could also do this by testing for null, 0 or false, but then you can't
distinguish between the field being absent, or the field
being present and actually having that value).

This is discussed on page 10 of the JSX manual - but because it is the same as
JOS, there are also several tutorials about it.
"serialPersistentFields" is probably the best search term for this.


> I need this tool to be fairly powerful but easy to use because
> we are in a commercial environment and can add/remove
> complex attributes from existing classes that are not of
> simple types String, int, boolean, etc.

Adding complex types is probably simpler to do within the classes.
You can also do it with XSLT and XML: I'd suggest generating the XML you need
(by writing code to create the object you need, and
then serializing it), and then writing an XSLT script to insert it into the XML
for each object of that class.

Deleting is automatic, because when reading, JSX silently discards a value if
its field does not appear in the current version of
the class (same as JOS).


cheers,
Brendan

--- In JSX-ideas@yahoogroups.com, "Stephen Kurlow" <skurlow@...> wrote:
>
> Lets say for example I have:
>
> class foo1 {
>    String a;
>    String b;
> }
>
> and I have literally hundreds of different objects of class foo1
> serialised to different XML files. Now I need to modify class foo1 to
> include a new attribute so its class definition is now:
>
> class foo1 {
>    String a;
>    String b;
>    String c;
> }
>
> What tools/approaches can I use to modify all of my XML files to
> include the new attribute 'c' with a certain value say 'newattrvalue'.
>  I need this tool to be fairly powerful but easy to use because we are
> in a commercial environment and can add/remove complex attributes from
> existing classes that are not of simple types String, int, boolean, etc.
>
> Thanks,
> Stephen
>

Good Morning All.

I have two issues that I am hoping someone can help us address.  We
purchased JSX around 9 months ago and have been very happy but have
noticed a couple of little issues recently.

First, we upgraded our version of Java (we run on HP-UX PA-RISC
systems) to 1.5.5 and now JSX is complaining about not being able to
determine the version of the JVM it is running for and says it is
defaulting to a 1.4 version.  I am happy to report that this is still
working fine, it's just filling up our logs and causing the Systems
Admins to yell at my team a little.

I remember this issue coming up around 4 or 5 months ago, and I
thought the new version of JSX removed this check.  Working under
that assumption, we downloaded a new version of JSX (from a URL that
we downloaded our purchased version from, just incremented the
version number as needed) but now we are seeing this.

      [java] Thanks for evaluating JSX for 30 days.
      [java] Thanks for evaluating JSX for 30 days.
      [java] If you need more time, please contact company@...
(for work)
      [java] If you need more time, please contact company@...
(for work)
      [java] For students, an academic version is avaiable at:
www.jsx.org/academic
      [java] For students, an academic version is avaiable at:
www.jsx.org/academic
      [java] Buy JSX at www.jsx.org/buy.html
      [java] Buy JSX at www.jsx.org/buy.html

We just downloaded the new version 2 weeks ago, plus we have what I
thought was the proper purchased version so I am really confused and
scared.

Right now this only happens on our test box, but if it starts in
production, things could get bad.

In addition to this error, the new JSX jar (JSX2.2.5.2) is still
complaining about the JVM version.


For now I am rolling back our version of JSX from JSX2.2.5.2 to
JSX2.2.5.1, but would like to know how to address the issues above
and where to get a proper jar for the upgraded version (hopefully
without the JVM check).

Details:
OS: HP-UX PA-RISC
JVM: HP's JVM 1.5.5
JSX Version: JSX2.2.5.1 and JSX2.2.5.2


Thanks
-JM

Sorry.  I went a reply via email last week but looks like it never
made it into the system.

Here is a copy of that email:


Here is the message from JSX while running on the HP's.
      [java] ---ATTENTION!---  JSX could not recognize your
implementation of java, which is:
      [java]     implVendor="Hewlett-Packard Co."
      [java]     specVersion="1.5"
      [java]     implVersion=" 1.5.0.05"
      [java] In the meantime, JSX2 will try the standard
implementation for Java 1.4 - which will probably work
      [java] Please post the above information to: jsx-
ideas@yahoogroups.com
      [java]  - in particular, please state whether the standard
implementation worked or not, for both writing and reading.  Please
do a few tests before you post.

      [java]     If JSX's guess really does work, it can be fixed with:
      [java]     if (implVendor.equals("Hewlett-Packard Co.") &&
specVersion.equals("1.5") && implVersion.equals ("1.5.0.02"))
      [java]     magicName = "JSX.magic.MagicClass14";

Also, I wont post the URL that I downloaded the file from, but could
you send it to me privately since the URL that i used last time no
longer works.

















--- In JSX-ideas@yahoogroups.com, Brendan <melbourne.research@...>
wrote:
>
> Hi James,
>
> Did the current download work for you?
>
> When you get a chance, could you send the version info that JSX
outputs. I
> need the exact strings to be able to check for them, so I can
remove these
> messages for you  It would also help me determine how best to avoid
you
> seeing these messages in future.
>
> I hope you're feeling reassured.
>
>
> cheers,
> Brendan
>
> On 27/12/06, Brendan <melbourne.research@...> wrote:
> >
> > Hi James,
> >
> > We should be able to fix these hassles up quickly.
> >
> > Expired:
> > I just checked the purchase version now, and confirmed that it is
working
> > normally (ie. not expired, and not giving the message you saw).
> >
> >   (1) Could you download it again, and confirm whether this fixes
the
> > problem? This would be a simple fix.
> >
> > BTW: I have been working on our release system over the past few
weeks, so
> > it is possible you got an incorrect version at the exact time you
> > downloaded. Seems unlikely, but that would explain what you are
seeing. The
> > purchased version of the jar has a few extra characters appended
to the
> > filename, relative to the trial version.
> >
> >
> > JVM:
> > The immediate solution to your problem is to add your specific
JVM to the
> > next release.
> >
> >   (2) JSX should write out a detailed report on the JVM version
etc -
> > could you include that, please?
> >
> > This release should happen within a day of getting that info from
you.
> >
> > Yes, you're right that I'd decided to disable the JVM check - but
this
> > caused problems for other users. Managing the targetting of
multiple JVM
> > versions and manufacturers is difficult.
> >
> >
> > cheers,
> > Brendan
> > PS: It's late here right now, so I'll revisit the JVM problem in
detail
> > tomorrow. The problem is to target your JVM so that you won't get
your logs
> > filled up when you upgrade your JVM next time; and that won't
interfere with
> > JSX detecting a JVM it hasn't seen before. The difficulty is that
whenever a
> > JVM is upgraded, it is a "JVM it hasn't seen before", as it is
*possible*
> > the internal implementation of the JVM's serialization has been
changed (ie,
> > of JOS, Java Object Serialization) - and JSX relies on this
internal
> > implementation.
> >
> > But in reality, JOS doesn't change very often; I've only seen it
change
> > between major version releases of the specification (Java 1.2,
1.3, 1.4,
> > 1.5) - implementation versions haven't changed the implementation
at all,
> > in fact. It's not something that other manufacturers want to mess
around
> > with either.
> >
> >
> > On 27/12/06, James Maes <jjmaes@...> wrote:
> > >
> > >   Good Morning All.
> > >
> > > I have two issues that I am hoping someone can help us address.
We
> > > purchased JSX around 9 months ago and have been very happy but
have
> > > noticed a couple of little issues recently.
> > >
> > > First, we upgraded our version of Java (we run on HP-UX PA-RISC
> > > systems) to 1.5.5 and now JSX is complaining about not being
able to
> > > determine the version of the JVM it is running for and says it
is
> > > defaulting to a 1.4 version. I am happy to report that this is
still
> > > working fine, it's just filling up our logs and causing the
Systems
> > > Admins to yell at my team a little.
> > >
> > > I remember this issue coming up around 4 or 5 months ago, and I
> > > thought the new version of JSX removed this check. Working under
> > > that assumption, we downloaded a new version of JSX (from a URL
that
> > > we downloaded our purchased version from, just incremented the
> > > version number as needed) but now we are seeing this.
> > >
> > > [java] Thanks for evaluating JSX for 30 days.
> > > [java] Thanks for evaluating JSX for 30 days.
> > > [java] If you need more time, please contact
company@...<company%40jsx.org>
> > > (for work)
> > > [java] If you need more time, please contact
company@...<company%40jsx.org>
> > > (for work)
> > > [java] For students, an academic version is avaiable at:
> > > www.jsx.org/academic
> > > [java] For students, an academic version is avaiable at:
> > > www.jsx.org/academic
> > > [java] Buy JSX at www.jsx.org/buy.html
> > > [java] Buy JSX at www.jsx.org/buy.html
> > >
> > > We just downloaded the new version 2 weeks ago, plus we have
what I
> > > thought was the proper purchased version so I am really
confused and
> > > scared.
> > >
> > > Right now this only happens on our test box, but if it starts in
> > > production, things could get bad.
> > >
> > > In addition to this error, the new JSX jar (JSX2.2.5.2) is still
> > > complaining about the JVM version.
> > >
> > > For now I am rolling back our version of JSX from JSX2.2.5.2 to
> > > JSX2.2.5.1, but would like to know how to address the issues
above
> > > and where to get a proper jar for the upgraded version
(hopefully
> > > without the JVM check).
> > >
> > > Details:
> > > OS: HP-UX PA-RISC
> > > JVM: HP's JVM 1.5.5
> > > JSX Version: JSX2.2.5.1 and JSX2.2.5.2
> > >
> > > Thanks
> > > -JM
> > >
> > >
> > >
> >
> >
>

This email is to inform you about the release of version '2.2.5.3' of 'Java
Serialization to XML' through freshmeat.net. All URLs and other useful
information can be found at

     http://freshmeat.net/projects/jsx/

The changes in this release are as follows:
This version has been confirmed with HP's 1.5 JVM. This version also
regains compatibility with Java 1.2, though final fields cannot be
set in Java 1.2.

Release focus:
4 - Minor feature enhancements

Project added:
Tue, Oct 10th 2000 01:06 (6 years, 2 months ago)

Project description:
Java Serialization to XML (JSX) translates between Java and XML,
making it possible to search, test, profile, and audit your object
data with ordinary XML and text processing tools. Your data can be
migrated to new application versions, to C++, and to other
applications by transforming the XML. Unlike other Java XML
serializers, JSX is accurate for all objects.

Trove categories:
[Development Status  ] 5 - Production/Stable
[Environment         ] Console (Text Based), MacOS X, Other Environment,
Web Environment, Win32 (MS Windows)
[Intended Audience   ] Developers
[License             ] OSI Approved :: GNU General Public License (GPL),
Other/Proprietary License with Free Trial
[Programming Language] Java
[Topic               ] Communications, Database, Software Development,
Software Development :: Libraries, Software Development :: Libraries ::
Java Libraries, Software Development :: Object Brokering, System ::
Archiving, System :: Recovery Tools, Text Processing :: Markup :: XML

If you would like to cancel subscription to releases of this project,
login to freshmeat.net and choose 'home' from the personal menubar at the
top of the page. You'll be presented with a list of projects and
categories you're subscribed to in the right column, which you may cancel
by highlighting the project or category in question and clicking the
'delete' button.

Sincerely,
freshmeat.net

Hi Stephen,

"serialPersistentFields" is the approach I was talking about. Here's an example:
http://java.sun.com/j2se/1.5.0/docs/guide/serialization/spec/examples.html

You customize how the object is serialized and deserialized by adding
callback methods to it, readObject and writeObject - JSX will call
these. Within these, you can use the serialPersistentFields (an array
that defines the class's fields for the purposes of serialization - so
they can differ from the actual fields of the class), and GetField and
PutField to read/write them.

So, you can customize how fields are read in, with these virtual
fields that you can process in whatever way you need to before
assigning the values to fields. For serialization, you can write out
the fields as normal.

I recommend having a play around with this. You can use this as a
migration mechanism, to read in the old version and write out the new.
You can inspect the XML to verify it has made the change you intended
to make.

For simple changes, it may be easier to modify the XML directly.

Note: for primitive type changes, JSX automatically converts them to
the expected type.


Here's the JOS spec.
http://java.sun.com/j2se/1.5.0/docs/guide/serialization/spec/serialTOC.html


BTW: There's only one change to serialization in Java 1.6 (very esoteric):
   
http://java.sun.com/javase/6/docs/technotes/guides/serialization/relnotes6.html

cheers,
Brendan

This email is to inform you about the release of version '2.2.5.4' of 'Java
Serialization to XML' through freshmeat.net. All URLs and other useful
information can be found at

     http://freshmeat.net/projects/jsx/

The changes in this release are as follows:
Unknown JVMs no longer cause warnings (which cluttered up logfiles),
unless the hooks required by JSX are missing.

Release focus:
6 - Minor bugfixes

Project added:
Tue, Oct 10th 2000 01:06 (6 years, 3 months ago)

Project description:
Java Serialization to XML (JSX) translates between Java and XML,
making it possible to search, test, profile, and audit your object
data with ordinary XML and text processing tools. Your data can be
migrated to new application versions, to C++, and to other
applications by transforming the XML. Unlike other Java XML
serializers, JSX is accurate for all objects.

Trove categories:
[Development Status  ] 5 - Production/Stable
[Environment         ] Console (Text Based), MacOS X, Other Environment,
Web Environment, Win32 (MS Windows)
[Intended Audience   ] Developers
[License             ] OSI Approved :: GNU General Public License (GPL),
Other/Proprietary License with Free Trial
[Programming Language] Java
[Topic               ] Communications, Database, Software Development,
Software Development :: Libraries, Software Development :: Libraries ::
Java Libraries, Software Development :: Object Brokering, System ::
Archiving, System :: Recovery Tools, Text Processing :: Markup :: XML

If you would like to cancel subscription to releases of this project,
login to freshmeat.net and choose 'home' from the personal menubar at the
top of the page. You'll be presented with a list of projects and
categories you're subscribed to in the right column, which you may cancel
by highlighting the project or category in question and clicking the
'delete' button.

Sincerely,
freshmeat.net

This email is to inform you about the release of version '2.2.5.5' of 'Java
Serialization to XML' through freshmeat.net. All URLs and other useful
information can be found at

     http://freshmeat.net/projects/jsx/

The changes in this release are as follows:
JSX now works with recent versions of BEA's JRockit 1.4 and 1.5.

Release focus:
4 - Minor feature enhancements

Project added:
Tue, Oct 10th 2000 01:06 (6 years, 3 months ago)

Project description:
Java Serialization to XML (JSX) translates between Java and XML,
making it possible to search, test, profile, and audit your object
data with ordinary XML and text processing tools. Your data can be
migrated to new application versions, to C++, and to other
applications by transforming the XML. Unlike other Java XML
serializers, JSX is accurate for all objects.

Trove categories:
[Development Status  ] 5 - Production/Stable
[Environment         ] Console (Text Based), MacOS X, Other Environment,
Web Environment, Win32 (MS Windows)
[Intended Audience   ] Developers
[License             ] OSI Approved :: GNU General Public License (GPL),
Other/Proprietary License with Free Trial
[Programming Language] Java
[Topic               ] Communications, Database, Software Development,
Software Development :: Libraries, Software Development :: Libraries ::
Java Libraries, Software Development :: Object Brokering, System ::
Archiving, System :: Recovery Tools, Text Processing :: Markup :: XML

If you would like to cancel subscription to releases of this project,
login to freshmeat.net and choose 'home' from the personal menubar at the
top of the page. You'll be presented with a list of projects and
categories you're subscribed to in the right column, which you may cancel
by highlighting the project or category in question and clicking the
'delete' button.

Sincerely,
freshmeat.net

This email is to inform you about the release of version '2.2.5.6' of 'Java
Serialization to XML' through freshmeat.net. All URLs and other useful
information can be found at

     http://freshmeat.net/projects/jsx/

The changes in this release are as follows:
Documentation was added for class evolution/object migration by
transforming the XML using XSLT.

Release focus:
2 - Documentation

Project added:
Tue, Oct 10th 2000 01:06 (6 years, 3 months ago)

Project description:
Java Serialization to XML (JSX) translates between Java and XML,
making it possible to search, test, profile, and audit your object
data with ordinary XML and text processing tools. Your data can be
migrated to new application versions, to C++, and to other
applications by transforming the XML. Unlike other Java XML
serializers, JSX is accurate for all objects.

Trove categories:
[Development Status  ] 5 - Production/Stable
[Environment         ] Console (Text Based), MacOS X, Other Environment,
Web Environment, Win32 (MS Windows)
[Intended Audience   ] Developers
[License             ] OSI Approved :: GNU General Public License (GPL),
Other/Proprietary License with Free Trial
[Programming Language] Java
[Topic               ] Communications, Database, Software Development,
Software Development :: Libraries, Software Development :: Libraries ::
Java Libraries, Software Development :: Object Brokering, System ::
Archiving, System :: Recovery Tools, Text Processing :: Markup :: XML

If you would like to cancel subscription to releases of this project,
login to freshmeat.net and choose 'home' from the personal menubar at the
top of the page. You'll be presented with a list of projects and
categories you're subscribed to in the right column, which you may cancel
by highlighting the project or category in question and clicking the
'delete' button.

Sincerely,
freshmeat.net

____________________________| Advertising |____________________________
Track & Manage Your Source Code and Digital Assets for FREE with Perforce


Discover how you can manage your source code and digital assets faster and
easier with Perforce. Perforce offers visual client interfaces for
Linux, Mac, Solairs,FreeBSD and Windows. Learn more and get a free two
user download at


http://sel.as-us.falkag.net/sel?cmd=lnk&kid=133888&bid=282689&dat=121642&opt=0&r\
dm=[timestamp]

____________________________| Advertising |____________________________

We have a site license for JSX. We have upgraded our project to
JDK1.6.0
and now JSX is complaining. Does JSX continue to operate properly
despite the message? Do we have to pay to be compatible with the
latest
version of the JDK? What are our options?



**** MESSAGE ****
---ATTENTION!---  JSX could not recognize your implementation of
java, which is:
   implVendor="Sun Microsystems Inc."
   specVersion="1.6"
   implVersion="1.6.0"
In the meantime, JSX2 will try the standard implementation for Java
1.4 - which will probably work
Please post the above information to: jsx-ideas@yahoogroups.com
  - in particular, please state whether the standard implementation
worked or not, for both writing and reading.  Please do a few tests
before you post.

   If JSX's guess really does work, it can be fixed with:
   if (implVendor.equals("Sun Microsystems Inc.") &&
specVersion.equals("1.6") && implVersion.equals("1.6.0"))
   magicName = "JSX.magic.MagicClass14";


**** LICENSE Type****
Description: JSX Site Distribution License
From: Brendan Macmillan t/as JSX Enterprises Merchant's cart ID: JSX
Site Distribution License Authorisation Date/Time: 22/Jun/2004
15:59:52

**** VERSION ****
I don't know what version we are using. There is no version info. In
the jar manifest. The is no version info in the jar name, such a
axis-1.1.jar. I did a quick search of the user manual, and did not
see a runtime way to display jar version.

This email is to inform you about the release of version '2.2.6.0' of 'Java
Serialization to XML' through freshmeat.net. All URLs and other useful
information can be found at

     http://freshmeat.net/projects/jsx/

The changes in this release are as follows:
Compatibility with Java 1.6 was added.

Release focus:
5 - Major feature enhancements

Project added:
Tue, Oct 10th 2000 01:06 (6 years, 4 months ago)

Project description:
Java Serialization to XML (JSX) translates between Java and XML,
making it possible to search, test, profile, and audit your object
data with ordinary XML and text processing tools. Your data can be
migrated to new application versions, to C++, and to other
applications by transforming the XML. Unlike other Java XML
serializers, JSX is accurate for all objects.

Trove categories:
[Development Status  ] 5 - Production/Stable
[Environment         ] Console (Text Based), MacOS X, Other Environment,
Web Environment, Win32 (MS Windows)
[Intended Audience   ] Developers
[License             ] OSI Approved :: GNU General Public License (GPL),
Other/Proprietary License with Free Trial
[Programming Language] Java
[Topic               ] Communications, Database, Software Development,
Software Development :: Libraries, Software Development :: Libraries ::
Java Libraries, Software Development :: Object Brokering, System ::
Archiving, System :: Recovery Tools, Text Processing :: Markup :: XML

If you would like to cancel subscription to releases of this project,
login to freshmeat.net and choose 'home' from the personal menubar at the
top of the page. You'll be presented with a list of projects and
categories you're subscribed to in the right column, which you may cancel
by highlighting the project or category in question and clicking the
'delete' button.

Sincerely,
freshmeat.net

____________________________| Advertising |____________________________
Open source and Linux from HP


From eight consecutive years of Linux market leadership to countless
community outreach programs, HP has proven solutions you can value, on a
next generation, highly-efficient BladeSystem platform ideal for Linux,
with the approach, experience, and customer commitment you can trust.


http://showcase.linux.com/hpos.tmpl
____________________________| Advertising |____________________________

--- In JSX-ideas@yahoogroups.com, "dcmacrae_boston" <dcmacrae@...> wrote:

> Do we have to pay to be compatible with the latest version of the JDK?

Just to confirm: the just released version of JSX is compatible with
Java 1.6, and it is free for you because your license covers all 2.2.*
version of JSX.

The JSX version you originally purchased was released before Java 1.5
- and there are some Java features introduced in Java 1.5 (Enums) that
required special support in serialization.

I recommend you upgrade. It's free for you.

I will send you the download URL again (ie for the purchase version,
that doesn't expire in 30 days) directly.


cheers,
Brendan Macmillan

Hi Edison,

  You can customize the JSX serialization of the class using the
  standard techniques as for JOS (Java Object Serialization). See below.
  But first, let me ask something:

  How much shorter do you need it to be?  The JSX output truly is
  verbose; but even if shorter, XML is still pretty verbose:
   (1). Would zipping the XML help enough? Due to the redundancy of
  JSX's XML, it compresses very well.
   (2). If you have an "image file", is there any way to just save that
  file (eg in a DB, or in the filesystem), and refer to it from the XML,
  instead of serializing as XML what is already a serial format?  (I
  recognize there can be good reasons for not doing this)


  Customizing JSX:
  For example, you could create a string that represents the image (in
  base64, or whatever you want), and record that as the serial form (and
  the decoder to read this back). Here's two ways of making JSX use your
  code:

  If the class is your own (ie you can edit it), you do this by writing
  writeObject() and readObject() methods in your class - these are
  call-back methods that JSX will call in your class.

  If the class is not your own (ie you can't edit it), you can subclass
  JSX.ObjectWriter, and implement the "Object objectReplace(Object obj)"
  method: in it, you detect if the object is of the class in question,
  and if it is, construct a new object, which has a field initialized to
  the String you want (as above).  For reading, you subclass
  JSX.ObjectReader, and implement "Object resolveObject(Object obj)" etc


  There are lots of resources available for how to do this. There's the
  JSX manual on www.jsx.org/support.html

  http://java.sun.com/j2se/1.5.0/docs/guide/serialization/spec/output.html

  http://java.sun.com/j2se/1.5.0/docs/guide/serialization/spec/input.html

  There are many tutorials online: search for JOS customization.

  Please post to the mailing list how you are going, and any questions you have.


  Hope this helps,
  Brendan


  On 26/03/2008, edison ouyang <edison728@...> wrote:
  > Hi:
  >    I am using the trial version JSX to serialize and de-serialize the
  > object.
  >    I serialized an image file, this is the output for the image:
  >   <primitive type='byte' value='-119'/>
  >        <primitive type='byte' value='80'/>
  >       <primitive type='byte' value='78'/>
  >       <primitive type='byte' value='71'/>
  >       <primitive type='byte' value='13'/>
  >        <primitive type='byte' value='10'/>
  >       <primitive type='byte' value='26'/>
  >       <primitive type='byte' value='10'/>
  >       <primitive type='byte' value='0'/>
  >        <primitive type='byte' value='0'/>
  >       <primitive type='byte' value='0'/>
  >       <primitive type='byte' value='13'/>
  >       <primitive type='byte' value='73'/>
  >        <primitive type='byte' value='72'/>
  >       <primitive type='byte' value='68'/>
  >       <primitive type='byte' value='82'/>
  >       <primitive type='byte' value='0'/>
  >        <primitive type='byte' value='0'/>
  >       <primitive type='byte' value='0'/>
  >       <primitive type='byte' value='-6'/>
  >       <primitive type='byte' value='0'/>
  >        <primitive type='byte' value='0'/>
  >       <primitive type='byte' value='0'/>
  >       <primitive type='byte' value='-6'/>
  >       <primitive type='byte' value='8'/>
  >        <primitive type='byte' value='6'/>
  >       <primitive type='byte' value='0'/>
  >       <primitive type='byte' value='0'/>
  >       <primitive type='byte' value='0'/>
  >        <primitive type='byte' value='-120'/>
  >       <primitive type='byte' value='-20'/>
  >       <primitive type='byte' value='90'/>
  >       <primitive type='byte' value='61'/>
  >        <primitive type='byte' value='0'/>
  >       <primitive type='byte' value='0'/>
  >       <primitive type='byte' value='5'/>
  >        ......................
  >
  > this method to keep the image in the xml makes the file quite big.
  > Is it possible to customize the other encoding methods defined in the API
  > such as using base 64 for image.
  >
  > Thanks for your time.
  >
  > edison
  >
  >
  >
  >
  >
  >
  >



--
  The competent programmer is fully aware of the strictly limited size
  of his own skull; therefore he approaches the programming task in full
  humility, and among other things he avoids clever tricks like the
  plague. - Dijkstra


--
The competent programmer is fully aware of the strictly limited size
of his own skull; therefore he approaches the programming task in full
humility, and among other things he avoids clever tricks like the
plague. - Dijkstra

sorry for the message; testing