I'm not injecting it directly. I'm using a proxy class to get a reference
to the stateless bean's interface like so:
public class CartProxy
{
private static ShoppingCartLocal lookupCartInterface()
{
ShoppingCartLocal cart = null;
try
{
InitialContext ctx = new
your CartProxy does not implement serialiazable so it cannot be serialized...
-igor
On Thu, Nov 19, 2009 at 7:30 AM, VGJ zambi...@gmail.com wrote:
I'm not injecting it directly. I'm using a proxy class to get a reference
to the stateless bean's interface like so:
public class CartProxy
{
One would think...however I tried it and it makes no difference. None of my
proxy classes implement Serializable and this exception occurs nowhere else,
also.
Just to be certain, I just went through and implemented it on *all* of my
proxy classes in this app. No change.
On Thu, Nov 19, 2009
according to the stacktrace, this component:
path=3:cartForm:orderLinesView]
has this reference: final com.myapp.session.ShoppingCartLocal
so looks like you are holding on to your bean directly instead of using a proxy.
-igor
On Thu, Nov 19, 2009 at 8:48 AM, VGJ zambi...@gmail.com wrote:
One
I reference the bean's interface in order to use it, yes. What's the
alternative? Would I instead access everything through a proxy class and
store the proxy itself into the WebSession, to retain a reference? As it
is, each page in the checkout process changes the Stateful bean's properties
and
i am going to guess that inside //stuff happens here... you access
the final cart field. when you do this inside an anonymous class it
keeps a reference, so that is what is causing your serialization
problem. instead of having the final field, do the lookup
((UserSession)getSession()).getCart();
The problems always seem to occur in that cloud in the middle of the diagram
that says stuff happens here or this is where the magic happens.
--
Jeremy Thomerson
http://www.wickettraining.com
On Thu, Nov 19, 2009 at 12:04 PM, Igor Vaynberg igor.vaynb...@gmail.comwrote:
i am going to
Yep, you're right - I have a link inside of the populateItem method that
calls it one time, like so:
Link removeLink = new Link(removeLink)
{
public void onClick()
{
try
{
//proxy method to remove line item
phase 1: collect underpants
phase 2: ?
phase 3: profit
:)
-igor
On Thu, Nov 19, 2009 at 10:06 AM, Jeremy Thomerson
jer...@wickettraining.com wrote:
The problems always seem to occur in that cloud in the middle of the diagram
that says stuff happens here or this is where the magic happens.
Ha! I deserve that. I was hesitant to put the stuff happens here instead
of just dumping another 100 lines of code in there. Dammit. ;)
Anyhow, worked great. Thanks for clearing it up for me!
On Thu, Nov 19, 2009 at 11:26 AM, Igor Vaynberg igor.vaynb...@gmail.comwrote:
phase 1: collect
I'm completely at wits end here and I hope someone can point out what's
wrong.
I've got an e-commerce application that is simply moving between two pages
using setRedirectPage() when going from a product detail page to the
shopping cart page. There isn't anything remarkable about either of these
Your cart has a reference to the sessionBean ShopingCart. This is not
allowed, however. The IOC incjectionsupport makes this possible by wrapping
this EJB reference with a serializable proxy.
I only have expecience with wicket-spring end it works great. (In your case,
define your ejb reference in
wicket stuff contains a wicket-jee module which supports injecting ejb
beans into wicket components the same way that wicket-spring injects
wicket beans.
-igor
On Wed, Nov 18, 2009 at 10:37 PM, Pieter Degraeuwe
pieter.degrae...@systemworks.be wrote:
Your cart has a reference to the sessionBean
13 matches
Mail list logo
