Eclipse Community Forums: JavaServer Faces » 2.0M6 JSF Content Assist issues

Help

Home

Home » Eclipse Projects » JavaServer Faces » 2.0M6 JSF Content Assist issues

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

2.0M6 JSF Content Assist issues [message #474142]

Tue, 10 April 2007 20:17

Anil Kommareddi

Messages: 9
Registered: July 2009

Junior Member

Hi,
I am using Eclipse 3.3M6 with WTP2.0M6. It appears that Content assist is
broken in the default JSP Editor. I see several issues and I hope it is
just my configuration that is broken.

My page looks like this (pl ignore any typos, it works when deployed):
------------
<?xml version="1.0" encoding="ISO-8859-1" ?>
<jsp:root
xmlns:ui="http://java.sun.com/jsf/facelets"
xmlns:f="http://java.sun.com/jsf/core"
xmlns:a4j="https://ajax4jsf.dev.java.net/ajax"
xmlns:h="http://java.sun.com/jsf/html"
xmlns:t="http://myfaces.apache.org/tomahawk"
version="2.0">

<ui:composition template="/internal/layout/layout.xhtml">
<html xmlns="http://www.w3.org/1999/xhtml">
<ui:define name="title">Test</ui:define>
<ui:define name="content">
<a4j:form id="testform">
<h:messages />
<h:inputText id="test" value="#{testBean.test}">
<h:commandButton id="btnAction" value="Submit"
action="#{testBean.action}"/>
</a4j:form>
</ui:define>
</html>
</ui:composition>
</jsp:root>
-----------------------

1. The "JSP Expression" assist is shown for MyFaces/Tomahawk/Ajax4JSF
libraries, nothing more. The tags seem to be recognized because there is
no red underline.

2. Facelets tags are not recognized at all, they are flagged with an error
"taglib directive for "ui" does not exist or TLD is not found". I have
tried extracting the tld and dropping it in the web-inf/lib, but it did
not help. I tried dropping it into a directory and setting the build path
to point to that directory, that did not help either.

3. Custom tag libs - same as Facelets tags.

#1 above works using the Amateras Faces IDE's JSP Editor - ie I can get
the content assist for MyFaces/Tomahawk/Ajax4JSF, but not Facelets or
Custom tags.

I have tried removing all my plugins completely and using just the
Platform with WTP and its pre-requisites. I started with a fresh
workspace, fresh dynamic web project with JSF facet, but it is the same
issue. I do not know what else to try. I have seen people mentioning
Facelets content assist works with Eclipse, but searching the newsgroups
yielded no clues.

Any help would be very much appreciated.

Thanks - Anil.

Report message to a moderator

Re: 2.0M6 JSF Content Assist issues [message #474147 is a reply to message #474142]

Wed, 11 April 2007 18:29

Cameron Bateman

Messages: 481
Registered: July 2009

Senior Member

There is indeed some strange behavior here, but let's just clarify a few
issues:

1) JSF Tooling currently does not guarantee facelet support. We have had
requests in this area though and they are under consideration. If you
have specific requirements in this area, the best thing to do is launch
bugs against the JSF Tooling project specify the support that you need.

2) There are two types of content-assist from JSF's perspective: static
value assist and EL assist. Static value assist works on tag attributes
that have literal values. For example, if you add a "layout" attribute to
the messages component in your example, you should see "list" and "table"
in the drop down list. EL support activates when you're inside the #{}
braces, such as on your action attribute for the command button.

When I tried this the first time, both these assists worked okay once I
fixed the syntax error in your example (the missing closing brace on the
inputText). However, the attribute assist on the tags did not recover.
This is a JSP editor issue; we don't control the assists for what
attributes are available for. The second time it recovered much better.
Try fixing syntax errors and then closing and re-opening the editor.

3) We don't support static assists for component libraries other than "f"
and "h". However, we do provide a meta-data framework so that component
library developers can contribute their own meta-data to add such support.
So you will not see any static content-assist support on your ajax, ui or
tomahawk tag libraries unless someone has added support for them.

--Cam

Anil Kommareddi wrote:

> Hi,
> I am using Eclipse 3.3M6 with WTP2.0M6. It appears that Content assist is
> broken in the default JSP Editor. I see several issues and I hope it is
> just my configuration that is broken.

> My page looks like this (pl ignore any typos, it works when deployed):
> ------------
> <?xml version="1.0" encoding="ISO-8859-1" ?>
> <jsp:root
> xmlns:ui="http://java.sun.com/jsf/facelets"
> xmlns:f="http://java.sun.com/jsf/core"
> xmlns:a4j="https://ajax4jsf.dev.java.net/ajax"
> xmlns:h="http://java.sun.com/jsf/html"
> xmlns:t="http://myfaces.apache.org/tomahawk"
> version="2.0">

