- Ian
Raghu/David,
Just to
clarify our mission, there are many cases where a feature request would be
"meeting such and such a spec level", for example when we claim to
support a given level of J2EE or Web service spec. In those cases
interoperability or portability are P1 goals. This means that our tools can't
"blow up" on any valid input document. However, there is a lot of gray area in
terms of how well we support the spec. We could tolerate it or we could
exploit it.
As for JSP 2.1 EL, I
don't think is part of Java EE 5 is it? If not, then we can support it
on a best efforts basis in anticipation of it becoming part of a future Java
EE version.
Arthur Ryman,
IBM
Software Group, Rational Division
blog:
http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL
969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920,
TL 969-4920
mobile: +1-416-939-5063, text: [EMAIL PROTECTED]
David M Williams
<[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
01/12/2006 12:17 PM
|
Please respond
to
"General discussion of project-wide or architectural
issues." |
|
|
To
| "General discussion of
project-wide or architectural issues."
<[email protected]>
|
|
cc
|
|
|
Subject
| Re: [wtp-dev] Support
for JSP 2.1 EL in WTP 1.5.. |
|
Raghu,
In short, no, no plans.
But, let me explain and
make some recommendations (for you and others making feature request
or
plan queries).
If you are
asking for someone to commit to doing more work, the answer will almost always
be no. :)
But,
more seriously, we seldom try to set a goal of "meeting such and such a spec
level". I'd like to
encourage anyone making a similar feature
request to me more specific in terms of what a user needs.
For example,
"content assist proposals for the new xyz construct that are new in version
abc".
You know,
maybe we won't give a validation error if used incorrectly, but may be syntax
highlighting is important?
Or, is some new runtime capabilities needed? Or
.. perhaps some new test effort is needed? Or, perhaps just
tolerate both
#{} and ${} as "EL" but do little else?
So, perhaps you could open a feature request
detailing what support you would like, expect, or need for 2.1?
That is,
be sure to provide some motivating message in the bugzilla report ... is
it to enhance a users experience,
is it required for a certain adopter to
ship a product/project on top of WTP, will (or do) errors occur if such
2.1 version constructs used? No to mention, be sure to spell out what's
wrong with the current support, or
how it is inadequate for the needs
expressed. Or, even, what the alternatives are with current level of
support (e.g. "have to install 'xyz.jar' by hand, but would be nice to
detect and do automatically").
Of course, if you were just asking because if not
planned you were volunteering to do the work, well,
then nevermind me and
yes please do! :)
HTH
David
Raghu Srinivasan
<[EMAIL PROTECTED]>
Sent by:
[EMAIL PROTECTED]
01/10/2006 08:52 PM
Please respond
to
"General discussion of project-wide or architectural
issues." <[email protected]> |
|
|
To
| "General discussion
of project-wide or architectural issues."
<[email protected]>, [EMAIL PROTECTED]
|
|
cc
|
|
|
Subject
| [wtp-dev] Support for JSP 2.1 EL
in WTP 1.5.. |
|
Hi,
Are there plans to
support the JSP 2.1 _expression_ language in the WTP
1.5 release? The JSF
Tools team is in the process of planning for the
WTP 1.5 relase and any
pointer on this topic would be
useful.
Thanks
Raghu
_______________________________________________
wtp-dev
mailing
list
[email protected]
https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________
wtp-dev mailing
list
[email protected]
https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________
wtp-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/wtp-dev
