Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » JavaServer Faces » Feedback on the proposal from the IBM team..
Feedback on the proposal from the IBM team.. [message #469066] Tue, 19 July 2005 18:28 Go to next message
Raghu Srinivasan is currently offline Raghu Srinivasan
Messages: 265
Registered: July 2009
Senior Member
Meeting notes from a conference call with the IBM team on the JSF Proposal.

Date: June 24th, 05
Attendees:
From Oracle: Raghu Srinivasan, Brian Fry, Stephen Tom and Ian Trimble
From IBM: Arthur Ryman, George DeCandio and team
Following are the comments on the proposal:

1) Add JSF Project nature to any Web Module
Instead of Nature, it should read Feature. This concept will be implemented
in WTP 1.0.

2) Graphical Editor for JSF page
This is a big ticket item. The proposal should be changed in one of the
following ways:
a) Drop it. This is a complex undertaking and may not be realistic. Also,
vendors use this feature as a value-add and may not be inclined to
participate in the project since it conflicts with their business interest.
b) Keep this feature for completeness, but move it to a future release. This
is not the first thing we will build.

3) Graphical Editor for faces-config.xml
a) This is more reasonable and a valid feature.
b) Include form-based editor . Investigate Lepido technology.

3) Wizard
The proposal should identify this as an extension point and also commit to
delivering related API's These can be used to generate the first cut of a
JSF page that can then be customized. Improves developer productivity.
Use cases:
a) WebServices project should be able to generate a default client in JSF.
Currently it generates in JSP.
b) Model Driven Development project: Generate JSF for a given model.
c) Generate a JSF page for a given backing bean.

4) Application Configuration - faces-config.xml
The proposal should say that there will be a Java model and associated API's
to manipulate this programmatically.

5)Tentative Schedule is to coincide with release of WTP 1.5

6) Solicit support from other vendors at JavaOne.


Raghu Srinivasan,
Project Lead - JSF
Re: Feedback on the proposal from the IBM team.. [message #469107 is a reply to message #469066] Thu, 28 July 2005 02:37 Go to previous messageGo to next message
Igor Shabalov is currently offline Igor Shabalov
Messages: 38
Registered: July 2009
Member
"Raghu Srinivasan" <e_raghu@yahoo.com> wrote in message
news:dbjgni$dob$1@news.eclipse.org...
> Meeting notes from a conference call with the IBM team on the JSF
> Proposal.
>
> Date: June 24th, 05
> Attendees:
> From Oracle: Raghu Srinivasan, Brian Fry, Stephen Tom and Ian Trimble
> From IBM: Arthur Ryman, George DeCandio and team
> Following are the comments on the proposal:
>
> 1) Add JSF Project nature to any Web Module
> Instead of Nature, it should read Feature. This concept will be
> implemented
> in WTP 1.0.
>
> 2) Graphical Editor for JSF page
> This is a big ticket item. The proposal should be changed in one of the
> following ways:
> a) Drop it. This is a complex undertaking and may not be realistic. Also,
> vendors use this feature as a value-add and may not be inclined to
> participate in the project since it conflicts with their business
> interest.
> b) Keep this feature for completeness, but move it to a future release.
> This
> is not the first thing we will build.

I agree with option (b)

>
> 3) Graphical Editor for faces-config.xml
> a) This is more reasonable and a valid feature.
> b) Include form-based editor . Investigate Lepido technology.

What Lepido technology? Can you give a link or explain it somehow?

>
> 3) Wizard
> The proposal should identify this as an extension point and also commit to
> delivering related API's These can be used to generate the first cut of a
> JSF page that can then be customized. Improves developer productivity.
> Use cases:
> a) WebServices project should be able to generate a default client in JSF.
> Currently it generates in JSP.
> b) Model Driven Development project: Generate JSF for a given model.

I think this use case is too wide, we need to identify way how to define the
model for JSF.

> c) Generate a JSF page for a given backing bean.

Interesting. I think we can explore possibility to "link" together JSF(JSP)
and Java editors and look to the page like a combination of JSP and java
class and sync changes somehow in both directions.

>
> 4) Application Configuration - faces-config.xml
> The proposal should say that there will be a Java model and associated
> API's
> to manipulate this programmatically.

I agree.

>
> 5)Tentative Schedule is to coincide with release of WTP 1.5

Make sense...


>
> 6) Solicit support from other vendors at JavaOne.

You have it already :-)