> <ui:composition template="/internal/layout/layout.xhtml">
> <html xmlns="http://www.w3.org/1999/xhtml">
> <ui:define name="title">Test</ui:define>
> <ui:define name="content">
> <a4j:form id="testform">
> <h:messages />
> <h:inputText id="test" value="#{testBean.test}">
> <h:commandButton id="btnAction" value="Submit"
> action="#{testBean.action}"/>
> </a4j:form>
> </ui:define>
> </html>
> </ui:composition>
> </jsp:root>
> -----------------------

> 1. The "JSP Expression" assist is shown for MyFaces/Tomahawk/Ajax4JSF
> libraries, nothing more. The tags seem to be recognized because there is
> no red underline.

> 2. Facelets tags are not recognized at all, they are flagged with an error
> "taglib directive for "ui" does not exist or TLD is not found". I have
> tried extracting the tld and dropping it in the web-inf/lib, but it did
> not help. I tried dropping it into a directory and setting the build path
> to point to that directory, that did not help either.

> 3. Custom tag libs - same as Facelets tags.

> #1 above works using the Amateras Faces IDE's JSP Editor - ie I can get
> the content assist for MyFaces/Tomahawk/Ajax4JSF, but not Facelets or
> Custom tags.

> I have tried removing all my plugins completely and using just the
> Platform with WTP and its pre-requisites. I started with a fresh
> workspace, fresh dynamic web project with JSF facet, but it is the same
> issue. I do not know what else to try. I have seen people mentioning
> Facelets content assist works with Eclipse, but searching the newsgroups
> yielded no clues.

> Any help would be very much appreciated.

> Thanks - Anil.

Report message to a moderator

