osdir.com
mailing list archive F.A.Q. -since 2001!



Subject: [xstream-dev] [jira] Created: (XSTR-101) XStream
should be able to work with classes that are
hot-redeployed - msg#00013

List: java.xstream.devel

Mail Archive Navigation:
by Date: Prev Next Date Index by Thread: Prev Next Thread Index

Message:

A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/XSTR-101

Here is an overview of the issue:
---------------------------------------------------------------------
Key: XSTR-101
Summary: XStream should be able to work with classes that are hot-redeployed
Type: Improvement

Status: Unassigned

Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown

Project: XStream
Fix Fors:
1.0.2

Assignee:
Reporter: Joe Walnes

Created: Thu, 22 Jul 2004 6:08 AM
Updated: Thu, 22 Jul 2004 6:08 AM

Description:
Stephane Nicoll wrote:

>Hello list,
>
>We use xstream in Jboss to serialize our messages to XML and post them to JMS
>queues. It works fine (great job) but when we hot redeploy serializable
>classes we have the following exception:
>
>11:10:08,587 ERROR [ejb.plugins.LogInterceptor]
>TransactionRolledbackLocalException in method: public abstract void
>javax.jms.MessageListener.onMessage(javax.jms.Message), causedBy:
>com.thoughtworks.xstream.converters.reflection.ObjectAccessException: Could
>not get field class java.lang.reflect.Field.codAmount: null
> at
>com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.vis
>itSerializableFields(Unknown Source)
> at
>com.thoughtworks.xstream.converters.reflection.ReflectionConverter.marshal(Un
>known Source)
> at
>com.thoughtworks.xstream.core.ReferenceByXPathMarshaller.convertAnother(Unkno
>wn Source)
> at com.thoughtworks.xstream.core.TreeMarshaller.start(Unknown Source)
> at
>com.thoughtworks.xstream.core.ReferenceByXPathMarshallingStrategy.marshal(Unk
>nown Source)
> at com.thoughtworks.xstream.XStream.marshal(Unknown Source)
> at com.thoughtworks.xstream.XStream.toXML(Unknown Source)
>
>To be clear, Xstream is not hot redeployed but the Objects to serialize are.
>Restarting Jboss solves the issue but this is quite annoying.
>
>We're using SUN JDK 1.4.2
>
>Thanks,
>
>Stéphane
>



---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira




Thread at a glance:

Previous Message by Date:

[xstream-dev] [jira] Commented: (XSTR-55) Ability to alias an entire package

The following comment has been added to this issue: Author: Gr?gory Joseph Created: Tue, 20 Jul 2004 3:05 PM Body: The previous patch isn't really satisfying me, because : - it doesn't actually map a package name to a "shortcut" name, but to empty string (ie, com.blah.bleh.SomeClass can not be aliased to "foo.SomeClass" but only to SomeClass) - it's based on startsWith and substring methods, which makes it a bit hairy - and possibly not very safe - for the sake of aliasing com.blah.bleh.bluh.SomeOtherClass to "bluh.SomeOtherClass" I'm planning on submitting another patch that would - allow actual aliasing of a package to a "prefix", but only A package and not it's subpackages - be based on full package name of a Class instead of just using startsWith on Class.getName() ... I'll do that .. eventually.. when my pc resurects. Please tell me what you think, anyway ;) --------------------------------------------------------------------- View this comment: http://jira.codehaus.org/browse/XSTR-55?page=comments#action_21970 --------------------------------------------------------------------- View the issue: http://jira.codehaus.org/browse/XSTR-55 Here is an overview of the issue: --------------------------------------------------------------------- Key: XSTR-55 Summary: Ability to alias an entire package Type: Improvement Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: XStream Components: Core Fix Fors: 1.1 Versions: 1.1 Assignee: Reporter: Joe Walnes Created: Thu, 6 May 2004 2:20 PM Updated: Tue, 20 Jul 2004 3:05 PM Description: Rather than having to do: xstream.alias("com.blah.mypackage.MyClass", "MyClass"); xstream.alias("com.blah.mypackage.YourClass", "YourClass"); xstream.alias("com.blah.mypackage.SheepClass", "SheepClass"); I'd like to be able to do: xstream.aliasPackage("com.blah.mypackage"); --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira

Next Message by Date:

Re: [xstream-dev] Cool changes and new Features

