On 9/18/07, Matt Raible <[EMAIL PROTECTED]> wrote:
> On 9/18/07, p7k <[EMAIL PROTECTED]> wrote:
> >
> > In terms of jetty, I was referring to
> > http://issues.appfuse.org/browse/APF-856
> > http://issues.appfuse.org/browse/APF-856
> > I experience most 'null object' problems with my facelets templates that use
> > lots of non-explicitly initialized parameters.  Everything works well under
> > Tomcat, including your 404 (errors) page.
>
> I've successfully been able to switch an AppFuse application from
> MyFaces to Sun's RI. The 404 doesn't happen in Jetty with Sun's RI -
> which implies this is a bug in MyFaces. I'll create a wiki page so
> others can switch if they'd like.

Here's the wiki page:

http://appfuse.org/display/APF/Changing+from+MyFaces+to+Sun%27s+RI

Hopefully we can eventually make this as easy as excluding/adding
dependencies and commenting out the MyFaces listener in web.xml.

Many of the JavaScript issues are caused by the fact that I can't get
@PostConstruct to work with Tomcat or Jetty out-of-the-box.

Matt


>
> >
> > Boy, I get no love from this non-serializable business, though.
> > Could you take a look at my applicationContext file (real short)
> > http://pastebin.com/m6be47161 http://pastebin.com/m6be47161
>
> The only thing I can think of is your references to JSF classes in your 
> Manager:
>
>     // Validation Methods
>     public Boolean isValid(BaseLocation location, FacesContext facesContext) {
>         // Hours validation
>         if (!location.getHours().isValid()) {
>             FacesMessage msgTime = new FacesMessage();
>             msgTime.setSeverity(FacesMessage.SEVERITY_ERROR);
>             msgTime.setSummary("Erroneous Operation Hours");
>             msgTime.setDetail("Opening Time is later than Closing Time");
>             facesContext.addMessage("locationForm:distHoursErrors",msgTime);
>             return false;
>         }
>
>         return true;
>     }
>
> In general, it's a good idea to not have your lower tiers calling your
> upper tiers.
>
> Otherwise, I'm like you - at a loss!
>
> Matt
>
> >
> > Much obliged !!!
> >
> >
> >
> > mraible wrote:
> > >
> > > 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]
> > >
> > >
> > >
> >
> > --
> > View this message in context: 
> > http://www.nabble.com/Non-serializable-attribute-blues.---JSF%2BTomcat--tf4471692s2369.html#a12750786
> > 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
>


-- 
http://raibledesigns.com

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

Reply via email to