Re: 2.0M6 JSF Content Assist issues [message #474151 is a reply to message #474147]

Mon, 16 April 2007 00:26

Anil Kommareddi

Messages: 9
Registered: July 2009

Junior Member

Cam,
Thanks for the response. The example I posted was a copy/paste with =

irrelevant stuff deleted, hence the syntax error. I cannot get either th=
e =

static value assist (f and h too) or the EL assist in the default JSP =

editor. The static value assist does not give any error. The EL assist =

throws an ArrayStoreException. Pasted the trace below.

I have another user here trying out the latest milestone and he sees the=
=

same issue. The assists work fine in the previous milestone. I guess I =

should post this in the webtools forum.

eclipse.buildId=3DI20070323-1616
java.version=3D1.5.0_09
java.vendor=3DSun Microsystems Inc.
BootLoader constants: OS=3Dwin32, ARCH=3Dx86, WS=3Dwin32, NL=3Den_US
Framework arguments: -startup =

C:\tools\eclipse_home\3.3M6\eclipse\plugins\org.eclipse.equi nox.launcher=
_1.0.0.v20070319.jar
Command-line arguments: -os win32 -ws win32 -arch x86 -startup =

C:\tools\eclipse_home\3.3M6\eclipse\plugins\org.eclipse.equi nox.launcher=
_1.0.0.v20070319.jar

java.lang.ArrayStoreException
at org.eclipse.emf.common.util.BasicEList.assign(BasicEList.jav a:191)
at org.eclipse.emf.common.util.BasicEList.addUnique(BasicEList. java:645=
)
at =

org.eclipse.emf.common.notify.impl.NotifyingListImpl.doAddUn ique(Notifyi=
ngListImpl.java:331)
at =

org.eclipse.emf.common.notify.impl.NotifyingListImpl.addUniq ue(Notifying=
ListImpl.java:315)
at org.eclipse.emf.common.util.BasicEList.add(BasicEList.java:6 26)
at =

org.eclipse.wst.common.internal.emf.utilities.ExtendedEcoreU til.eSetOrAd=
d(ExtendedEcoreUtil.java:75)
at =

org.eclipse.wst.common.internal.emf.resource.Translator.setM OFValue(Tran=
slator.java:605)
at =

org.eclipse.wst.common.internal.emf.resource.Translator.setM OFValue(Tran=
slator.java:620)
at =

org.eclipse.wst.common.internal.emf.resource.Translator.setM OFValue(Tran=
slator.java:611)
at =

org.eclipse.wst.common.internal.emf.resource.Translator.setT extValueIfNe=
cessary(Translator.java:453)
at =

org.eclipse.wst.common.internal.emf.resource.CacheEventNode. commit(Cache=
EventNode.java:231)
at =

org.eclipse.wst.common.internal.emf.resource.EMF2SAXDocument Handler.endE=
lement(EMF2SAXDocumentHandler.java:115)
at =

com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser .endElement(=
AbstractSAXParser.java:633)
at =

com.sun.org.apache.xerces.internal.impl.dtd.XMLNSDTDValidato r.endNamespa=
ceScope(XMLNSDTDValidator.java:260)
at =

com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator. handleEndEle=
ment(XMLDTDValidator.java:2059)
at =

com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator. endElement(X=
MLDTDValidator.java:932)
at =

com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScanner Impl.scanEnd=
Element(XMLNSDocumentScannerImpl.java:719)
at =

com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentS cannerImpl$F=
ragmentContentDispatcher.dispatch(XMLDocumentFragmentScanner Impl.java:16=
85)
at =

com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentS cannerImpl.s=
canDocument(XMLDocumentFragmentScannerImpl.java:368)
at =

com.sun.org.apache.xerces.internal.parsers.XML11Configuratio n.parse(XML1=
1Configuration.java:834)
at =

com.sun.org.apache.xerces.internal.parsers.XML11Configuratio n.parse(XML1=
1Configuration.java:764)
at =

com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(X MLParser.jav=
a:148)
at =

com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser .parse(Abstr=
actSAXParser.java:1242)
at =

org.eclipse.wst.common.internal.emf.resource.EMF2SAXRenderer .doLoad(EMF2=
SAXRenderer.java:93)
at =

org.eclipse.wst.common.internal.emf.resource.TranslatorResou rceImpl.basi=
cDoLoad(TranslatorResourceImpl.java:142)
at =

org.eclipse.wst.common.internal.emf.resource.CompatibilityXM IResourceImp=
l.doLoad(CompatibilityXMIResourceImpl.java:173)
at =

org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(Resour ceImpl.java:=
1354)
at =

org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(Resour ceImpl.java:=
1155)
at =

org.eclipse.wst.common.internal.emf.resource.CompatibilityXM IResourceImp=
l.load(CompatibilityXMIResourceImpl.java:259)
at =

org.eclipse.wst.common.internal.emf.resource.TranslatorResou rceImpl.load=
(TranslatorResourceImpl.java:388)
at =

org.eclipse.jst.jsf.core.internal.provisional.jsfappconfig.J ARFileJSFApp=
ConfigProvider.getFacesConfigModel(JARFileJSFAppConfigProvid er.java:87)
at =

org.eclipse.jst.jsf.core.internal.provisional.jsfappconfig.J SFAppConfigM=
anager.getFacesConfigModels(JSFAppConfigManager.java:404)
at =

org.eclipse.jst.jsf.core.internal.provisional.jsfappconfig.J SFAppConfigM=
anager.getManagedBeans(JSFAppConfigManager.java:439)
at =

org.eclipse.jst.jsf.designtime.internal.provisional.symbols. DefaultBeanS=
ymbolSourceProvider.getManagedBeanSymbols(DefaultBeanSymbolS ourceProvide=
r.java:124)
at =

org.eclipse.jst.jsf.designtime.internal.provisional.symbols. DefaultBeanS=
ymbolSourceProvider.getSymbols(DefaultBeanSymbolSourceProvid er.java:82)
at =

org.eclipse.jst.jsf.designtime.internal.provisional.symbols. DefaultBeanS=
ymbolSourceProvider.getSymbol(DefaultBeanSymbolSourceProvide r.java:99)
at =

org.eclipse.jst.jsf.designtime.internal.provisional.el.Defau ltDTVariable=
Resolver.resolveVariable(DefaultDTVariableResolver.java:86)
at =

org.eclipse.jst.jsf.designtime.internal.provisional.resolver .SymbolConte=
xtResolver.getVariable(SymbolContextResolver.java:55)
at =

org.eclipse.jst.jsf.core.internal.contentassist.el.FunctionC ompletionStr=
ategy.getProposals(FunctionCompletionStrategy.java:86)
at =

org.eclipse.jst.jsf.ui.internal.contentassist.el.JSFELConten tAssistProce=
ssor.computeCompletionProposals(JSFELContentAssistProcessor. java:103)
at =

org.eclipse.wst.sse.ui.internal.contentassist.CompoundConten tAssistProce=
ssor.computeCompletionProposals(CompoundContentAssistProcess or.java:290)=

at =

org.eclipse.jface.text.contentassist.ContentAssistant.comput eCompletionP=
roposals(ContentAssistant.java:1758)
at =

org.eclipse.jface.text.contentassist.CompletionProposalPopup .computeProp=
osals(CompletionProposalPopup.java:478)
at =

org.eclipse.jface.text.contentassist.CompletionProposalPopup .access$16(C=
ompletionProposalPopup.java:475)
at =

org.eclipse.jface.text.contentassist.CompletionProposalPopup $2.run(Compl=
etionProposalPopup.java:410)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator .java:67=
)
at =

org.eclipse.jface.text.contentassist.CompletionProposalPopup .showProposa=
ls(CompletionProposalPopup.java:404)
at =

org.eclipse.jface.text.contentassist.ContentAssistant.showPo ssibleComple=
tions(ContentAssistant.java:1587)
at =

org.eclipse.wst.sse.ui.internal.StructuredTextViewer.doOpera tion(Structu=
redTextViewer.java:376)
at =

org.eclipse.ui.texteditor.TextOperationAction$1.run(TextOper ationAction.=
java:131)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator .java:67=
)
at =

org.eclipse.ui.texteditor.TextOperationAction.run(TextOperat ionAction.ja=
va:129)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498 )
at org.eclipse.ui.commands.ActionHandler.execute(ActionHandler. java:185=
)
at =