Best regards,
Igor.
Re: Feedback on the proposal from the IBM team.. [message #469110 is a reply to message #469107] Thu, 28 July 2005 09:49 Go to previous message
Michael Strothjohann is currently offline Michael Strothjohann
Messages: 52
Registered: July 2009
Member
in short: Lepido = "Tooling for Cocoon" .
There is eclipse newsgroup on Lepido.
project hompage: http://www.eclipse.org/lepido/
project proposal: http://www.eclipse.org/proposals/eclipse-lepido/
michael




"Igor Shabalov" <ishabalov@exadel.com> schrieb im Newsbeitrag
news:dc9ge7$jev$1@news.eclipse.org...
>
> "Raghu Srinivasan" <e_raghu@yahoo.com> wrote in message
> news:dbjgni$dob$1@news.eclipse.org...
>> Meeting notes from a conference call with the IBM team on the JSF
>> Proposal.
>>
>> Date: June 24th, 05
>> Attendees:
>> From Oracle: Raghu Srinivasan, Brian Fry, Stephen Tom and Ian Trimble
>> From IBM: Arthur Ryman, George DeCandio and team
>> Following are the comments on the proposal:
>>
>> 1) Add JSF Project nature to any Web Module
>> Instead of Nature, it should read Feature. This concept will be
>> implemented
>> in WTP 1.0.
>>
>> 2) Graphical Editor for JSF page
>> This is a big ticket item. The proposal should be changed in one of the
>> following ways:
>> a) Drop it. This is a complex undertaking and may not be realistic. Also,
>> vendors use this feature as a value-add and may not be inclined to
>> participate in the project since it conflicts with their business
>> interest.
>> b) Keep this feature for completeness, but move it to a future release.
>> This
>> is not the first thing we will build.
>
> I agree with option (b)
>
>>
>> 3) Graphical Editor for faces-config.xml
>> a) This is more reasonable and a valid feature.
>> b) Include form-based editor . Investigate Lepido technology.
>
> What Lepido technology? Can you give a link or explain it somehow?
>
>>
>> 3) Wizard
>> The proposal should identify this as an extension point and also commit
>> to
>> delivering related API's These can be used to generate the first cut of
>> a
>> JSF page that can then be customized. Improves developer productivity.
>> Use cases:
>> a) WebServices project should be able to generate a default client in
>> JSF.
>> Currently it generates in JSP.
>> b) Model Driven Development project: Generate JSF for a given model.
>
> I think this use case is too wide, we need to identify way how to define
> the model for JSF.
>
>> c) Generate a JSF page for a given backing bean.
>
> Interesting. I think we can explore possibility to "link" together
> JSF(JSP) and Java editors and look to the page like a combination of JSP
> and java class and sync changes somehow in both directions.
>
>>
>> 4) Application Configuration - faces-config.xml
>> The proposal should say that there will be a Java model and associated
>> API's
>> to manipulate this programmatically.
>
> I agree.
>
>>
>> 5)Tentative Schedule is to coincide with release of WTP 1.5
>
> Make sense...
>
>
>>
>> 6) Solicit support from other vendors at JavaOne.
>
> You have it already :-)
>
> Best regards,
> Igor.
>
Re: Feedback on the proposal from the IBM team.. [message #567175 is a reply to message #469066] Thu, 28 July 2005 02:37 Go to previous message
Igor Shabalov is currently offline Igor Shabalov
Messages: 38
Registered: July 2009
Member
"Raghu Srinivasan" <e_raghu@yahoo.com> wrote in message
news:dbjgni$dob$1@news.eclipse.org...
> Meeting notes from a conference call with the IBM team on the JSF
> Proposal.
>
> Date: June 24th, 05
> Attendees:
> From Oracle: Raghu Srinivasan, Brian Fry, Stephen Tom and Ian Trimble
> From IBM: Arthur Ryman, George DeCandio and team
> Following are the comments on the proposal:
>
> 1) Add JSF Project nature to any Web Module
> Instead of Nature, it should read Feature. This concept will be
> implemented
> in WTP 1.0.
>
> 2) Graphical Editor for JSF page
> This is a big ticket item. The proposal should be changed in one of the
> following ways:
> a) Drop it. This is a complex undertaking and may not be realistic. Also,
> vendors use this feature as a value-add and may not be inclined to
> participate in the project since it conflicts with their business
> interest.
> b) Keep this feature for completeness, but move it to a future release.
> This
> is not the first thing we will build.

I agree with option (b)

>
> 3) Graphical Editor for faces-config.xml
> a) This is more reasonable and a valid feature.
> b) Include form-based editor . Investigate Lepido technology.

