Eclipse Community Forums: JavaServer Faces » [REQ] Wizards

Help

Home

Home » Eclipse Projects » JavaServer Faces » [REQ] Wizards - Create Managed Bean

Show: Today's Messages :: Show Polls :: Message Navigator

[REQ] Wizards - Create Managed Bean [message #469145]

Fri, 29 July 2005 00:02

Ian Trimble

Messages: 137
Registered: July 2009

Senior Member

Feature requirements:

1) Create Managed Bean

2) Extension Points
- To be determined

Report message to a moderator

Re: [REQ] Wizards - Create Managed Bean [message #469889 is a reply to message #469145]

Fri, 29 July 2005 19:05

Jeff Duska

Messages: 11
Registered: July 2009

Junior Member

Ian Trimble wrote:
> Feature requirements:
>
> 1) Create Managed Bean
>
> 2) Extension Points
> - To be determined
>
>

Isn't this more of J2EE requirement that should be part of the EJB
support in the WTP?

Report message to a moderator

Re: [REQ] Wizards - Create Managed Bean [message #469895 is a reply to message #469889]

Fri, 29 July 2005 19:45

Igor Shabalov

Messages: 38
Registered: July 2009

Member

Managed Beans is specific Java Beans in JSF. It is specified in Faces
Context and there is special facility for Managed Beans in JSF. For sure
it's JSF related artifact.

You can find small example how to use JSF managed Beans for Dependency
Injection in my blog here : http://blog.exadel.com/?p=6

Best,
Igor.

"Jeff Duska" <jeff.duska_removethis@noaa.gov> wrote in message
news:dcdukc$jf5$1@news.eclipse.org...
> Ian Trimble wrote:
>> Feature requirements:
>>
>> 1) Create Managed Bean
>>
>> 2) Extension Points
>> - To be determined
>>
>>
>
> Isn't this more of J2EE requirement that should be part of the EJB support
> in the WTP?
>

Report message to a moderator

Re: [REQ] Wizards - Create Managed Bean [message #470385 is a reply to message #469145]

Fri, 12 August 2005 15:36

Glenn Silverman

Messages: 19
Registered: July 2009

Junior Member

Ian Trimble wrote:
> Feature requirements:
>
> 1) Create Managed Bean
>
> 2) Extension Points
> - To be determined
>
>
A managed bean per JSP page should be avoided. That's the .NET model.
JSF is more flexible allowing one-to-many and many-to-one relationships.
The idea is that beans are bound to components. Related components - by
some id construct - is preferrable.

Glenn...

Report message to a moderator

Re: [REQ] Wizards - Create Managed Bean [message #470386 is a reply to message #470385]

Fri, 12 August 2005 16:47

Ian Trimble

Messages: 137
Registered: July 2009

Senior Member

There have been some requests for some type of binding between a managed
bean and a JSP page throughout several threads. The main argument in the
requests seems sound; some folks want to work this way, and we should not
prevent them from doing so. That said, I personally (and obviously other
folks also) generally do not want to work this way, and so we should also be
allowed to work in the manner that suits us.

We're currently thinking along the lines of this being optional
functionality, such as it is in JDeveloper. At JSP creation time the user
can choose whether or not to "auto-bind" to a new or existing backing bean,
and subsequent behaviour while editing the JSP page will respect this
"auto-bind" setting and act appropriately.

Thoughts?

- Ian (Oracle)

"Glenn Silverman" <glancey3@cox.net> wrote in message
news:ddifpp$gin$1@news.eclipse.org...
> Ian Trimble wrote:
>> Feature requirements:
>>
>> 1) Create Managed Bean
>>
>> 2) Extension Points
>> - To be determined
>>
>>
> A managed bean per JSP page should be avoided. That's the .NET model. JSF
> is more flexible allowing one-to-many and many-to-one relationships.
> The idea is that beans are bound to components. Related components - by
> some id construct - is preferrable.
>
> Glenn...
>

Report message to a moderator

Re: [REQ] Wizards - Create Managed Bean [message #470396 is a reply to message #470386]

Mon, 22 August 2005 19:35

john rohrlich

Messages: 10
Registered: July 2009

Junior Member

I find Ian's position quite reasonable. There is enough interest in the
bean per page style to include support for those users who like to work
in this style.

- john

Ian Trimble wrote:
> There have been some requests for some type of binding between a managed
> bean and a JSP page throughout several threads. The main argument in the
> requests seems sound; some folks want to work this way, and we should not
> prevent them from doing so. That said, I personally (and obviously other
> folks also) generally do not want to work this way, and so we should also be
> allowed to work in the manner that suits us.
>
> We're currently thinking along the lines of this being optional
> functionality, such as it is in JDeveloper. At JSP creation time the user
> can choose whether or not to "auto-bind" to a new or existing backing bean,
> and subsequent behaviour while editing the JSP page will respect this
> "auto-bind" setting and act appropriately.
>
> Thoughts?
>
> - Ian (Oracle)
>
> "Glenn Silverman" <glancey3@cox.net> wrote in message
> news:ddifpp$gin$1@news.eclipse.org...
>
>>Ian Trimble wrote:
>>
>>>Feature requirements:
>>>
>>>1) Create Managed Bean
>>>
>>>2) Extension Points
>>> - To be determined
>>>
>>>
>>
>>A managed bean per JSP page should be avoided. That's the .NET model. JSF
>>is more flexible allowing one-to-many and many-to-one relationships.
>>The idea is that beans are bound to components. Related components - by
>>some id construct - is preferrable.
>>
>>Glenn...
>>
>
>
>

Report message to a moderator