-
1. Re: HornetQDestination implements Serializable but is actually not serializable
clebert.suconic Sep 13, 2010 1:20 PM (in response to alkod)How would you expect to serialize a Session? A Session is something that's connnected to the server.
It's not supposed to be serialized and it doesn't make any sense doing it.
-
2. Re: HornetQDestination implements Serializable but is actually not serializable
leosbitto Sep 13, 2010 1:41 PM (in response to alkod)There is no need to serialize HornetQDestination - you could use Queue#getQueueName() on the sending side and Session#createQueue(String name) on the receiving side.
-
3. Re: HornetQDestination implements Serializable but is actually not serializable
leosbitto Sep 13, 2010 1:53 PM (in response to clebert.suconic)Clebert, if Session is not supposed to be serialized, then it should not be used as a field in a Serializable object (HornetQDestination). Either do not implement Serializable in HornetQDestination, or mark its field Session as transient (which would break the method delete() on temporary destinations, though).
-
4. Re: HornetQDestination implements Serializable but is actually not serializable
clebert.suconic Sep 13, 2010 2:05 PM (in response to leosbitto)Oh, I see what you mean now.
HornetQ Destination will hold the session for temporary destinations. I'm making it transient.
However, as you said, you don't need to serialize it.. you can just use its name.
-
5. Re: HornetQDestination implements Serializable but is actually not serializable
alkod Sep 13, 2010 3:04 PM (in response to clebert.suconic)Ok, thanks for clearing that up.