What Lepido technology? Can you give a link or explain it somehow?

>
> 3) Wizard
> The proposal should identify this as an extension point and also commit to
> delivering related API's These can be used to generate the first cut of a
> JSF page that can then be customized. Improves developer productivity.
> Use cases:
> a) WebServices project should be able to generate a default client in JSF.
> Currently it generates in JSP.
> b) Model Driven Development project: Generate JSF for a given model.

I think this use case is too wide, we need to identify way how to define the
model for JSF.

> c) Generate a JSF page for a given backing bean.

Interesting. I think we can explore possibility to "link" together JSF(JSP)
and Java editors and look to the page like a combination of JSP and java
class and sync changes somehow in both directions.

>
> 4) Application Configuration - faces-config.xml
> The proposal should say that there will be a Java model and associated
> API's
> to manipulate this programmatically.

I agree.

>
> 5)Tentative Schedule is to coincide with release of WTP 1.5

Make sense...


>
> 6) Solicit support from other vendors at JavaOne.

You have it already :-)

Best regards,
Igor.
Re: Feedback on the proposal from the IBM team.. [message #567194 is a reply to message #469107] Thu, 28 July 2005 09:49 Go to previous message
Michael Strothjohann is currently offline Michael Strothjohann
Messages: 52
Registered: July 2009
Member
in short: Lepido = "Tooling for Cocoon" .
There is eclipse newsgroup on Lepido.
project hompage: http://www.eclipse.org/lepido/
project proposal: http://www.eclipse.org/proposals/eclipse-lepido/
michael




"Igor Shabalov" <ishabalov@exadel.com> schrieb im Newsbeitrag
news:dc9ge7$jev$1@news.eclipse.org...
>
> "Raghu Srinivasan" <e_raghu@yahoo.com> wrote in message
> news:dbjgni$dob$1@news.eclipse.org...
>> Meeting notes from a conference call with the IBM team on the JSF
>> Proposal.
>>
>> Date: June 24th, 05
>> Attendees:
>> From Oracle: Raghu Srinivasan, Brian Fry, Stephen Tom and Ian Trimble
>> From IBM: Arthur Ryman, George DeCandio and team
>> Following are the comments on the proposal:
>>
>> 1) Add JSF Project nature to any Web Module
>> Instead of Nature, it should read Feature. This concept will be
>> implemented
>> in WTP 1.0.
>>
>> 2) Graphical Editor for JSF page
>> This is a big ticket item. The proposal should be changed in one of the
>> following ways:
>> a) Drop it. This is a complex undertaking and may not be realistic. Also,
>> vendors use this feature as a value-add and may not be inclined to
>> participate in the project since it conflicts with their business
>> interest.
>> b) Keep this feature for completeness, but move it to a future release.
>> This
>> is not the first thing we will build.
>
> I agree with option (b)
>
>>
>> 3) Graphical Editor for faces-config.xml
>> a) This is more reasonable and a valid feature.
>> b) Include form-based editor . Investigate Lepido technology.
>
> What Lepido technology? Can you give a link or explain it somehow?
>
>>
>> 3) Wizard
>> The proposal should identify this as an extension point and also commit
>> to
>> delivering related API's These can be used to generate the first cut of
>> a
>> JSF page that can then be customized. Improves developer productivity.
>> Use cases:
>> a) WebServices project should be able to generate a default client in
>> JSF.
>> Currently it generates in JSP.
>> b) Model Driven Development project: Generate JSF for a given model.
>
> I think this use case is too wide, we need to identify way how to define
> the model for JSF.
>
>> c) Generate a JSF page for a given backing bean.
>
> Interesting. I think we can explore possibility to "link" together
> JSF(JSP) and Java editors and look to the page like a combination of JSP
> and java class and sync changes somehow in both directions.
>
>>
>> 4) Application Configuration - faces-config.xml
>> The proposal should say that there will be a Java model and associated
>> API's
>> to manipulate this programmatically.
>
> I agree.
>
>>
>> 5)Tentative Schedule is to coincide with release of WTP 1.5
>
> Make sense...
>
>
>>
>> 6) Solicit support from other vendors at JavaOne.
>
> You have it already :-)
>
> Best regards,
> Igor.
>
Previous Topic:Project creation wizard
Next Topic:[REQ] Application Configuration Resource File - Model with API
Goto Forum:
  


Current Time: Wed Sep 03 02:30:52 GMT 2014

Powered by FUDForum. Page generated in 0.13612 seconds