org.eclipse.ui.internal.handlers.LegacyHandlerWrapper.execut e(LegacyHand=
lerWrapper.java:109)
at org.eclipse.core.commands.Command.executeWithChecks(Command. java:471=
)
at =

org.eclipse.core.commands.ParameterizedCommand.executeWithCh ecks(Paramet=
erizedCommand.java:424)
at =

org.eclipse.ui.internal.handlers.HandlerService.executeComma nd(HandlerSe=
rvice.java:164)
at =

org.eclipse.ui.internal.keys.WorkbenchKeyboard.executeComman d(WorkbenchK=
eyboard.java:467)
at =

org.eclipse.ui.internal.keys.WorkbenchKeyboard.press(Workben chKeyboard.j=
ava:791)
at =

org.eclipse.ui.internal.keys.WorkbenchKeyboard.processKeyEve nt(Workbench=
Keyboard.java:838)
at =

org.eclipse.ui.internal.keys.WorkbenchKeyboard.filterKeySequ enceBindings=
(WorkbenchKeyboard.java:565)
at =

org.eclipse.ui.internal.keys.WorkbenchKeyboard.access$3(Work benchKeyboar=
d.java:507)
at =

org.eclipse.ui.internal.keys.WorkbenchKeyboard$KeyDownFilter .handleEvent=
(WorkbenchKeyboard.java:124)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :66)
at org.eclipse.swt.widgets.Display.filterEvent(Display.java:113 9)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:937)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:962)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:947)
at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:975)
at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:971)
at org.eclipse.swt.widgets.Widget.wmChar(Widget.java:1285)
at org.eclipse.swt.widgets.Control.WM_CHAR(Control.java:3770)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:3670 )
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4342 )
at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:22 26)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3282)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:2337)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2301)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:21 76)
at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:463)
at =

org.eclipse.core.databinding.observable.Realm.runWithDefault (Realm.java:=
289)
at =

org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:4=
58)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:149)=

at =

org.eclipse.ui.internal.ide.application.IDEApplication.start (IDEApplicat=
ion.java:101)
at =

org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.j=
ava:146)
at =

org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplicat=
ion(EclipseAppLauncher.java:106)
at =

org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(Eclip=
seAppLauncher.java:76)
at =

org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:=
356)
at =

org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:=
171)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at =

sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.jav=
a:39)
at =

sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessor=
Impl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 476)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:416)
at org.eclipse.equinox.launcher.Main.run(Main.java:1141)
at org.eclipse.equinox.launcher.Main.main(Main.java:1116)

On Wed, 11 Apr 2007 14:29:43 -0400, Cameron Bateman =

<cameron.bateman@oracle.com> wrote:

> There is indeed some strange behavior here, but let's just clarify a f=
ew =

> issues:
>
> 1) JSF Tooling currently does not guarantee facelet support. We have =
=

> had requests in this area though and they are under consideration. If=
=

> you have specific requirements in this area, the best thing to do is =

> launch bugs against the JSF Tooling project specify the support that y=
ou =

> need.
>
> 2) There are two types of content-assist from JSF's perspective: stati=
c =

> value assist and EL assist. Static value assist works on tag attribut=
es =

> that have literal values. For example, if you add a "layout" attribut=
e =

> to the messages component in your example, you should see "list" and =

> "table" in the drop down list. EL support activates when you're insid=
e =

> the #{} braces, such as on your action attribute for the command butto=
n.
>
> When I tried this the first time, both these assists worked okay once =
I =

> fixed the syntax error in your example (the missing closing brace on t=
he =

> inputText). However, the attribute assist on the tags did not recover=
.. =

> This is a JSP editor issue; we don't control the assists for what =

> attributes are available for. The second time it recovered much =

> better. Try fixing syntax errors and then closing and re-opening the =
=

> editor.
>
> 3) We don't support static assists for component libraries other than =
=

> "f" and "h". However, we do provide a meta-data framework so that =

> component library developers can contribute their own meta-data to add=
=

> such support. So you will not see any static content-assistsupport on=
=

> your ajax, ui or tomahawk tag libraries unless someone has added suppo=
rt =

> for them.
>
>
> --Cam
>
> Anil Kommareddi wrote:
>
>> Hi,
>> I am using Eclipse 3.3M6 with WTP2.0M6. It appears that Content assis=
t =

>> is broken in the default JSP Editor. I see several issues and I hope =
it =

>> is just my configuration that is broken.
>
>> My page looks like this (pl ignore any typos, it works when deployed)=
:
>> ------------
>> <?xml version=3D"1.0" encoding=3D"ISO-8859-1" ?>
>> <jsp:root
>> xmlns:ui=3D"http://java.sun.com/jsf/facelets"
>> xmlns:f=3D"http://java.sun.com/jsf/core"
>> xmlns:a4j=3D"https://ajax4jsf.dev.java.net/ajax"
>> xmlns:h=3D"http://java.sun.com/jsf/html"
>> xmlns:t=3D"http://myfaces.apache.org/tomahawk"
>> version=3D"2.0">
>
>> <ui:composition template=3D"/internal/layout/layout.xhtml">
>> <html xmlns=3D"http://www.w3.org/1999/xhtml">
>> <ui:define name=3D"title">Test</ui:define>
>> <ui:define name=3D"content">
>> <a4j:form id=3D"testform">
>> <h:messages />
>> <h:inputText id=3D"test" value=3D"#{testBean.test}">
>> <h:commandButton id=3D"btnAction" value=3D"Submit" =

