This may not be relevant to you but you might want to try and get away
from the specifics of the client implementation (i.e. Servlets) as soon
as possible. If you extract the required data fom the HttpServletRequest
into a client neutral form (e.g. a List of parameters) and send that to
your session bean you shouldn't get the problem. This has the added
advantage that your session bean can then be used by any client that can
talk to the EJB server, e.g. a SWING client, or another web client that
talks to EJB.
This is discussed somewhere in the depths of the J2EE blueprint that I
think you can download from http://java.sun.com/j2ee/blueprints/
Matty.
Thomas Hagedorn wrote:
>
> Hi there,
>
> In my application, I want to forward all HttpServletRequests from the
> jsp over a wrapperbean to a SessionBean to process the data there.
> jsp to bean works fine, but if I get the home interface of my
> SessionBean and call a method with the HttpServletRequests as
> parameter, nothing appears in the SessionBean but I don't see any
> exception, only a 'null' for the HttpServletRequests in the SessionBean.
> If I do the same with a String, it works fine.
> The other way round it works returning a complex JavaObject from a
> SessionBean method.
> Are there any restrictions for the parameters I can pass to an EJB ?
>
> hopefull waiting for good advice
>
> best regards
> tom
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
