On 9/17/07, p7k <[EMAIL PROTECTED]> wrote:
>
> Dear Matt,
>
> There's no explicit reference to that Spring class.
> My LocationManager extends your GenericManager and implements my
> LocationManager and LocationService interfaces.
>
> you can see the  http://pastebin.com/m6749f1d8 code here @ pastebin .
>
> I tried it both: with the WebService implementation and without, but
> resistance is futile.
>
> Serializing UserManager objects also produces:
> java.io.NotSerializableException:
> org.springframework.beans.factory.support.DefaultListableBeanFactory
>
> but again, I don't think that this is what causes the problem, since your
> UserForm works perfectly.
> I really don't know what to think.

I googled for NotSerializableException and DefaultListableBeanFactory.
I found this from a couple years ago:

http://tinyurl.com/3dr2kt

If you're calling the same backend classes and not using the
ApplicationContext specifically, I don't know what the problem could
be.

>
> If you could, please clarify: can both the bean and jsf+facelets cause this
> error, or just the bean.
>
>
> Thank you for your quick response.
>
> BTW: the current jetty doesn't live well with facelets, i looked on jira and
> your ticket is inconclusive (to me anyway) as to what is going to happen
> with that and when.  if possible, please clarify.
>

Can you give me an example of "not live well"? It might be an issue
with MyFaces + Jetty. Does it work OK if you deploy to Tomcat? You can
use "mvn -Dcargo.wait=true" to test.

Matt

>
>
>
> mraible wrote:
> >
> > Does your LocationManager have a reference to the Spring class mentioned?
> >
> > On 9/17/07, p7k <[EMAIL PROTECTED]> wrote:
> >>
> >> Dear appfusers,
> >>
> >> I've been trying to debug "setAttribute: Non-serializable attribute"
> >> issue
> >> that occurs when I navigate to my forms which are modeled very closely
> >> after
> >> appfuse tutorials.
> >>
> >> I understand that it is the <distributable/> tag at work here, posing a
> >> strict serialization requirement on anything that enters the session
> >> under
> >> Tomcat.
> >>
> >> I checked the Customer class which is the focus of the form, and it
> >> serializes fine.  I checked the LocationManager which I also attach to
> >> the
> >> form's bean and found the following:
> >> java.io.NotSerializableException:
> >> org.springframework.beans.factory.support.DefaultListableBeanFactory
> >>
> >> However, an attempt to serialize appfuse's UserManager is also futile,
> >> but
> >> everything works with the UserForm, so ...   I guess the problem is not
> >> with
> >> the manager.
> >>
> >> Hence, I have a question:  can this error be caused only by some
> >> non-serializable stuff in the backing bean of an action
> >> http://pastebin.com/m70131e8e - code at pastebin - , or in the xhtml [jsf
> >> +
> >> facelets] also ?
> >>
> >> Any help would be very much appreciated !
> >>
> >>
> >>
> >>
> >> --
> >> View this message in context:
> >> http://www.nabble.com/Non-serializable-attribute-blues.---JSF%2BTomcat--tf4471692s2369.html#a12750015
> >> Sent from the AppFuse - User mailing list archive at Nabble.com.
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >>
> >>
> >
> >
> > --
> > http://raibledesigns.com
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> >
>
> --
> View this message in context: 
> http://www.nabble.com/Non-serializable-attribute-blues.---JSF%2BTomcat--tf4471692s2369.html#a12750354
> Sent from the AppFuse - User mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
http://raibledesigns.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to