>> action=3D"#{testBean.action}"/>
>> </a4j:form>
>> </ui:define>
>> </html>
>> </ui:composition>
>> </jsp:root>
>> -----------------------
>
>> 1. The "JSP Expression" assist is shown for MyFaces/Tomahawk/Ajax4JSF=
=

>> libraries, nothing more. The tags seem to be recognized because there=
=

>> is no red underline.
>
>> 2. Facelets tags are not recognized at all, they are flagged with an =
=

>> error "taglib directive for "ui" does not exist or TLD is not found".=
I =

>> have tried extracting the tld and dropping it in the web-inf/lib, but=
=

>> it did not help. I tried dropping it into a directory and setting the=
=

>> build path to point to that directory, that did not help either.
>
>> 3. Custom tag libs - same as Facelets tags.
>
>> #1 above works using the Amateras Faces IDE's JSP Editor - ie I can g=
et =

>> the content assist for MyFaces/Tomahawk/Ajax4JSF, but not Facelets or=
=

>> Custom tags.
>
>> I have tried removing all my plugins completely and using just the =

>> Platform with WTP and its pre-requisites. I started with a fresh =

>> workspace, fresh dynamic web project with JSF facet, but it is the sa=
me =

>> issue. I do not know what else to try. I have seen people mentioning =
=

>> Facelets content assist works with Eclipse, but searching the =

>> newsgroups yielded no clues.
>
>> Any help would be very much appreciated.
>
>> Thanks - Anil.
>
>

-- =

Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

Report message to a moderator