> Hello I am a newie in this mailing list, but i would like to be an assiduous contributor. Jose, First, I owe you a massive apology for taking a month to reply. I accidently filed your email in the wrong folder and forgot about it. Sorry!! The new features are (see attachments): 1 · New converters for data types: java.sql.Time java.sql.timestamp java.sql.Date java.util.Currency java.util.Locale java.util.regexp.Pattern Thanks! There have been requests for a lot of these. I'll integrate them shortly. 2 · I would like to perform XMLization as standard Java mechanism Reader/Writer allowing a well know API and combination with others Java Readers/Writers. Actually in test..., last week I can send this new feature: Sounds like a good idea. I'll add this to a later release. 3 · XMLize null objects: currently one uses of the XML for an Object is transformer to html/wml using XSLT... but the XML for null atributes not exists (except in root node or first level). In XSL if one node not exists can not apply their transform, this can be a big problem... [IMHO] consider that null objects (in fields, items in list, etc...) must be represented also into XML. I can see reasons for both ways. I'm happy to add that support but I think it should be optional. Thanks for your contributions. -Joe

Previous Message by Thread:

[xstream-dev] [jira] Commented: (XSTR-55) Ability to alias an entire package

The following comment has been added to this issue: Author: Gr?gory Joseph Created: Tue, 20 Jul 2004 3:05 PM Body: The previous patch isn't really satisfying me, because : - it doesn't actually map a package name to a "shortcut" name, but to empty string (ie, com.blah.bleh.SomeClass can not be aliased to "foo.SomeClass" but only to SomeClass) - it's based on startsWith and substring methods, which makes it a bit hairy - and possibly not very safe - for the sake of aliasing com.blah.bleh.bluh.SomeOtherClass to "bluh.SomeOtherClass" I'm planning on submitting another patch that would - allow actual aliasing of a package to a "prefix", but only A package and not it's subpackages - be based on full package name of a Class instead of just using startsWith on Class.getName() ... I'll do that .. eventually.. when my pc resurects. Please tell me what you think, anyway ;) --------------------------------------------------------------------- View this comment: http://jira.codehaus.org/browse/XSTR-55?page=comments#action_21970 --------------------------------------------------------------------- View the issue: http://jira.codehaus.org/browse/XSTR-55 Here is an overview of the issue: --------------------------------------------------------------------- Key: XSTR-55 Summary: Ability to alias an entire package Type: Improvement Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: XStream Components: Core Fix Fors: 1.1 Versions: 1.1 Assignee: Reporter: Joe Walnes Created: Thu, 6 May 2004 2:20 PM Updated: Tue, 20 Jul 2004 3:05 PM Description: Rather than having to do: xstream.alias("com.blah.mypackage.MyClass", "MyClass"); xstream.alias("com.blah.mypackage.YourClass", "YourClass"); xstream.alias("com.blah.mypackage.SheepClass", "SheepClass"); I'd like to be able to do: xstream.aliasPackage("com.blah.mypackage"); --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira

Next Message by Thread:

Re: [xstream-dev] Cool changes and new Features

> Hello I am a newie in this mailing list, but i would like to be an assiduous contributor. Jose, First, I owe you a massive apology for taking a month to reply. I accidently filed your email in the wrong folder and forgot about it. Sorry!! The new features are (see attachments): 1 · New converters for data types: java.sql.Time java.sql.timestamp java.sql.Date java.util.Currency java.util.Locale java.util.regexp.Pattern Thanks! There have been requests for a lot of these. I'll integrate them shortly. 2 · I would like to perform XMLization as standard Java mechanism Reader/Writer allowing a well know API and combination with others Java Readers/Writers. Actually in test..., last week I can send this new feature: Sounds like a good idea. I'll add this to a later release. 3 · XMLize null objects: currently one uses of the XML for an Object is transformer to html/wml using XSLT... but the XML for null atributes not exists (except in root node or first level). In XSL if one node not exists can not apply their transform, this can be a big problem... [IMHO] consider that null objects (in fields, items in list, etc...) must be represented also into XML. I can see reasons for both ways. I'm happy to add that support but I think it should be optional. Thanks for your contributions. -Joe
blog comments powered by Disqus

Home | News | Sitemap | FAQ | advertise | OSDir is an Inevitable website. GBiz is too!