Re: EJB3.0 and Backing Beans Design

Hi! Hi! For this there is e.g. JBoss Seam, or, if you would like to use a lightweigt approach, the conversation tag in tomahawk sandbox. The conversation tag sounds interesting. Could you describe it on http://wiki.apache.org/myfaces/MyFacesComponents? Done.

RE: EJB3.0 and Backing Beans Design

is the right way to go. Eagerly awaiting the WIKI... Thanks for the great work guys! Best regards, Yee -Original Message- From: Mario Ivankovits [mailto:[EMAIL PROTECTED] Sent: Thursday, July 06, 2006 10:48 PM To: Thomas Heute Cc: users@myfaces.apache.org Subject: Re: EJB3.0 and Backing

Re: EJB3.0 and Backing Beans Design

Hi Thomas, In this case maybe you can fix inputSugestAjax component from myfaces-sandbox. Seam is building other kind of solution for Ajax. that myfaces team and the number of differences(incompatibilities) is increasing day by day. Maybe you need to look more to the others ideas about

Re: EJB3.0 and Backing Beans Design

Hi! Spring web flow is a also a good alternative to the conversation system you are describing... Sure. The reason why we developed yet another conversation/dialog stuff is, that compared to seam (dependency hell) and things like sprint web flow, shale dialog our tag doesn't require any

Re: EJB3.0 and Backing Beans Design

The reason why we developed yet another conversation/dialog stuff is, that compared to seam (dependency hell) and things like sprint web flow, shale dialog our tag doesn't require any additional configuration. Seam has tons of deps! to much. Being able to control the flow using

Re: EJB3.0 and Backing Beans Design

Hi Rogerio! But this deps comes with JBoss Seam distribution, somebody found any other big issue on JBoss Seam beyond this one? Even if they come with the distribution, you have to take care of them. Additional issues? Well, personally I dont like it to use annotations for nearly everything.

Re: EJB3.0 and Backing Beans Design

2006/7/6, Mario Ivankovits [EMAIL PROTECTED]: Even if they come with the distribution, you have to take care of them.Additional issues?Well, personally I dont like it to use annotations for nearly everything.And seam would like to solve too much. For example JSF has some issues with redirects,

Re: EJB3.0 and Backing Beans Design

Please stop fudding around... You went a bit too far. This one is funny: I think seam is getting too complex - way too much to read, no? If we could measure the complexity of a framework by the number of pages of the documentation, the worse documented framework would be the simplest... We

Re: EJB3.0 and Backing Beans Design

Hi! If we could measure the complexity of a framework by the number of pages of the documentation, the worse documented framework would be the simplest... It wasn't the number of pages, but the number of different topics. I was asked about my opinion and so I answered AND I stated that I

Re: EJB3.0 and Backing Beans Design

Thomas Heute wrote: Please stop fudding around... You went a bit too far. This one is funny: " I think seam is getting too complex - way too much to read, no?" If we could measure the complexity of a framework by the number of pages of the documentation, the worse documented framework

Re: EJB3.0 and Backing Beans Design

Hi! I am not sure, if it is really required to separate the entities and the view model. We use hibernate too, but directly use the entities in the view. This means, if one changes some data, we use the transparent mechanismn of the persistence framework to have them persisted. For sure, this

Re: EJB3.0 and Backing Beans Design

Hello, On Wed, 2006-07-05 at 10:06 +0200, Mario Ivankovits wrote: For this there is e.g. JBoss Seam, or, if you would like to use a lightweigt approach, the conversation tag in tomahawk sandbox. The conversation tag sounds interesting. Could you describe it on

Re: EJB3.0 and Backing Beans Design

Hi! For this there is e.g. JBoss Seam, or, if you would like to use a lightweigt approach, the conversation tag in tomahawk sandbox. The conversation tag sounds interesting. Could you describe it on http://wiki.apache.org/myfaces/MyFacesComponents? Yes, I am aware that documentation

RE: EJB3.0 and Backing Beans Design

2006 6:06 PM To: MyFaces Discussion Subject: Re: EJB3.0 and Backing Beans Design Hi! I am not sure, if it is really required to separate the entities and the view model. We use hibernate too, but directly use the entities in the view. This means, if one changes some data, we use the transparent

Re: EJB3.0 and Backing Beans Design

Spring web flow is a also a good alternative to the conversation system you are describing... for some reasons I prefere the Shale / ADF dialog on that. It is closer to JSF than the Spring one. -Matt