Re: 2.0M6 JSF Content Assist issues [message #474152 is a reply to message #474151]

Mon, 16 April 2007 16:57

Xiaonan Jiang

Messages: 14
Registered: July 2009

Junior Member

Hi, Anil,

I believe this is the same problem I ecountered in the bugzilla#181643:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=181643

The problem happens when you have a jar file in your WEB-INF/lib folder,
and the jar constains a faces-config.xml inside which having tags like
<component-extension>, <property-extension>, or <attribute-extension>.

Thanks.

- Xiaonan

"Anil Kommareddi" <kommareddi@yahoo.com> wrote in message
news:op.tquotw2fvchism@toy2...
Cam,
Thanks for the response. The example I posted was a copy/paste with
irrelevant stuff deleted, hence the syntax error. I cannot get either the
static value assist (f and h too) or the EL assist in the default JSP
editor. The static value assist does not give any error. The EL assist
throws an ArrayStoreException. Pasted the trace below.

I have another user here trying out the latest milestone and he sees the
same issue. The assists work fine in the previous milestone. I guess I
should post this in the webtools forum.

eclipse.buildId=I20070323-1616
java.version=1.5.0_09
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Framework arguments: -startup
C:\tools\eclipse_home\3.3M6\eclipse\plugins\org.eclipse.equi nox.launcher_1.0.0.v20070319.jar
Command-line arguments: -os win32 -ws win32 -arch x86 -startup
C:\tools\eclipse_home\3.3M6\eclipse\plugins\org.eclipse.equi nox.launcher_1.0.0.v20070319.jar

java.lang.ArrayStoreException
at org.eclipse.emf.common.util.BasicEList.assign(BasicEList.jav a:191)
at org.eclipse.emf.common.util.BasicEList.addUnique(BasicEList. java:645)
at
org.eclipse.emf.common.notify.impl.NotifyingListImpl.doAddUn ique(NotifyingListImpl.java:331)
at
org.eclipse.emf.common.notify.impl.NotifyingListImpl.addUniq ue(NotifyingListImpl.java:315)
at org.eclipse.emf.common.util.BasicEList.add(BasicEList.java:6 26)
at
org.eclipse.wst.common.internal.emf.utilities.ExtendedEcoreU til.eSetOrAdd(ExtendedEcoreUtil.java:75)
at
org.eclipse.wst.common.internal.emf.resource.Translator.setM OFValue(Translator.java:605)
at
org.eclipse.wst.common.internal.emf.resource.Translator.setM OFValue(Translator.java:620)
at
org.eclipse.wst.common.internal.emf.resource.Translator.setM OFValue(Translator.java:611)
at
org.eclipse.wst.common.internal.emf.resource.Translator.setT extValueIfNecessary(Translator.java:453)
at
org.eclipse.wst.common.internal.emf.resource.CacheEventNode. commit(CacheEventNode.java:231)
at
org.eclipse.wst.common.internal.emf.resource.EMF2SAXDocument Handler.endElement(EMF2SAXDocumentHandler.java:115)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser .endElement(AbstractSAXParser.java:633)
at
com.sun.org.apache.xerces.internal.impl.dtd.XMLNSDTDValidato r.endNamespaceScope(XMLNSDTDValidator.java:260)
at
com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator. handleEndElement(XMLDTDValidator.java:2059)
at
com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator. endElement(XMLDTDValidator.java:932)
at
com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScanner Impl.scanEndElement(XMLNSDocumentScannerImpl.java:719)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentS cannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFra gmentScannerImpl.java:1685)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentS cannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java: 368)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuratio n.parse(XML11Configuration.java:834)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuratio n.parse(XML11Configuration.java:764)
at
com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(X MLParser.java:148)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser .parse(AbstractSAXParser.java:1242)
at
org.eclipse.wst.common.internal.emf.resource.EMF2SAXRenderer .doLoad(EMF2SAXRenderer.java:93)
at
org.eclipse.wst.common.internal.emf.resource.TranslatorResou rceImpl.basicDoLoad(TranslatorResourceImpl.java:142)
at
org.eclipse.wst.common.internal.emf.resource.CompatibilityXM IResourceImpl.doLoad(CompatibilityXMIResourceImpl.java:173)
at
org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(Resour ceImpl.java:1354)
at
org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(Resour ceImpl.java:1155)
at
org.eclipse.wst.common.internal.emf.resource.CompatibilityXM IResourceImpl.load(CompatibilityXMIResourceImpl.java:259)
at
org.eclipse.wst.common.internal.emf.resource.TranslatorResou rceImpl.load(TranslatorResourceImpl.java:388)
at
org.eclipse.jst.jsf.core.internal.provisional.jsfappconfig.J ARFileJSFAppConfigProvider.getFacesConfigModel(JARFileJSFApp ConfigProvider.java:87)
at
org.eclipse.jst.jsf.core.internal.provisional.jsfappconfig.J SFAppConfigManager.getFacesConfigModels(JSFAppConfigManager. java:404)
at
org.eclipse.jst.jsf.core.internal.provisional.jsfappconfig.J SFAppConfigManager.getManagedBeans(JSFAppConfigManager.java: 439)
at
org.eclipse.jst.jsf.designtime.internal.provisional.symbols. DefaultBeanSymbolSourceProvider.getManagedBeanSymbols(Defaul tBeanSymbolSourceProvider.java:124)
at
org.eclipse.jst.jsf.designtime.internal.provisional.symbols. DefaultBeanSymbolSourceProvider.getSymbols(DefaultBeanSymbol SourceProvider.java:82)
at
org.eclipse.jst.jsf.designtime.internal.provisional.symbols. DefaultBeanSymbolSourceProvider.getSymbol(DefaultBeanSymbolS ourceProvider.java:99)
at
org.eclipse.jst.jsf.designtime.internal.provisional.el.Defau ltDTVariableResolver.resolveVariable(DefaultDTVariableResolv er.java:86)
at
org.eclipse.jst.jsf.designtime.internal.provisional.resolver .SymbolContextResolver.getVariable(SymbolContextResolver.jav a:55)
at
org.eclipse.jst.jsf.core.internal.contentassist.el.FunctionC ompletionStrategy.getProposals(FunctionCompletionStrategy.ja va:86)
at
org.eclipse.jst.jsf.ui.internal.contentassist.el.JSFELConten tAssistProcessor.computeCompletionProposals(JSFELContentAssi stProcessor.java:103)
at
org.eclipse.wst.sse.ui.internal.contentassist.CompoundConten tAssistProcessor.computeCompletionProposals(CompoundContentA ssistProcessor.java:290)
at
org.eclipse.jface.text.contentassist.ContentAssistant.comput eCompletionProposals(ContentAssistant.java:1758)
at
org.eclipse.jface.text.contentassist.CompletionProposalPopup .computeProposals(CompletionProposalPopup.java:478)
at
org.eclipse.jface.text.contentassist.CompletionProposalPopup .access$16(CompletionProposalPopup.java:475)
at
org.eclipse.jface.text.contentassist.CompletionProposalPopup $2.run(CompletionProposalPopup.java:410)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator .java:67)
at
org.eclipse.jface.text.contentassist.CompletionProposalPopup .showProposals(CompletionProposalPopup.java:404)
at
org.eclipse.jface.text.contentassist.ContentAssistant.showPo ssibleCompletions(ContentAssistant.java:1587)
at
org.eclipse.wst.sse.ui.internal.StructuredTextViewer.doOpera tion(StructuredTextViewer.java:376)
at
org.eclipse.ui.texteditor.TextOperationAction$1.run(TextOper ationAction.java:131)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator .java:67)
at
org.eclipse.ui.texteditor.TextOperationAction.run(TextOperat ionAction.java:129)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498 )
at org.eclipse.ui.commands.ActionHandler.execute(ActionHandler. java:185)
at
org.eclipse.ui.internal.handlers.LegacyHandlerWrapper.execut e(LegacyHandlerWrapper.java:109)
at org.eclipse.core.commands.Command.executeWithChecks(Command. java:471)
at
org.eclipse.core.commands.ParameterizedCommand.executeWithCh ecks(ParameterizedCommand.java:424)
at
org.eclipse.ui.internal.handlers.HandlerService.executeComma nd(HandlerService.java:164)
at
org.eclipse.ui.internal.keys.WorkbenchKeyboard.executeComman d(WorkbenchKeyboard.java:467)
at
org.eclipse.ui.internal.keys.WorkbenchKeyboard.press(Workben chKeyboard.java:791)
at
org.eclipse.ui.internal.keys.WorkbenchKeyboard.processKeyEve nt(WorkbenchKeyboard.java:838)
at
org.eclipse.ui.internal.keys.WorkbenchKeyboard.filterKeySequ enceBindings(WorkbenchKeyboard.java:565)
at
org.eclipse.ui.internal.keys.WorkbenchKeyboard.access$3(Work benchKeyboard.java:507)
at
org.eclipse.ui.internal.keys.WorkbenchKeyboard$KeyDownFilter .handleEvent(WorkbenchKeyboard.java:124)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :66)
at org.eclipse.swt.widgets.Display.filterEvent(Display.java:113 9)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:937)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:962)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:947)
at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:975)
at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:971)
at org.eclipse.swt.widgets.Widget.wmChar(Widget.java:1285)
at org.eclipse.swt.widgets.Control.WM_CHAR(Control.java:3770)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:3670 )
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4342 )
at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:22 26)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3282)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:2337)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2301)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:21 76)
at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:463)
at
org.eclipse.core.databinding.observable.Realm.runWithDefault (Realm.java:289)
at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:458)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:149)
at
org.eclipse.ui.internal.ide.application.IDEApplication.start (IDEApplication.java:101)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:146)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:106)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:76)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:356)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:171)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 476)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:416)
at org.eclipse.equinox.launcher.Main.run(Main.java:1141)
at org.eclipse.equinox.launcher.Main.main(Main.java:1116)

