Hi Martin, I have designed my application in the classical obejct-oriented way so that each use case has a controller, some boundary objects (JSF pages) and entities. I believe your page-bean is the controller for your application use case. I do not see how you can avoid a controller, unless you go back to lumping everything into one object.
I have a navigation aspect for each business object. This aspect introduces a navigateTo() method into the object, which contains the logic for navigation. I.e. returns the String to be used in the navigation case. I have not tested this with an object which can be used over multiple pages yet. Note this is a pet project, so I will be making slow progress. Regards, Fintan -----Original Message----- From: Martin Marinschek [mailto:[EMAIL PROTECTED] Sent: 23 August 2006 20:03 To: MyFaces Discussion Subject: Re: very simple question regarding h:inputText You're using aspects? great! Manfred and me have been working on what we call "Lightweight aspect-oriented JSF-UIs" ;) where each business-object is automatically wrapped in a JSF-enhanced aspect, if necessary. We still have a page-bean, though. for storing the aspects, if nothing else. regards, Martin On 8/23/06, Conway. Fintan (IT Solutions) <[EMAIL PROTECTED]> wrote: > I have to disagree. The way that I read Martin's setup is that Martin > is keeping the UI/navigation logic of his application in a different > class/layer to the business model. (You may correct me if I am wrong) > > I like the fact that I can use a simple POJO (business model) as the > centre of my application. In my applications the business model is a > managed bean. Using JDO I can also persist this POJO to the database > in a similar fashion. In order to keep View and Control separate from > the Model I use aspects to capture the navigation and persistence > stuff. Thus I do NOT duplicate any business logic, and I keep the > Model separate from and View or Control logic. > > -----Original Message----- > From: Iordanov, Borislav (GIC) [mailto:[EMAIL PROTECTED] > Sent: 22 August 2006 22:00 > To: MyFaces Discussion > Subject: RE: very simple question regarding h:inputText > > > That's point. You are essentially duplicating your business model in > order to fit the UI framework. > > -----Original Message----- > From: Martin Marinschek [mailto:[EMAIL PROTECTED] > Sent: Tuesday, August 22, 2006 4:52 PM > To: MyFaces Discussion > Subject: Re: very simple question regarding h:inputText > > Personally, I don't use my business model as managed beans. My > "managed-beans" are a layer of page-supporting Java-classes instead, > and they carry business model objects as properties. > > e.g. I don't use person as a managed bean - instead I have a > PersonEditor bean which will allow me to edit not only the person, but > all accompanying information as well. > > regards, > > Martin > > On 8/22/06, Iordanov, Borislav (GIC) <[EMAIL PROTECTED]> wrote: > > No, it's defined in a Java class that contains action methods for > > several different (but conceptually related) forms. I'd like my > "backing > > beans" to not have any JSF API dependencies. IMHO, this is one of > > the biggest problems with JSF - it's too API intrusive as a > > framework. It seems to me that it likes to either (1) make your > > business model dependent on it or (2) force you to duplicate your > > business model. But > I > > might be mistaken, haven't used it enough yet. > > > > Regards, > > Bolerio > > > > -----Original Message----- > > From: Behrang Saeedzadeh [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, August 22, 2006 4:14 PM > > To: MyFaces Discussion > > Subject: Re: very simple question regarding h:inputText > > > > Isn't the action method a method defined in the backing bean :-? > > > > -Behi > > > > On 8/22/06, Iordanov, Borislav (GIC) <[EMAIL PROTECTED]> wrote: > > > I don't have a backing bean and I don't want to have one as it > doesn't > > > make sense for such an "add new" text box. The action method is > > > the proper place, thanks a lot. > > > > > > -----Original Message----- > > > From: Andrew Robinson [mailto:[EMAIL PROTECTED] > > > Sent: Tuesday, August 22, 2006 2:47 PM > > > To: MyFaces Discussion > > > Subject: Re: very simple question regarding h:inputText > > > > > > Answer: it depends > > > > > > if you want the value to be cleared even though there are > > > validation > > > > errors or if your submit is immediate, then you can bind your text > box > > > to a varaible on the backing bean. In the actionListener or action > of > > > the submit, clear the submitted value and local value of the > > > component. > > > > > > if you want the value to be cleared when a "normal" > > > (non-immediate) action is run, just clear the value from the > > > backing bean that the text box is bound to. > > > > > > On 8/22/06, Iordanov, Borislav (GIC) <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > > > I have an input box and an "Add" button next to it that allows > > > > the > > > user to > > > > enter new entries of something. After each submit, the text of > > > > my > > > input box > > > > must be cleared empty. But by default JSF keeps that last > submitted > > > value as > > > > the value of the component. How do I circumvent that? Any ideas? > > > > > > > > > > > > > > > > Thanks, > > > > > > > > Bolerio > > > > > > > > > > > > > > > > > -- > > "We can only see a short distance ahead, > > but we can see plenty there > > that needs to be done." - Alan Turing > > > > "Science is a differential equation. Religion > > is a boundary condition" - Alan Turing > > > > Behrang Saeedzadeh > > http://www.jroller.com/page/behrangsa > > http://my.opera.com/behrangsa > > > > > -- > > http://www.irian.at > > Your JSF powerhouse - > JSF Consulting, Development and > Courses in English and German > > Professional Support for Apache MyFaces > > > * ** *** ** * ** *** ** * ** *** ** * > This email and any files transmitted with it are confidential and > intended solely for the use of the individual or entity to whom they > are addressed. Any views or opinions presented are solely those of the > author, and do not necessarily represent those of ESB. If you have > received this email in error please notify the sender. > > Although ESB scans e-mail and attachments for viruses, it does not > guarantee that either are virus-free and accepts no liability for any > damage sustained as a result of viruses. > > * ** *** ** * ** *** ** * ** *** ** * > > -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
