Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » JavaServer Faces » JSF Tools Project RC3 build+Tutorial posted..
JSF Tools Project RC3 build+Tutorial posted.. [message #471985] Wed, 31 May 2006 00:37 Go to next message
Raghu Srinivasan is currently offline Raghu SrinivasanFriend
Messages: 265
Registered: July 2009
Senior Member
Hi,

We have posted a build of the JSF Tools project along with a tutorial that
walks through the features in the build. You can access both of them from
this page: http://www.eclipse.org/webtools/jsf/dev_resource/index.html.

The next build on June 7th will be the feature freeze build.

Please review and post your comments, log issues.

The JSF Tools project build is integrated with the WTP Continuous Builds
and can be accessed from http://download.eclipse.org/webtools/committers/.
However, we noticed errors while verifying the build and hence didn't
announce its availability in the newsgroup. We hope to resolve this soon
and we will then post the result of our smoke tests to the mailing list.


Thanks
Raghu Srinivasan
JSF Tools Project Lead


Raghu Srinivasan,
Project Lead - JSF
Re: JSF Tools Project RC3 build+Tutorial posted.. [message #471987 is a reply to message #471985] Wed, 31 May 2006 03:12 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: paul.lecky.paradisefood.com.au

Raghu Srinivasan wrote:
> Hi,
>
> We have posted a build of the JSF Tools project along with a tutorial
> that walks through the features in the build. You can access both of
> them from this page:
> http://www.eclipse.org/webtools/jsf/dev_resource/index.html.
>
> The next build on June 7th will be the feature freeze build.
> Please review and post your comments, log issues.
>
> The JSF Tools project build is integrated with the WTP Continuous Builds
> and can be accessed from
> http://download.eclipse.org/webtools/committers/. However, we noticed
> errors while verifying the build and hence didn't announce its
> availability in the newsgroup. We hope to resolve this soon and we will
> then post the result of our smoke tests to the mailing list.
>
>
> Thanks
> Raghu Srinivasan
> JSF Tools Project Lead
>
Thanks for the great work Raghu. I am just starting with web
development and jsf looks to be the solution for me.
I'm looking forward to jsf coming out of incubation at the end of the month.
Re: JSF Tools Project RC3 build+Tutorial posted.. [message #471988 is a reply to message #471987] Wed, 31 May 2006 23:04 Go to previous messageGo to next message
Raghu Srinivasan is currently offline Raghu SrinivasanFriend
Messages: 265
Registered: July 2009
Senior Member
Hi Paul,

Thanks for taking the time to review the build. Please log issues you face
in bugzilla.
-Raghu


Raghu Srinivasan,
Project Lead - JSF
Re: JSF Tools Project RC3 build+Tutorial posted.. [message #471989 is a reply to message #471985] Thu, 01 June 2006 23:56 Go to previous messageGo to next message
Max Rydahl Andersen is currently offline Max Rydahl AndersenFriend
Messages: 225
Registered: July 2009
Senior Member
On Wed, 31 May 2006 02:37:10 +0200, Raghu Srinivasan
<raghunathan.srinivasan@oracle.com> wrote:

does this release/build contain any support for pluggable name resolver ?

/max

> Hi,
>
> We have posted a build of the JSF Tools project along with a tutorial
> that walks through the features in the build. You can access both of
> them from this page:
> http://www.eclipse.org/webtools/jsf/dev_resource/index.html.
>
> The next build on June 7th will be the feature freeze build. Please
> review and post your comments, log issues.
>
> The JSF Tools project build is integrated with the WTP Continuous Builds
> and can be accessed from
> http://download.eclipse.org/webtools/committers/. However, we noticed
> errors while verifying the build and hence didn't announce its
> availability in the newsgroup. We hope to resolve this soon and we will
> then post the result of our smoke tests to the mailing list.
>
>
> Thanks
> Raghu Srinivasan
> JSF Tools Project Lead
>



--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
Re: JSF Tools Project RC3 build+Tutorial posted.. [message #471990 is a reply to message #471989] Fri, 02 June 2006 18:04 Go to previous messageGo to next message
Raghu Srinivasan is currently offline Raghu SrinivasanFriend
Messages: 265
Registered: July 2009
Senior Member
Hi Max,

Pluggable name resolver will be available in the June 7th feature-freeze
drop.
Thanks
Raghu


Raghu Srinivasan,
Project Lead - JSF
Re: JSF Tools Project RC3 build+Tutorial posted.. [message #471992 is a reply to message #471989] Thu, 08 June 2006 16:56 Go to previous messageGo to next message
Cameron Bateman is currently offline Cameron BatemanFriend
Messages: 480
Registered: July 2009
Senior Member
Hi Max,

The pluggable resolver code is checked into CVS in should appear in the
weekly I-build on Friday.

The bug:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=145158

Contains example code for use. The bug description contains basic
instructions for how to run the examples.

Let me know if you have any problems or need further assistance.


--Cam
Re: JSF Tools Project RC3 build+Tutorial posted.. [message #471999 is a reply to message #471992] Thu, 15 June 2006 01:38 Go to previous messageGo to next message
Max Rydahl Andersen is currently offline Max Rydahl AndersenFriend
Messages: 225
Registered: July 2009
Senior Member
Hi,

I finally discovered your answer here ;)

I am trying to make it work but I get really many excpetions when using =
=

jsp/jsf related
files in non-jsf-faceted projects so it is kinda annoying ;(

but anyhow it looks like the functionallity is in there, but I must say =
I =

don't like
that all the symbol api requires things to extend EObject.

e.g. how do i create an ISymbol impl to e.g. return from resolveVariable=
?

/max

> Hi Max,
>
> The pluggable resolver code is checked into CVS in should appear in th=
e =

> weekly I-build on Friday.
>
> The bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=3D145158
>
> Contains example code for use. The bug description contains basic =

> instructions for how to run the examples.
>
> Let me know if you have any problems or need further assistance.
>
>
> --Cam
>



-- =

Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
Re: JSF Tools Project RC3 build+Tutorial posted.. [message #472000 is a reply to message #471999] Thu, 15 June 2006 01:43 Go to previous messageGo to next message
Max Rydahl Andersen is currently offline Max Rydahl AndersenFriend
Messages: 225
Registered: July 2009
Senior Member
btw. it also fails within the example app there is on that bug.

e.g. opening faces-config.xml gives me:

java.lang.IllegalArgumentException: Path must include project and resour=
ce =

name: /DTResolverExampleApp
at org.eclipse.core.runtime.Assert.isLegal(Assert.java:62)
at =

org.eclipse.core.internal.resources.Workspace.newResource(Wo rkspace.java=
:1565)
at =

org.eclipse.core.internal.resources.Container.getFolder(Cont ainer.java:1=
37)
at =

org.eclipse.jst.jsf.facesconfig.common.utils.WebrootUtil.get WebContentFo=
lder(WebrootUtil.java:79)
at =

org.eclipse.jst.jsf.facesconfig.ui.FacesConfigEditor.loadMod el(FacesConf=
igEditor.java:333)
at =

org.eclipse.jst.jsf.facesconfig.ui.FacesConfigEditor.setInpu t(FacesConfi=
gEditor.java:323)
at org.eclipse.ui.forms.editor.FormEditor.init(FormEditor.java: 132)
at =

org.eclipse.jst.jsf.facesconfig.ui.FacesConfigEditor.init(Fa cesConfigEdi=
tor.java:296)
at =

org.eclipse.ui.internal.EditorManager.createSite(EditorManag er.java:839)=



and when opening any other faces-config.xml:

org.eclipse.core.runtime.AssertionFailedException: assertion failed:
at org.eclipse.core.runtime.Assert.isTrue(Assert.java:109)
at org.eclipse.core.runtime.Assert.isTrue(Assert.java:95)
at =

org.eclipse.jst.jsf.facesconfig.ui.FacesConfigEditor.loadMod el(FacesConf=
igEditor.java:334)
at =

org.eclipse.jst.jsf.facesconfig.ui.FacesConfigEditor.setInpu t(FacesConfi=
gEditor.java:323)
at org.eclipse.ui.forms.editor.FormEditor.init(FormEditor.java: 132)
at =

org.eclipse.jst.jsf.facesconfig.ui.FacesConfigEditor.init(Fa cesConfigEdi=
tor.java:296)
at =

org.eclipse.ui.internal.EditorManager.createSite(EditorManag er.java:839)=

at =

org.eclipse.ui.internal.EditorReference.createPartHelper(Edi torReference=
..java:583)
at =

org.eclipse.ui.internal.EditorReference.createPart(EditorRef erence.java:=
372)
at =

org.eclipse.ui.internal.WorkbenchPartReference.getPart(Workb enchPartRefe=
rence.java:566)
at =

org.eclipse.ui.internal.EditorReference.getEditor(EditorRefe rence.java:2=
14)
at =

org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched( WorkbenchPag=
e.java:2588)
at =

org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(Workben chPage.java:=
2521)
at =

org.eclipse.ui.internal.WorkbenchPage.access$10(WorkbenchPag e.java:2513)=

at org.eclipse.ui.internal.WorkbenchPage$9.run(WorkbenchPage.ja va:2498)=

at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator .java:67=
)
=


/max



> Hi,
>
> I finally discovered your answer here ;)
>
> I am trying to make it work but I get really many excpetions when usin=
g =

> jsp/jsf related
> files in non-jsf-faceted projects so it is kinda annoying ;(
>
> but anyhow it looks like the functionallity is in there, but I must sa=
y =

> I don't like
> that all the symbol api requires things to extend EObject.
>
> e.g. how do i create an ISymbol impl to e.g. return from resolveVariab=
le =

> ?
>
> /max
>
>> Hi Max,
>>
>> The pluggable resolver code is checked into CVS in should appear in t=
he =

>> weekly I-build on Friday.
>>
>> The bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=3D145158
>>
>> Contains example code for use. The bug description contains basic =

>> instructions for how to run the examples.
>>
>> Let me know if you have any problems or need further assistance.
>>
>>
>> --Cam
>>
>
>
>



-- =

Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
Re: JSF Tools Project RC3 build+Tutorial posted.. [message #472001 is a reply to message #471999] Thu, 15 June 2006 04:05 Go to previous messageGo to next message
Cameron Bateman is currently offline Cameron BatemanFriend
Messages: 480
Registered: July 2009
Senior Member
Hi Max,

> I am trying to make it work but I get really many excpetions when using
> jsp/jsf related files in non-jsf-faceted projects so it is kinda annoying ;(

Can you be more specific about how these exceptions are being produced?
The JSF tooling is not designed to work on a non-faceted project, but you
shouldn't be getting exceptions. Can you launch a bug?

> e.g. how do i create an ISymbol impl to e.g. return from resolveVariable ?

The SymbolFactory is used to create new ISymbol instances. How are the
variables being introduced at runtime?


--Cam
Re: JSF Tools Project RC3 build+Tutorial posted.. [message #472002 is a reply to message #472000] Thu, 15 June 2006 04:20 Go to previous messageGo to next message
Cameron Bateman is currently offline Cameron BatemanFriend
Messages: 480
Registered: July 2009
Senior Member
I haven't seen that one and can't seem to re-produce. Are you using the
latest release? Can you launch a bug?

Thanks,

Cameron

Max Rydahl Andersen wrote:

> btw. it also fails within the example app there is on that bug.

> e.g. opening faces-config.xml gives me:
...
<snip>
Re: JSF Tools Project RC3 build+Tutorial posted.. [message #472004 is a reply to message #472002] Thu, 15 June 2006 17:48 Go to previous messageGo to next message
Max Rydahl Andersen is currently offline Max Rydahl AndersenFriend
Messages: 225
Registered: July 2009
Senior Member
On Thu, 15 Jun 2006 06:20:01 +0200, Cameron Bateman
<cameron.bateman@oracle.com> wrote:

> I haven't seen that one and can't seem to re-produce. Are you using the
> latest release? Can you launch a bug?

This is against the RC4 (the latest available as downloads afaik)

/max


>
> Thanks,
>
> Cameron
>
> Max Rydahl Andersen wrote:
>
>> btw. it also fails within the example app there is on that bug.
>
>> e.g. opening faces-config.xml gives me:
> ..
> <snip>
>



--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
Re: JSF Tools Project RC3 build+Tutorial posted.. [message #472672 is a reply to message #472001] Mon, 10 July 2006 10:31 Go to previous messageGo to next message
Max Rydahl Andersen is currently offline Max Rydahl AndersenFriend
Messages: 225
Registered: July 2009
Senior Member
On Thu, 15 Jun 2006 06:05:37 +0200, Cameron Bateman =

<cameron.bateman@oracle.com> wrote:

> Hi Max,
>
>> I am trying to make it work but I get really many excpetions when =

>> using jsp/jsf related files in non-jsf-faceted projects so it is kin=
da =

>> annoying ;(
>
> Can you be more specific about how these exceptions are being produced=
? =

> The JSF tooling is not designed to work on a non-faceted project, but =
=

> you shouldn't be getting exceptions. Can you launch a bug?

I've added a bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=3D150120=


>> e.g. how do i create an ISymbol impl to e.g. return from =

>> resolveVariable ?
>
> The SymbolFactory is used to create new ISymbol instances. How are th=
e =

> variables being introduced at runtime?

Via a resolver registred through a META-INF/faces-config.xml in =

jboss-seam.jar file.

How do i get to the SymbolFactory ? just statically or do I need to get =
a =

specific one?
(still, why can't i just implement the Symbol API ?)


/max
Re: JSF Tools Project RC3 build+Tutorial posted.. [message #472673 is a reply to message #472672] Mon, 10 July 2006 19:28 Go to previous messageGo to next message
Cameron Bateman is currently offline Cameron BatemanFriend
Messages: 480
Registered: July 2009
Senior Member
> I've added a bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=150120

Thanks.

>> The SymbolFactory is used to create new ISymbol instances. How are the
>> variables being introduced at runtime?

> Via a resolver registred through a META-INF/faces-config.xml in
> jboss-seam.jar file.

If you are changing the way all variables get resolved, then I suggest
using the org.eclipse.jst.jsf.designtime.variableresolver extension point
to introduce your own DTVariableResolver and then register it for each
IProject of interest using
DesignTimeApplicationManager.setVariableResolverProvider with your
extension id.

> How do i get to the SymbolFactory ? just statically or do I need to get a
> specific one?
> (still, why can't i just implement the Symbol API ?)

SymbolFactory is a public singleton in the context.symbol plugin. There
is no reason you can't create your own impls, but I recommend seeing if
there is anything you can reuse that's already there. If not, the
preferred way to create your own impl would be to create your own ecore
model that extends the base symbols one. I will be creating a tutorial on
this for the docs at some point, but can outline the steps for you if you
want. By taking this approach you can benefit from current and future
extensibility that rely on EMF. Currently this mainly means extensibility
of the content assist UI but in future could have implications for things
such as hover help and hyperlink.

--Cam
Re: JSF Tools Project RC3 build+Tutorial posted.. [message #472709 is a reply to message #472673] Mon, 17 July 2006 08:32 Go to previous messageGo to next message
Max Rydahl Andersen is currently offline Max Rydahl AndersenFriend
Messages: 225
Registered: July 2009
Senior Member
>>> The SymbolFactory is used to create new ISymbol instances. How are
>>> the variables being introduced at runtime?
>
>> Via a resolver registred through a META-INF/faces-config.xml in
>> jboss-seam.jar file.
>
> If you are changing the way all variables get resolved,

Not all, just adding some variables automatically so you don't have to
register
them constantly in faces-config.xml.

> then I suggest using the org.eclipse.jst.jsf.designtime.variableresolver
> extension point to introduce your own DTVariableResolver and then
> register it for each IProject of interest using
> DesignTimeApplicationManager.setVariableResolverProvider with your
> extension id.

mkay - i'll look into it.

>> How do i get to the SymbolFactory ? just statically or do I need to get
>> a specific one?
>> (still, why can't i just implement the Symbol API ?)
>
> SymbolFactory is a public singleton in the context.symbol plugin. There
> is no reason you can't create your own impls, but I recommend seeing if
> there is anything you can reuse that's already there. If not, the
> preferred way to create your own impl would be to create your own ecore
> model that extends the base symbols one.

I would rather not.

> I will be creating a tutorial on this for the docs at some point, but
> can outline the steps for you if you want.

....but I might have too...so if you could outline the steps it would be
nice.

> By taking this approach you can benefit from current and future
> extensibility that rely on EMF. Currently this mainly means
> extensibility of the content assist UI but in future could have
> implications for things such as hover help and hyperlink.

EMF is very big dependency for just giving extended content assist UI,
hover and hyperlink.
Anyhow, that is just my opinion ;)

/max
Re: JSF Tools Project RC3 build+Tutorial posted.. [message #472712 is a reply to message #472709] Mon, 17 July 2006 18:09 Go to previous messageGo to next message
Cameron Bateman is currently offline Cameron BatemanFriend
Messages: 480
Registered: July 2009
Senior Member
> Not all, just adding some variables automatically so you don't have to
> register them constantly in faces-config.xml.

In that case, you should be able to write your design time resolver in
much the same way you would your runtime resolver -- resolve the automatic
ones in your instance and the delegate to the abstract super-class for all
others.

>> then I suggest using the org.eclipse.jst.jsf.designtime.variableresolver
>> extension point to introduce your own DTVariableResolver and then
...
> mkay - i'll look into it.

Incidently, the developer's guide contains some docs on this including a
tutorial on contributing variables (from the component library
perspective, but it still may be helpful).

>> preferred way to create your own impl would be to create your own ecore
>> model that extends the base symbols one.
> I would rather not.

Why?

> ....but I might have too...so if you could outline the steps it would be
> nice.

There is a bug in our SDK build and the ecore is not being included. I
thought this had been resolved before release, but it has not. This will
be targeted for the 1.5.1 release. To track the status, here's the bug
number.
Here's the bug number:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=147911.

> EMF is very big dependency for just giving extended content assist UI,

I'm not sure what you mean here. EMF is already a dependency required by
both WTP and JSF for other reasons in order to operate.


--Cam
Re: JSF Tools Project RC3 build+Tutorial posted.. [message #472713 is a reply to message #472712] Fri, 21 July 2006 08:02 Go to previous messageGo to next message
Max Rydahl Andersen is currently offline Max Rydahl AndersenFriend
Messages: 225
Registered: July 2009
Senior Member
>> mkay - i'll look into it.
>
> Incidently, the developer's guide contains some docs on this including=
a =

> tutorial on contributing variables (from the component library =

> perspective, but it still may be helpful).

yes, i found those the other day.

btw. what are the criteria for the jsf-el related code completion do wor=
k ?
Is it like the faces-config.xml that it is required to be in a specific =
=

type
of facet enabled project and/or what triggers it enablement in the edito=
r ?

>>> preferred way to create your own impl would be to create your own =

>>> ecore model that extends the base symbols one.
>> I would rather not.
>
> Why?

Meet me over a beer one day and i'll tell you all about it ;)
But basically ecore is a *very* intrusive API which makes it a pain
when you want to keep your code clean and (easy!) usable in other IDE's.=


>> ....but I might have too...so if you could outline the steps it would=
=

>> be nice.
>
> There is a bug in our SDK build and the ecore is not being included. =
I =

> thought this had been resolved before release, but it has not. This =

> will be targeted for the 1.5.1 release. To track the status, here's t=
he =

> bug number.
> Here's the bug number: =

> https://bugs.eclipse.org/bugs/show_bug.cgi?id=3D147911.
>
>> EMF is very big dependency for just giving extended content assist UI=
,
>
> I'm not sure what you mean here. EMF is already a dependency required=
=

> by both WTP and JSF for other reasons in order to operate.

It is the first time I have been *forced* to have EMF exposed this hard
in some extension API.

I know it is used in the basis of many plugins, but that does not =

automatically
make it something you should put out fully exposed in the public API.

/max
Re: JSF Tools Project RC3 build+Tutorial posted.. [message #472716 is a reply to message #472713] Fri, 21 July 2006 21:31 Go to previous messageGo to next message
Cameron Bateman is currently offline Cameron BatemanFriend
Messages: 480
Registered: July 2009
Senior Member
> btw. what are the criteria for the jsf-el related code completion do work ?
> Is it like the faces-config.xml that it is required to be in a specific

This is handled automatically by the .Edit framework. For it to show up,
you need only resolve a symbol (through one of the mechanisms described in
the dev guide) that is an instance of an object who's provider implements
IContentProposalProvider. .Edit automatically finds the most specific
provider for your symbol object based on its type. This will also be true
if you extend the EMF model and implement your symbols types and providers
(there is some extension point magic required, but it's standard EMF stuff
that can be copy/pasted). This will be in my tutorial.

If you want to step through to see how it works, try this:

1) Set break points in IPropertySymbolItemProvider.getProposals and in
FunctionCompletionStrategy.getProposals at line 125 (at this point you
will have an array of either property or method symbols and you step
through how the adapter factory finds the providers and constructs the
proposals.

2) Launch a runtime workbench in debug mode.

3) In a properly created project (Dynamic Web with JSF Facet -- note that
the facet is required to find the managed bean configuration, not to
activate the symbol resolution), create a new managed bean called "foo".
Make sure whatever class "foo" corresponds to matches a resolvable Java
class with at least one implicit bean property.

4) In a JSF-JSP page, create an EL statement like this one:

<h:outputText value="#{foo}"/>

Putting a "." after foo should activate the auto-complete (or "." + hit
Ctrl-Space) and trigger your break points.


--Cam
Re: JSF Tools Project RC3 build+Tutorial posted.. [message #472718 is a reply to message #472716] Mon, 24 July 2006 10:32 Go to previous messageGo to next message
Max Rydahl Andersen is currently offline Max Rydahl AndersenFriend
Messages: 225
Registered: July 2009
Senior Member
sorry, I was apparently to vague in my question ;)

My question is more specifically:

Will jsf-el related completion work on files that is *not* inside WTP =

enable projects ?
(In my view it should be able to work there too, but eg. faces-config.xm=
l =

editing doesn't)

And another related question:
What kind of files is it enabled on ?

/max

>> btw. what are the criteria for the jsf-el related code completion do =
=

>> work ?
>> Is it like the faces-config.xml that it is required to be in a specif=
ic
>
> This is handled automatically by the .Edit framework. For it to show =
=

> up, you need only resolve a symbol (through one of the mechanisms =

> described in the dev guide) that is an instance of an object who's =

> provider implements IContentProposalProvider. .Edit automatically =

> finds the most specific provider for your symbol object based on its =

> type. This will also be true if you extend the EMF model and implemen=
t =

> your symbols types and providers (there is some extension point magic =
=

> required, but it's standard EMF stuff that can be copy/pasted). This =
=

> will be in my tutorial.
>
> If you want to step through to see how it works, try this:
>
> 1) Set break points in IPropertySymbolItemProvider.getProposals and in=
=

> FunctionCompletionStrategy.getProposals at line 125 (at this point you=
=

> will have an array of either property or method symbols and you step =

> through how the adapter factory finds the providers and constructs the=
=

> proposals.
>
> 2) Launch a runtime workbench in debug mode.
>
> 3) In a properly created project (Dynamic Web with JSF Facet -- note =

> that the facet is required to find the managed bean configuration, not=
=

> to activate the symbol resolution), create a new managed bean called =

> "foo". Make sure whatever class "foo" corresponds to matches a =

> resolvable Java class with at least one implicit bean property.
>
> 4) In a JSF-JSP page, create an EL statement like this one:
>
> <h:outputText value=3D"#{foo}"/>
>
> Putting a "." after foo should activate the auto-complete (or "." + hi=
t =

> Ctrl-Space) and trigger your break points.
>
>
> --Cam
>



-- =

Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
Re: JSF Tools Project RC3 build+Tutorial posted.. [message #472719 is a reply to message #472718] Mon, 24 July 2006 16:49 Go to previous messageGo to next message
Cameron Bateman is currently offline Cameron BatemanFriend
Messages: 480
Registered: July 2009
Senior Member
> Will jsf-el related completion work on files that is *not* inside WTP
> enable projects ?

The UI part is only designed to work in the JSP editor inside a JSF-faced
WTP project at the present time. The code that calculates the completions
code could be repurposed to activate anywhere that JFace-style completion
proposals can be contributed and there is also EL context.

There is certainly room to broaden this feature. Can you launch a bug
illustrating the use case(s) you have in mind? I can envision decoupling
the completion calculation API more fully from the UI api in 1.0 so as to
allow someone to re-use it anywhere that they have EL context.


--Cam
Re: JSF Tools Project RC3 build+Tutorial posted.. [message #472722 is a reply to message #472719] Tue, 25 July 2006 14:41 Go to previous message
Max Rydahl Andersen is currently offline Max Rydahl AndersenFriend
Messages: 225
Registered: July 2009
Senior Member
Done: https://bugs.eclipse.org/bugs/show_bug.cgi?id=3D151703


>> Will jsf-el related completion work on files that is *not* inside WTP=
=

>> enable projects ?
>
> The UI part is only designed to work in the JSP editor inside a =

> JSF-faced WTP project at the present time. The code that calculates t=
he =

> completions code could be repurposed to activate anywhere that =

> JFace-style completion proposals can be contributed and there is also =
EL =

> context.
>
> There is certainly room to broaden this feature. Can you launch a bug=
=

> illustrating the use case(s) you have in mind? I can envision =

> decoupling the completion calculation API more fully from the UI api i=
n =

> 1.0 so as to allow someone to re-use it anywhere that they have EL =

> context.
>
>
> --Cam
>
>
>
>
>



-- =

Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
Re: JSF Tools Project RC3 build+Tutorial posted.. [message #600600 is a reply to message #471985] Wed, 31 May 2006 03:12 Go to previous message
Eclipse UserFriend
Originally posted by: paul.lecky.paradisefood.com.au

Raghu Srinivasan wrote:
> Hi,
>
> We have posted a build of the JSF Tools project along with a tutorial
> that walks through the features in the build. You can access both of
> them from this page:
> http://www.eclipse.org/webtools/jsf/dev_resource/index.html
>
> The next build on June 7th will be the feature freeze build.
> Please review and post your comments, log issues.
>
> The JSF Tools project build is integrated with the WTP Continuous Builds
> and can be accessed from
> http://download.eclipse.org/webtools/committers/ However, we noticed
> errors while verifying the build and hence didn't announce its
> availability in the newsgroup. We hope to resolve this soon and we will
> then post the result of our smoke tests to the mailing list.
>
>
> Thanks
> Raghu Srinivasan
> JSF Tools Project Lead
>
Thanks for the great work Raghu. I am just starting with web
development and jsf looks to be the solution for me.
I'm looking forward to jsf coming out of incubation at the end of the month.
Re: JSF Tools Project RC3 build+Tutorial posted.. [message #600607 is a reply to message #471987] Wed, 31 May 2006 23:04 Go to previous message
Raghu Srinivasan is currently offline Raghu SrinivasanFriend
Messages: 265
Registered: July 2009
Senior Member
Hi Paul,

Thanks for taking the time to review the build. Please log issues you face
in bugzilla.
-Raghu


Raghu Srinivasan,
Project Lead - JSF
Re: JSF Tools Project RC3 build+Tutorial posted.. [message #600615 is a reply to message #471985] Thu, 01 June 2006 23:56 Go to previous message
Max Rydahl Andersen is currently offline Max Rydahl AndersenFriend
Messages: 225
Registered: July 2009
Senior Member
On Wed, 31 May 2006 02:37:10 +0200, Raghu Srinivasan
<raghunathan.srinivasan@oracle.com> wrote:

does this release/build contain any support for pluggable name resolver ?

/max

> Hi,
>
> We have posted a build of the JSF Tools project along with a tutorial
> that walks through the features in the build. You can access both of
> them from this page:
> http://www.eclipse.org/webtools/jsf/dev_resource/index.html
>
> The next build on June 7th will be the feature freeze build. Please
> review and post your comments, log issues.
>
> The JSF Tools project build is integrated with the WTP Continuous Builds
> and can be accessed from
> http://download.eclipse.org/webtools/committers/ However, we noticed
> errors while verifying the build and hence didn't announce its
> availability in the newsgroup. We hope to resolve this soon and we will
> then post the result of our smoke tests to the mailing list.
>
>
> Thanks
> Raghu Srinivasan
> JSF Tools Project Lead
>



--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
Re: JSF Tools Project RC3 build+Tutorial posted.. [message #600626 is a reply to message #471989] Fri, 02 June 2006 18:04 Go to previous message
Raghu Srinivasan is currently offline Raghu SrinivasanFriend
Messages: 265
Registered: July 2009
Senior Member
Hi Max,

Pluggable name resolver will be available in the June 7th feature-freeze
drop.
Thanks
Raghu


Raghu Srinivasan,
Project Lead - JSF
Re: JSF Tools Project RC3 build+Tutorial posted.. [message #600645 is a reply to message #471989] Thu, 08 June 2006 16:56 Go to previous message
Cameron Bateman is currently offline Cameron BatemanFriend
Messages: 480
Registered: July 2009
Senior Member
Hi Max,

The pluggable resolver code is checked into CVS in should appear in the
weekly I-build on Friday.

The bug:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=145158

Contains example code for use. The bug description contains basic
instructions for how to run the examples.

Let me know if you have any problems or need further assistance.


--Cam
Re: JSF Tools Project RC3 build+Tutorial posted.. [message #600685 is a reply to message #471992] Thu, 15 June 2006 01:38 Go to previous message
Max Rydahl Andersen is currently offline Max Rydahl AndersenFriend
Messages: 225
Registered: July 2009
Senior Member
Hi,

I finally discovered your answer here ;)

I am trying to make it work but I get really many excpetions when using =
=

jsp/jsf related
files in non-jsf-faceted projects so it is kinda annoying ;(

but anyhow it looks like the functionallity is in there, but I must say =
I =

don't like
that all the symbol api requires things to extend EObject.

e.g. how do i create an ISymbol impl to e.g. return from resolveVariable=
?

/max

> Hi Max,
>
> The pluggable resolver code is checked into CVS in should appear in th=
e =

> weekly I-build on Friday.
>
> The bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=3D145158
>
> Contains example code for use. The bug description contains basic =

> instructions for how to run the examples.
>
> Let me know if you have any problems or need further assistance.
>
>
> --Cam
>



-- =

Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
Re: JSF Tools Project RC3 build+Tutorial posted.. [message #600691 is a reply to message #471999] Thu, 15 June 2006 01:43 Go to previous message
Max Rydahl Andersen is currently offline Max Rydahl AndersenFriend
Messages: 225
Registered: July 2009
Senior Member
btw. it also fails within the example app there is on that bug.

e.g. opening faces-config.xml gives me:

java.lang.IllegalArgumentException: Path must include project and resour=
ce =

name: /DTResolverExampleApp
at org.eclipse.core.runtime.Assert.isLegal(Assert.java:62)
at =

org.eclipse.core.internal.resources.Workspace.newResource(Wo rkspace.java=
:1565)
at =

org.eclipse.core.internal.resources.Container.getFolder(Cont ainer.java:1=
37)
at =

org.eclipse.jst.jsf.facesconfig.common.utils.WebrootUtil.get WebContentFo=
lder(WebrootUtil.java:79)
at =

org.eclipse.jst.jsf.facesconfig.ui.FacesConfigEditor.loadMod el(FacesConf=
igEditor.java:333)
at =

org.eclipse.jst.jsf.facesconfig.ui.FacesConfigEditor.setInpu t(FacesConfi=
gEditor.java:323)
at org.eclipse.ui.forms.editor.FormEditor.init(FormEditor.java: 132)
at =

org.eclipse.jst.jsf.facesconfig.ui.FacesConfigEditor.init(Fa cesConfigEdi=
tor.java:296)
at =

org.eclipse.ui.internal.EditorManager.createSite(EditorManag er.java:839)=



and when opening any other faces-config.xml:

org.eclipse.core.runtime.AssertionFailedException: assertion failed:
at org.eclipse.core.runtime.Assert.isTrue(Assert.java:109)
at org.eclipse.core.runtime.Assert.isTrue(Assert.java:95)
at =

org.eclipse.jst.jsf.facesconfig.ui.FacesConfigEditor.loadMod el(FacesConf=
igEditor.java:334)
at =

org.eclipse.jst.jsf.facesconfig.ui.FacesConfigEditor.setInpu t(FacesConfi=
gEditor.java:323)
at org.eclipse.ui.forms.editor.FormEditor.init(FormEditor.java: 132)
at =

org.eclipse.jst.jsf.facesconfig.ui.FacesConfigEditor.init(Fa cesConfigEdi=
tor.java:296)
at =

org.eclipse.ui.internal.EditorManager.createSite(EditorManag er.java:839)=

at =

org.eclipse.ui.internal.EditorReference.createPartHelper(Edi torReference=
..java:583)
at =

org.eclipse.ui.internal.EditorReference.createPart(EditorRef erence.java:=
372)
at =

org.eclipse.ui.internal.WorkbenchPartReference.getPart(Workb enchPartRefe=
rence.java:566)
at =

org.eclipse.ui.internal.EditorReference.getEditor(EditorRefe rence.java:2=
14)
at =

org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched( WorkbenchPag=
e.java:2588)
at =

org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(Workben chPage.java:=
2521)
at =

org.eclipse.ui.internal.WorkbenchPage.access$10(WorkbenchPag e.java:2513)=

at org.eclipse.ui.internal.WorkbenchPage$9.run(WorkbenchPage.ja va:2498)=

at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator .java:67=
)
=


/max



> Hi,
>
> I finally discovered your answer here ;)
>
> I am trying to make it work but I get really many excpetions when usin=
g =

> jsp/jsf related
> files in non-jsf-faceted projects so it is kinda annoying ;(
>
> but anyhow it looks like the functionallity is in there, but I must sa=
y =

> I don't like
> that all the symbol api requires things to extend EObject.
>
> e.g. how do i create an ISymbol impl to e.g. return from resolveVariab=
le =

> ?
>
> /max
>
>> Hi Max,
>>
>> The pluggable resolver code is checked into CVS in should appear in t=
he =

>> weekly I-build on Friday.
>>
>> The bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=3D145158
>>
>> Contains example code for use. The bug description contains basic =

>> instructions for how to run the examples.
>>
>> Let me know if you have any problems or need further assistance.
>>
>>
>> --Cam
>>
>
>
>



-- =

Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
Re: JSF Tools Project RC3 build+Tutorial posted.. [message #600697 is a reply to message #471999] Thu, 15 June 2006 04:05 Go to previous message
Cameron Bateman is currently offline Cameron BatemanFriend
Messages: 480
Registered: July 2009
Senior Member
Hi Max,

> I am trying to make it work but I get really many excpetions when using
> jsp/jsf related files in non-jsf-faceted projects so it is kinda annoying ;(

Can you be more specific about how these exceptions are being produced?
The JSF tooling is not designed to work on a non-faceted project, but you
shouldn't be getting exceptions. Can you launch a bug?

> e.g. how do i create an ISymbol impl to e.g. return from resolveVariable ?

The SymbolFactory is used to create new ISymbol instances. How are the
variables being introduced at runtime?


--Cam
Re: JSF Tools Project RC3 build+Tutorial posted.. [message #600701 is a reply to message #472000] Thu, 15 June 2006 04:20 Go to previous message
Cameron Bateman is currently offline Cameron BatemanFriend
Messages: 480
Registered: July 2009
Senior Member
I haven't seen that one and can't seem to re-produce. Are you using the
latest release? Can you launch a bug?

Thanks,

Cameron

Max Rydahl Andersen wrote:

> btw. it also fails within the example app there is on that bug.

> e.g. opening faces-config.xml gives me:
...
<snip>
Re: JSF Tools Project RC3 build+Tutorial posted.. [message #600712 is a reply to message #472002] Thu, 15 June 2006 17:48 Go to previous message
Max Rydahl Andersen is currently offline Max Rydahl AndersenFriend
Messages: 225
Registered: July 2009
Senior Member
On Thu, 15 Jun 2006 06:20:01 +0200, Cameron Bateman
<cameron.bateman@oracle.com> wrote:

> I haven't seen that one and can't seem to re-produce. Are you using the
> latest release? Can you launch a bug?

This is against the RC4 (the latest available as downloads afaik)

/max


>
> Thanks,
>
> Cameron
>
> Max Rydahl Andersen wrote:
>
>> btw. it also fails within the example app there is on that bug.
>
>> e.g. opening faces-config.xml gives me:
> ..
> <snip>
>



--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
Re: JSF Tools Project RC3 build+Tutorial posted.. [message #603429 is a reply to message #472001] Mon, 10 July 2006 10:31 Go to previous message
Max Rydahl Andersen is currently offline Max Rydahl AndersenFriend
Messages: 225
Registered: July 2009
Senior Member
On Thu, 15 Jun 2006 06:05:37 +0200, Cameron Bateman =

<cameron.bateman@oracle.com> wrote:

> Hi Max,
>
>> I am trying to make it work but I get really many excpetions when =

>> using jsp/jsf related files in non-jsf-faceted projects so it is kin=
da =

>> annoying ;(
>
> Can you be more specific about how these exceptions are being produced=
? =

> The JSF tooling is not designed to work on a non-faceted project, but =
=

> you shouldn't be getting exceptions. Can you launch a bug?

I've added a bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=3D150120=


>> e.g. how do i create an ISymbol impl to e.g. return from =

>> resolveVariable ?
>
> The SymbolFactory is used to create new ISymbol instances. How are th=
e =

> variables being introduced at runtime?

Via a resolver registred through a META-INF/faces-config.xml in =

jboss-seam.jar file.

How do i get to the SymbolFactory ? just statically or do I need to get =
a =

specific one?
(still, why can't i just implement the Symbol API ?)


/max
Re: JSF Tools Project RC3 build+Tutorial posted.. [message #603433 is a reply to message #472672] Mon, 10 July 2006 19:28 Go to previous message
Cameron Bateman is currently offline Cameron BatemanFriend
Messages: 480
Registered: July 2009
Senior Member
> I've added a bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=150120

Thanks.

>> The SymbolFactory is used to create new ISymbol instances. How are the
>> variables being introduced at runtime?

> Via a resolver registred through a META-INF/faces-config.xml in
> jboss-seam.jar file.

If you are changing the way all variables get resolved, then I suggest
using the org.eclipse.jst.jsf.designtime.variableresolver extension point
to introduce your own DTVariableResolver and then register it for each
IProject of interest using
DesignTimeApplicationManager.setVariableResolverProvider with your
extension id.

> How do i get to the SymbolFactory ? just statically or do I need to get a
> specific one?
> (still, why can't i just implement the Symbol API ?)

SymbolFactory is a public singleton in the context.symbol plugin. There
is no reason you can't create your own impls, but I recommend seeing if
there is anything you can reuse that's already there. If not, the
preferred way to create your own impl would be to create your own ecore
model that extends the base symbols one. I will be creating a tutorial on
this for the docs at some point, but can outline the steps for you if you
want. By taking this approach you can benefit from current and future
extensibility that rely on EMF. Currently this mainly means extensibility
of the content assist UI but in future could have implications for things
such as hover help and hyperlink.

--Cam
Re: JSF Tools Project RC3 build+Tutorial posted.. [message #604598 is a reply to message #472673] Mon, 17 July 2006 08:32 Go to previous message
Max Rydahl Andersen is currently offline Max Rydahl AndersenFriend
Messages: 225
Registered: July 2009
Senior Member
>>> The SymbolFactory is used to create new ISymbol instances. How are
>>> the variables being introduced at runtime?
>
>> Via a resolver registred through a META-INF/faces-config.xml in
>> jboss-seam.jar file.
>
> If you are changing the way all variables get resolved,

Not all, just adding some variables automatically so you don't have to
register
them constantly in faces-config.xml.

> then I suggest using the org.eclipse.jst.jsf.designtime.variableresolver
> extension point to introduce your own DTVariableResolver and then
> register it for each IProject of interest using
> DesignTimeApplicationManager.setVariableResolverProvider with your
> extension id.

mkay - i'll look into it.

>> How do i get to the SymbolFactory ? just statically or do I need to get
>> a specific one?
>> (still, why can't i just implement the Symbol API ?)
>
> SymbolFactory is a public singleton in the context.symbol plugin. There
> is no reason you can't create your own impls, but I recommend seeing if
> there is anything you can reuse that's already there. If not, the
> preferred way to create your own impl would be to create your own ecore
> model that extends the base symbols one.

I would rather not.

> I will be creating a tutorial on this for the docs at some point, but
> can outline the steps for you if you want.

....but I might have too...so if you could outline the steps it would be
nice.

> By taking this approach you can benefit from current and future
> extensibility that rely on EMF. Currently this mainly means
> extensibility of the content assist UI but in future could have
> implications for things such as hover help and hyperlink.

EMF is very big dependency for just giving extended content assist UI,
hover and hyperlink.
Anyhow, that is just my opinion ;)

/max
Re: JSF Tools Project RC3 build+Tutorial posted.. [message #604602 is a reply to message #472709] Mon, 17 July 2006 18:09 Go to previous message
Cameron Bateman is currently offline Cameron BatemanFriend
Messages: 480
Registered: July 2009
Senior Member
> Not all, just adding some variables automatically so you don't have to
> register them constantly in faces-config.xml.

In that case, you should be able to write your design time resolver in
much the same way you would your runtime resolver -- resolve the automatic
ones in your instance and the delegate to the abstract super-class for all
others.

>> then I suggest using the org.eclipse.jst.jsf.designtime.variableresolver
>> extension point to introduce your own DTVariableResolver and then
...
> mkay - i'll look into it.

Incidently, the developer's guide contains some docs on this including a
tutorial on contributing variables (from the component library
perspective, but it still may be helpful).

>> preferred way to create your own impl would be to create your own ecore
>> model that extends the base symbols one.
> I would rather not.

Why?

> ....but I might have too...so if you could outline the steps it would be
> nice.

There is a bug in our SDK build and the ecore is not being included. I
thought this had been resolved before release, but it has not. This will
be targeted for the 1.5.1 release. To track the status, here's the bug
number.
Here's the bug number:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=147911

> EMF is very big dependency for just giving extended content assist UI,

I'm not sure what you mean here. EMF is already a dependency required by
both WTP and JSF for other reasons in order to operate.


--Cam
Re: JSF Tools Project RC3 build+Tutorial posted.. [message #604606 is a reply to message #472712] Fri, 21 July 2006 08:02 Go to previous message
Max Rydahl Andersen is currently offline Max Rydahl AndersenFriend
Messages: 225
Registered: July 2009
Senior Member
>> mkay - i'll look into it.
>
> Incidently, the developer's guide contains some docs on this including=
a =

> tutorial on contributing variables (from the component library =

> perspective, but it still may be helpful).

yes, i found those the other day.

btw. what are the criteria for the jsf-el related code completion do wor=
k ?
Is it like the faces-config.xml that it is required to be in a specific =
=

type
of facet enabled project and/or what triggers it enablement in the edito=
r ?

>>> preferred way to create your own impl would be to create your own =

>>> ecore model that extends the base symbols one.
>> I would rather not.
>
> Why?

Meet me over a beer one day and i'll tell you all about it ;)
But basically ecore is a *very* intrusive API which makes it a pain
when you want to keep your code clean and (easy!) usable in other IDE's.=


>> ....but I might have too...so if you could outline the steps it would=
=

>> be nice.
>
> There is a bug in our SDK build and the ecore is not being included. =
I =

> thought this had been resolved before release, but it has not. This =

> will be targeted for the 1.5.1 release. To track the status, here's t=
he =

> bug number.
> Here's the bug number: =

> https://bugs.eclipse.org/bugs/show_bug.cgi?id=3D147911
>
>> EMF is very big dependency for just giving extended content assist UI=
,
>
> I'm not sure what you mean here. EMF is already a dependency required=
=

> by both WTP and JSF for other reasons in order to operate.

It is the first time I have been *forced* to have EMF exposed this hard
in some extension API.

I know it is used in the basis of many plugins, but that does not =

automatically
make it something you should put out fully exposed in the public API.

/max
Re: JSF Tools Project RC3 build+Tutorial posted.. [message #604610 is a reply to message #472713] Fri, 21 July 2006 21:31 Go to previous message
Cameron Bateman is currently offline Cameron BatemanFriend
Messages: 480
Registered: July 2009
Senior Member
> btw. what are the criteria for the jsf-el related code completion do work ?
> Is it like the faces-config.xml that it is required to be in a specific

This is handled automatically by the .Edit framework. For it to show up,
you need only resolve a symbol (through one of the mechanisms described in
the dev guide) that is an instance of an object who's provider implements
IContentProposalProvider. .Edit automatically finds the most specific
provider for your symbol object based on its type. This will also be true
if you extend the EMF model and implement your symbols types and providers
(there is some extension point magic required, but it's standard EMF stuff
that can be copy/pasted). This will be in my tutorial.

If you want to step through to see how it works, try this:

1) Set break points in IPropertySymbolItemProvider.getProposals and in
FunctionCompletionStrategy.getProposals at line 125 (at this point you
will have an array of either property or method symbols and you step
through how the adapter factory finds the providers and constructs the
proposals.

2) Launch a runtime workbench in debug mode.

3) In a properly created project (Dynamic Web with JSF Facet -- note that
the facet is required to find the managed bean configuration, not to
activate the symbol resolution), create a new managed bean called "foo".
Make sure whatever class "foo" corresponds to matches a resolvable Java
class with at least one implicit bean property.

4) In a JSF-JSP page, create an EL statement like this one:

<h:outputText value="#{foo}"/>

Putting a "." after foo should activate the auto-complete (or "." + hit
Ctrl-Space) and trigger your break points.


--Cam
Re: JSF Tools Project RC3 build+Tutorial posted.. [message #604614 is a reply to message #472716] Mon, 24 July 2006 10:32 Go to previous message
Max Rydahl Andersen is currently offline Max Rydahl AndersenFriend
Messages: 225
Registered: July 2009
Senior Member
sorry, I was apparently to vague in my question ;)

My question is more specifically:

Will jsf-el related completion work on files that is *not* inside WTP =

enable projects ?
(In my view it should be able to work there too, but eg. faces-config.xm=
l =

editing doesn't)

And another related question:
What kind of files is it enabled on ?

/max

>> btw. what are the criteria for the jsf-el related code completion do =
=

>> work ?
>> Is it like the faces-config.xml that it is required to be in a specif=
ic
>
> This is handled automatically by the .Edit framework. For it to show =
=

> up, you need only resolve a symbol (through one of the mechanisms =

> described in the dev guide) that is an instance of an object who's =

> provider implements IContentProposalProvider. .Edit automatically =

> finds the most specific provider for your symbol object based on its =

> type. This will also be true if you extend the EMF model and implemen=
t =

> your symbols types and providers (there is some extension point magic =
=

> required, but it's standard EMF stuff that can be copy/pasted). This =
=

> will be in my tutorial.
>
> If you want to step through to see how it works, try this:
>
> 1) Set break points in IPropertySymbolItemProvider.getProposals and in=
=

> FunctionCompletionStrategy.getProposals at line 125 (at this point you=
=

> will have an array of either property or method symbols and you step =

> through how the adapter factory finds the providers and constructs the=
=

> proposals.
>
> 2) Launch a runtime workbench in debug mode.
>
> 3) In a properly created project (Dynamic Web with JSF Facet -- note =

> that the facet is required to find the managed bean configuration, not=
=

> to activate the symbol resolution), create a new managed bean called =

> "foo". Make sure whatever class "foo" corresponds to matches a =

> resolvable Java class with at least one implicit bean property.
>
> 4) In a JSF-JSP page, create an EL statement like this one:
>
> <h:outputText value=3D"#{foo}"/>
>
> Putting a "." after foo should activate the auto-complete (or "." + hi=
t =

> Ctrl-Space) and trigger your break points.
>
>
> --Cam
>



-- =

Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
Re: JSF Tools Project RC3 build+Tutorial posted.. [message #604619 is a reply to message #472718] Mon, 24 July 2006 16:49 Go to previous message
Cameron Bateman is currently offline Cameron BatemanFriend
Messages: 480
Registered: July 2009
Senior Member
> Will jsf-el related completion work on files that is *not* inside WTP
> enable projects ?

The UI part is only designed to work in the JSP editor inside a JSF-faced
WTP project at the present time. The code that calculates the completions
code could be repurposed to activate anywhere that JFace-style completion
proposals can be contributed and there is also EL context.

There is certainly room to broaden this feature. Can you launch a bug
illustrating the use case(s) you have in mind? I can envision decoupling
the completion calculation API more fully from the UI api in 1.0 so as to
allow someone to re-use it anywhere that they have EL context.


--Cam
Re: JSF Tools Project RC3 build+Tutorial posted.. [message #604622 is a reply to message #472719] Tue, 25 July 2006 14:41 Go to previous message
Max Rydahl Andersen is currently offline Max Rydahl AndersenFriend
Messages: 225
Registered: July 2009
Senior Member
Done: https://bugs.eclipse.org/bugs/show_bug.cgi?id=3D151703


>> Will jsf-el related completion work on files that is *not* inside WTP=
=

>> enable projects ?
>
> The UI part is only designed to work in the JSP editor inside a =

> JSF-faced WTP project at the present time. The code that calculates t=
he =

> completions code could be repurposed to activate anywhere that =

> JFace-style completion proposals can be contributed and there is also =
EL =

> context.
>
> There is certainly room to broaden this feature. Can you launch a bug=
=

> illustrating the use case(s) you have in mind? I can envision =

> decoupling the completion calculation API more fully from the UI api i=
n =

> 1.0 so as to allow someone to re-use it anywhere that they have EL =

> context.
>
>
> --Cam
>
>
>
>
>



-- =

Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
Previous Topic:JSF Plugin and MyFaces
Next Topic:Tag Libraries ICONs
Goto Forum:
  


Current Time: Mon Nov 24 03:00:36 GMT 2014

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

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