On Wed, 11 Apr 2007 14:29:43 -0400, Cameron Bateman
<cameron.bateman@oracle.com> wrote:

> There is indeed some strange behavior here, but let's just clarify a few
> issues:
>
> 1) JSF Tooling currently does not guarantee facelet support. We have had
> requests in this area though and they are under consideration. If you
> have specific requirements in this area, the best thing to do is launch
> bugs against the JSF Tooling project specify the support that you need.
>
> 2) There are two types of content-assist from JSF's perspective: static
> value assist and EL assist. Static value assist works on tag attributes
> that have literal values. For example, if you add a "layout" attribute
> to the messages component in your example, you should see "list" and
> "table" in the drop down list. EL support activates when you're inside
> the #{} braces, such as on your action attribute for the command button.
>
> When I tried this the first time, both these assists worked okay once I
> fixed the syntax error in your example (the missing closing brace on the
> inputText). However, the attribute assist on the tags did not recover.
> This is a JSP editor issue; we don't control the assists for what
> attributes are available for. The second time it recovered much better.
> Try fixing syntax errors and then closing and re-opening the editor.
>
> 3) We don't support static assists for component libraries other than "f"
> and "h". However, we do provide a meta-data framework so that component
> library developers can contribute their own meta-data to add such
> support. So you will not see any static content-assistsupport on your
> ajax, ui or tomahawk tag libraries unless someone has added support for
> them.
>
>
> --Cam
>
> Anil Kommareddi wrote:
>
>> Hi,
>> I am using Eclipse 3.3M6 with WTP2.0M6. It appears that Content assist
>> is broken in the default JSP Editor. I see several issues and I hope it
>> is just my configuration that is broken.
>
>> My page looks like this (pl ignore any typos, it works when deployed):
>> ------------
>> <?xml version="1.0" encoding="ISO-8859-1" ?>
>> <jsp:root
>> xmlns:ui="http://java.sun.com/jsf/facelets"
>> xmlns:f="http://java.sun.com/jsf/core"
>> xmlns:a4j="https://ajax4jsf.dev.java.net/ajax"
>> xmlns:h="http://java.sun.com/jsf/html"
>> xmlns:t="http://myfaces.apache.org/tomahawk"
>> version="2.0">
>
>> <ui:composition template="/internal/layout/layout.xhtml">
>> <html xmlns="http://www.w3.org/1999/xhtml">
>> <ui:define name="title">Test</ui:define>
>> <ui:define name="content">
>> <a4j:form id="testform">
>> <h:messages />
>> <h:inputText id="test" value="#{testBean.test}">
>> <h:commandButton id="btnAction" value="Submit"
>> action="#{testBean.action}"/>
>> </a4j:form>
>> </ui:define>
>> </html>
>> </ui:composition>
>> </jsp:root>
>> -----------------------
>
>> 1. The "JSP Expression" assist is shown for MyFaces/Tomahawk/Ajax4JSF
>> libraries, nothing more. The tags seem to be recognized because there is
>> no red underline.
>
>> 2. Facelets tags are not recognized at all, they are flagged with an
>> error "taglib directive for "ui" does not exist or TLD is not found". I
>> have tried extracting the tld and dropping it in the web-inf/lib, but it
>> did not help. I tried dropping it into a directory and setting the build
>> path to point to that directory, that did not help either.
>
>> 3. Custom tag libs - same as Facelets tags.
>
>> #1 above works using the Amateras Faces IDE's JSP Editor - ie I can get
>> the content assist for MyFaces/Tomahawk/Ajax4JSF, but not Facelets or
>> Custom tags.
>
>> I have tried removing all my plugins completely and using just the
>> Platform with WTP and its pre-requisites. I started with a fresh
>> workspace, fresh dynamic web project with JSF facet, but it is the same
>> issue. I do not know what else to try. I have seen people mentioning
>> Facelets content assist works with Eclipse, but searching the newsgroups
>> yielded no clues.
>
>> Any help would be very much appreciated.
>
>> Thanks - Anil.
>
>

