Yeah you have to return an arraylist or a vector, i.e something that is
serializable. It is never a good idea to pass ResultSet objects around.
Although it is attractive in terms of changeability (eg adding more fields
etc) to use a ResultSet, it can become a nightmare when there are network
Use a disconnected RowSet; that's what they were
designed for. You won't
have to modify your application because RowSet
extends ResultSet!!
- Original Message -
From:
Andres
Garcia Hourcade
To: Orion-Interest
Sent: Monday, November 26, 2001 10:41
AM
Subject:
Please please PLEASE do not send messages with Read Receipt Requests to
the mailing list. Thats just
annoying.
-Original Message-
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On
Behalf Of Andres Garcia Hourcade
Sent: Monday, November 26, 2001
1:42 PM
To: Orion-Interest
Exception says it
all...
This is a logn-time discussed
problem/issue.
Your Ejb methods should return the
valid J2EE types: simple types, Serializable, EJBObject, Remote and
Externalizable (I think).
The ResultSet is none of the
above.
You should do something else. A
Vector would be
Many
thanks, i will modifiy my sources to return Vectors
Thks
again
-Original Message-From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Lachezar
DobrevSent: lunes, 26 de noviembre de 2001 8:33To:
Orion-InterestSubject: Re: OrionRemoteException: Error
(de
Title: Message
you
should NOT be returning results sets back from ANY remote
methods.
it is
very very very very bad design, with a capital VERYand a capital
BAD
you
should have serializable wrapper objects.
-Original Message-From:
[EMAIL PROTECTED]
[mailto:[EMAIL
Make sure you are closing your all of your ResultSets after you've
finished with them (same for Statement and Connection objects).
Chris
Andres Garcia Hourcade wrote:
I have an application (jsp ejb) running with version 1.4.0, i am trying to
upgrade the same EAR in 1.5.2 version, but i get
Orion 1.5.2 is much stricter about what you can put into app / session
scopes. Any objects you want to store MUST be serializable (they didn't have
to be in 1.4.0, the 1.5.2 behaviour is more spec compliant).
I think the ResultSet you're using isn't serializable. Try pulling the data
out first
