Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » JavaServer Faces » Regarding Milestone 1 - Registering the JSF Implementation
Regarding Milestone 1 - Registering the JSF Implementation [message #470629] Mon, 31 October 2005 19:58 Go to next message
john rohrlich is currently offline john rohrlich
Messages: 10
Registered: July 2009
Junior Member
The "Register the JSF Implementation" use case calls for 6 pieces of
information:

* Name
* JSF Version supported
* Libraries
* Tag libraries
* Default servlet name
* Default servlet class

I don't think we need to collect "Tag Libraries" because the JSP spec
requires the tlds to be in the same jar as the implemenation so we can
just pick them up from the jar file.

- John Rohrlich
BEA Systems
Re: Regarding Milestone 1 - Registering the JSF Implementation [message #470631 is a reply to message #470629] Tue, 01 November 2005 01:05 Go to previous messageGo to next message
Ian Trimble is currently offline Ian Trimble
Messages: 137
Registered: July 2009
Senior Member
You're absolutely right, John.

Our current research-in-progress for M1 slims this list down to collecting
just Name, JSF Version, and Libraries. The servlet class name is fixed (as
"javax.faces.webapp.FacesServlet") by the JSF spec., and our current
thinking is that the "Default servlet name" should be a JSF preference, not
specific to any one implementation. (We haven't updated the M1 web page yet,
but we will as we work through our current investigations.)

It is possible (though not required) for a JSF implementation to include tag
libraries in addition to core and html, so post-M1 I expect we will explore
automated discovery of all TLDs in the specified libraries and possibly some
form of tag library registry.

Thanks for the input,
Ian Trimble (Oracle)

John Rohrlich wrote:
>
> The "Register the JSF Implementation" use case calls for 6 pieces of
> information:
>
> * Name
> * JSF Version supported
> * Libraries
> * Tag libraries
> * Default servlet name
> * Default servlet class
>
> I don't think we need to collect "Tag Libraries" because the JSP spec
> requires the tlds to be in the same jar as the implemenation so we can
> just pick them up from the jar file.
>
> - John Rohrlich
> BEA Systems
Re: Regarding Milestone 1 - Registering the JSF Implementation [message #470632 is a reply to message #470631] Tue, 01 November 2005 04:03 Go to previous messageGo to next message
Nitin Dahyabhai is currently offline Nitin Dahyabhai
Messages: 2267
Registered: July 2009
Senior Member
Ian Trimble wrote:
> It is possible (though not required) for a JSF implementation to include
> tag libraries in addition to core and html, so post-M1 I expect we will
> explore automated discovery of all TLDs in the specified libraries and
> possibly some form of tag library registry.

Actually, we've had a similar need in WTP's JSP component for a long
time. We've almost got a registry ready for API in the JSP
TaglibIndex class, but it's more oriented around locating a TLD (by
path or relative reference, web.xml mapping, project *buildpath*,
and JSP 1.2 auto-discovered URI) and providing information on how to
access its contents than actually modelling its contents directly.
Perhaps there's some space for collaboration, if not at least the
potential for reuse?

--
- Nitin


---
Nitin Dahyabhai
Eclipse WTP, IBM
Re: Regarding Milestone 1 - Registering the JSF Implementation [message #470634 is a reply to message #470632] Wed, 02 November 2005 21:43 Go to previous messageGo to next message
Raghu Srinivasan is currently offline Raghu Srinivasan
Messages: 265
Registered: July 2009
Senior Member
Nitin Dahyabhai wrote:
> Ian Trimble wrote:
>
>> It is possible (though not required) for a JSF implementation to
>> include tag libraries in addition to core and html, so post-M1 I
>> expect we will explore automated discovery of all TLDs in the
>> specified libraries and possibly some form of tag library registry.
>
>
> Actually, we've had a similar need in WTP's JSP component for a long
> time. We've almost got a registry ready for API in the JSP TaglibIndex
> class, but it's more oriented around locating a TLD (by path or relative
> reference, web.xml mapping, project *buildpath*, and JSP 1.2
> auto-discovered URI) and providing information on how to access its
> contents than actually modelling its contents directly. Perhaps there's
> some space for collaboration, if not at least the potential for reuse?
>
We are definitely interested in looking into the registry implementation
in the ESP component. Please point us to any design doc on this feature.
We can explore areas of collaboration for the TWP 1.5 release.
-Raghu


Raghu Srinivasan,
Project Lead - JSF
Re: Regarding Milestone 1 - Registering the JSF Implementation [message #470657 is a reply to message #470634] Wed, 30 November 2005 08:00 Go to previous messageGo to next message
Nitin Dahyabhai is currently offline Nitin Dahyabhai
Messages: 2267
Registered: July 2009
Senior Member
Raghu Srinivasan wrote:
> We are definitely interested in looking into the registry implementation
> in the ESP component. Please point us to any design doc on this feature.
> We can explore areas of collaboration for the TWP 1.5 release.

The design is intentionally minimal as it's oriented around
providing the information to retrieve the contents of a .tld so it
can be modelled, not providing a model of the .tld itself. You'll
find it documented at
http://eclipse.org/webtools/jst/components/jsp/designs/tagli bindex/taglibindex.html.
That in turn is linked from the JSP Component's Overview at
http://eclipse.org/webtools/jst/components/jsp/overview.html .
Questions, bug reports, and other feedback are welcome.

--
- Nitin


---
Nitin Dahyabhai
Eclipse WTP, IBM
Re: Regarding Milestone 1 - Registering the JSF Implementation [message #470660 is a reply to message #470657] Wed, 30 November 2005 17:43 Go to previous message
Raghu Srinivasan is currently offline Raghu Srinivasan
Messages: 265
Registered: July 2009
Senior Member
Nitin Dahyabhai wrote:
> Raghu Srinivasan wrote:
>
>> We are definitely interested in looking into the registry
>> implementation in the ESP component. Please point us to any design doc
>> on this feature. We can explore areas of collaboration for the TWP 1.5
>> release.
>
>
> The design is intentionally minimal as it's oriented around providing
> the information to retrieve the contents of a .tld so it can be
> modelled, not providing a model of the .tld itself. You'll find it
> documented at
> http://eclipse.org/webtools/jst/components/jsp/designs/tagli bindex/taglibindex.html.
> That in turn is linked from the JSP Component's Overview at
> http://eclipse.org/webtools/jst/components/jsp/overview.html . Questions,
> bug reports, and other feedback are welcome.
>
Thanks, Nitin. We will review and give our feedback.
-Raghu


Raghu Srinivasan,
Project Lead - JSF
Re: Regarding Milestone 1 - Registering the JSF Implementation [message #573780 is a reply to message #470629] Tue, 01 November 2005 01:05 Go to previous message
Ian Trimble is currently offline Ian Trimble
Messages: 137
Registered: July 2009
Senior Member
You're absolutely right, John.

Our current research-in-progress for M1 slims this list down to collecting
just Name, JSF Version, and Libraries. The servlet class name is fixed (as
"javax.faces.webapp.FacesServlet") by the JSF spec., and our current
thinking is that the "Default servlet name" should be a JSF preference, not
specific to any one implementation. (We haven't updated the M1 web page yet,
but we will as we work through our current investigations.)

It is possible (though not required) for a JSF implementation to include tag
libraries in addition to core and html, so post-M1 I expect we will explore
automated discovery of all TLDs in the specified libraries and possibly some
form of tag library registry.

Thanks for the input,
Ian Trimble (Oracle)

John Rohrlich wrote:
>
> The "Register the JSF Implementation" use case calls for 6 pieces of
> information:
>
> * Name
> * JSF Version supported
> * Libraries
> * Tag libraries
> * Default servlet name
> * Default servlet class
>
> I don't think we need to collect "Tag Libraries" because the JSP spec
> requires the tlds to be in the same jar as the implemenation so we can
> just pick them up from the jar file.
>
> - John Rohrlich
> BEA Systems
Re: Regarding Milestone 1 - Registering the JSF Implementation [message #573792 is a reply to message #470631] Tue, 01 November 2005 04:03 Go to previous message
Nitin Dahyabhai is currently offline Nitin Dahyabhai
Messages: 2267
Registered: July 2009
Senior Member
Ian Trimble wrote:
> It is possible (though not required) for a JSF implementation to include
> tag libraries in addition to core and html, so post-M1 I expect we will
> explore automated discovery of all TLDs in the specified libraries and
> possibly some form of tag library registry.

Actually, we've had a similar need in WTP's JSP component for a long
time. We've almost got a registry ready for API in the JSP
TaglibIndex class, but it's more oriented around locating a TLD (by
path or relative reference, web.xml mapping, project *buildpath*,
and JSP 1.2 auto-discovered URI) and providing information on how to
access its contents than actually modelling its contents directly.
Perhaps there's some space for collaboration, if not at least the
potential for reuse?

--
- Nitin


---
Nitin Dahyabhai
Eclipse WTP, IBM
Re: Regarding Milestone 1 - Registering the JSF Implementation [message #573804 is a reply to message #470632] Wed, 02 November 2005 21:43 Go to previous message
Raghu Srinivasan is currently offline Raghu Srinivasan
Messages: 265
Registered: July 2009
Senior Member
Nitin Dahyabhai wrote:
> Ian Trimble wrote:
>
>> It is possible (though not required) for a JSF implementation to
>> include tag libraries in addition to core and html, so post-M1 I
>> expect we will explore automated discovery of all TLDs in the
>> specified libraries and possibly some form of tag library registry.
>
>
> Actually, we've had a similar need in WTP's JSP component for a long
> time. We've almost got a registry ready for API in the JSP TaglibIndex
> class, but it's more oriented around locating a TLD (by path or relative
> reference, web.xml mapping, project *buildpath*, and JSP 1.2
> auto-discovered URI) and providing information on how to access its
> contents than actually modelling its contents directly. Perhaps there's
> some space for collaboration, if not at least the potential for reuse?
>
We are definitely interested in looking into the registry implementation
in the ESP component. Please point us to any design doc on this feature.
We can explore areas of collaboration for the TWP 1.5 release.
-Raghu


Raghu Srinivasan,
Project Lead - JSF
Re: Regarding Milestone 1 - Registering the JSF Implementation [message #578711 is a reply to message #470634] Wed, 30 November 2005 08:00 Go to previous message
Nitin Dahyabhai is currently offline Nitin Dahyabhai
Messages: 2267
Registered: July 2009
Senior Member
Raghu Srinivasan wrote:
> We are definitely interested in looking into the registry implementation
> in the ESP component. Please point us to any design doc on this feature.
> We can explore areas of collaboration for the TWP 1.5 release.

The design is intentionally minimal as it's oriented around
providing the information to retrieve the contents of a .tld so it
can be modelled, not providing a model of the .tld itself. You'll
find it documented at
http://eclipse.org/webtools/jst/components/jsp/designs/tagli bindex/taglibindex.html
That in turn is linked from the JSP Component's Overview at
http://eclipse.org/webtools/jst/components/jsp/overview.html
Questions, bug reports, and other feedback are welcome.

--
- Nitin


---
Nitin Dahyabhai
Eclipse WTP, IBM
Re: Regarding Milestone 1 - Registering the JSF Implementation [message #578749 is a reply to message #470657] Wed, 30 November 2005 17:43 Go to previous message
Raghu Srinivasan is currently offline Raghu Srinivasan
Messages: 265
Registered: July 2009
Senior Member
Nitin Dahyabhai wrote:
> Raghu Srinivasan wrote:
>
>> We are definitely interested in looking into the registry
>> implementation in the ESP component. Please point us to any design doc
>> on this feature. We can explore areas of collaboration for the TWP 1.5
>> release.
>
>
> The design is intentionally minimal as it's oriented around providing
> the information to retrieve the contents of a .tld so it can be
> modelled, not providing a model of the .tld itself. You'll find it
> documented at
> http://eclipse.org/webtools/jst/components/jsp/designs/tagli bindex/taglibindex.html
> That in turn is linked from the JSP Component's Overview at
> http://eclipse.org/webtools/jst/components/jsp/overview.html Questions,
> bug reports, and other feedback are welcome.
>
Thanks, Nitin. We will review and give our feedback.
-Raghu


Raghu Srinivasan,
Project Lead - JSF
Previous Topic:Sybase to Demo Faces Config Editor Today
Next Topic:Test.
Goto Forum:
  


Current Time: Wed Sep 17 23:39:48 GMT 2014

Powered by FUDForum. Page generated in 0.02210 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software