--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

Report message to a moderator

Re: 2.0M6 JSF Content Assist issues [message #474153 is a reply to message #474152]

Tue, 17 April 2007 17:52

Anil Kommareddi

Messages: 9
Registered: July 2009

Junior Member

Hi Xiaonan,
Tomahawk and JBoss RichFaces use the *extension tags. I removed those JARs
from WEB-INF, but I still get the exception.

We have decided to stick with 3.2 with Exadel for now.

Thanks for your response.

- Anil.

Report message to a moderator

Re: 2.0M6 JSF Content Assist issues [message #474154 is a reply to message #474153]

Tue, 17 April 2007 20:02

Cameron Bateman

Messages: 481
Registered: July 2009

Senior Member

Hi Anil,

The Jar loading bug is
https://bugs.eclipse.org/bugs/show_bug.cgi?id=181643. If you CC yourself
on the bug, then you will be sent an e-mail when the bug that appears to
be causing your problem is fixed. This bug is in the high priority bug
list targeted for RC0 (May timeframe).

--Cam

Anil Kommareddi wrote:

> Hi Xiaonan,
> Tomahawk and JBoss RichFaces use the *extension tags. I removed those JARs
> from WEB-INF, but I still get the exception.

> We have decided to stick with 3.2 with Exadel for now.

> Thanks for your response.

> - Anil.

Report message to a moderator

Re: 2.0M6 JSF Content Assist issues [message #474155 is a reply to message #474152]

Tue, 17 April 2007 20:10

Anil Kommareddi

Messages: 9
Registered: July 2009

Junior Member

Hi Cam,
I added myself to the CC list. Hopefully that is what I am seeing.

Thanks - Anil.

Report message to a moderator

Re: 2.0M6 JSF Content Assist issues [message #609324 is a reply to message #474142]

Wed, 11 April 2007 18:29

Cameron Bateman

Messages: 481
Registered: July 2009

Senior Member

Report message to a moderator

Re: 2.0M6 JSF Content Assist issues [message #609332 is a reply to message #474147]

Mon, 16 April 2007 00:26

Anil Kommareddi

Messages: 9
Registered: July 2009

Junior Member

Report message to a moderator

Re: 2.0M6 JSF Content Assist issues [message #609334 is a reply to message #474151]

Mon, 16 April 2007 16:57

Xiaonan Jiang

Messages: 14
Registered: July 2009

Junior Member

Report message to a moderator

Re: 2.0M6 JSF Content Assist issues [message #609337 is a reply to message #474152]

Tue, 17 April 2007 17:52

Anil Kommareddi

Messages: 9
Registered: July 2009

Junior Member

Report message to a moderator

Re: 2.0M6 JSF Content Assist issues [message #609338 is a reply to message #474153]

Tue, 17 April 2007 20:02

Cameron Bateman

Messages: 481
Registered: July 2009

Senior Member

Hi Anil,

The Jar loading bug is
https://bugs.eclipse.org/bugs/show_bug.cgi?id=181643 If you CC yourself
on the bug, then you will be sent an e-mail when the bug that appears to
be causing your problem is fixed. This bug is in the high priority bug
list targeted for RC0 (May timeframe).

--Cam

Anil Kommareddi wrote:

> Hi Xiaonan,
> Tomahawk and JBoss RichFaces use the *extension tags. I removed those JARs
> from WEB-INF, but I still get the exception.

> We have decided to stick with 3.2 with Exadel for now.

> Thanks for your response.

> - Anil.

Report message to a moderator

Re: 2.0M6 JSF Content Assist issues [message #609340 is a reply to message #474152]

Tue, 17 April 2007 20:10

Anil Kommareddi

Messages: 9
Registered: July 2009

Junior Member

Hi Cam,
I added myself to the CC list. Hopefully that is what I am seeing.

Thanks - Anil.

Report message to a moderator

Previous Topic:	Updating org.eclipse.jem to version 1.2.3
Next Topic:	SEVERE: Allocate exception for servlet Faces Servlet java.lang.NullPointerException

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Sep 20 11:13:03 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter