[Randy]

This message has not been recovered.

[Riyad Kalla]

This message has not been recovered.

[Randy]

This message has not been recovered.

[Randy]

Ok, I’m getting my butt kicked. monday.

I went to Window > Prefs > MyEclipse > Project Capabilities > Java Server Faces, and removed the myfaces stuff (not the depndancies though, just stuff with myfaces-*).

I then added the myfaces 1.1.0 myfaces-impl.jar, myfaces-api.jar, and tomahawk.jar (mentioned here: http://wiki.apache.org/myfaces/From_1.0.9m9_to_1.1.0)

I then cleaned up my projects buildpath, so these jars were on the path. verified that the stuff in the webroot/WEB-INF/libs was the new stuff, not the old stuff.

I then tweeked my jsp to use the new myfaces stuff by tweeking the include urls, ie: <%@ taglib uri=”http://myfaces.apache.org/tomahawk&#8221; prefix=”t”%>

problem so far is that anything in the tomahawk package is not being seen, so <t:tree2…> failes since it can’t find it.

Ideas? Also, is the next release of ME going to have the 1.1.0 myfaces support?

TIA!

Randy

[support-eugene]

I tried to upgrade the project (I have MyEclipse 4.0.1):
1. Created JSF project with MyFaces 1.0.9.
2. Removed all myfaces* jars.
3. Copied the myfaces-api, myfaces-impl and tomahawk jars.

Contest assist works with the tomahawk TLD now.

[support-eugene]

I verified your configuration of MyFaces 1.1.0 support – it worked fine, context assist was showing t:tree, t:tree2, etc. Do you see anything in the log?

List of the MyFaces jar files after I changed the preferences:
D:/myfaces-1.1.0/myfaces-impl.jar;
D:/myfaces-1.1.0/myfaces-api.jar;
D:/myfaces-1.1.0/tomahawk.jar;
MYECLIPSE_JSF_HOME/1.1/MyFaces/lib/commons-beanutils-1.6.1.jar;
MYECLIPSE_JSF_HOME/1.1/MyFaces/lib/commons-codec-1.2.jar;
MYECLIPSE_JSF_HOME/1.1/MyFaces/lib/commons-collections-3.0.jar;
MYECLIPSE_JSF_HOME/1.1/MyFaces/lib/commons-digester-1.5.jar;
MYECLIPSE_JSF_HOME/1.1/MyFaces/lib/commons-el.jar;
MYECLIPSE_JSF_HOME/1.1/MyFaces/lib/commons-fileupload-1.0.jar;
MYECLIPSE_JSF_HOME/1.1/MyFaces/lib/commons-logging.jar;
MYECLIPSE_JSF_HOME/1.1/MyFaces/lib/commons-validator.jar;
MYECLIPSE_JSF_HOME/1.1/MyFaces/lib/jakarta-oro.jar;
MYECLIPSE_JSF_HOME/1.1/MyFaces/lib/jsp-2.0.jar;
MYECLIPSE_JSF_HOME/1.1/MyFaces/lib/jstl.jar

[Randy]

wow. I’m still having a bad day. I just can’t get this to work for some reason it looks like it is not seeing any of the tlds for jsf/jstl.

Here is what my MyFaces jar files look like:
/usr/local/randy/workspace/Libs/myfaces-1.1.0/tomahawk.jar
/usr/local/randy/workspace/Libs/myfaces-1.1.0/myfaces-impl.jar
/usr/local/randy/workspace/Libs/myfaces-1.1.0/myfaces-api.jar
MYECLIPSE_JSF_HOME/1.1/MyFaces/lib/jstl.jar
MYECLIPSE_JSF_HOME/1.1/MyFaces/lib/commons-digester-1.5.jar
MYECLIPSE_JSF_HOME/1.1/MyFaces/lib/commons-collection-3.0.jar
MYECLIPSE_JSF_HOME/1.1/MyFaces/lib/commons-el.jar
MYECLIPSE_JSF_HOME/1.1/MyFaces/lib/commons-validator.jar
MYECLIPSE_JSF_HOME/1.1/MyFaces/lib/commons-logging.jar
MYECLIPSE_JSF_HOME/1.1/MyFaces/lib/commons-fileupload.jar
MYECLIPSE_JSF_HOME/1.1/MyFaces/lib/jsp-2.0.jar
MYECLIPSE_JSF_HOME/1.1/MyFaces/lib/commons-beanutils-1.6.1.jar
MYECLIPSE_JSF_HOME/1.1/MyFaces/lib/commons-codec-1.2.jar
MYECLIPSE_JSF_HOME/1.1/MyFaces/lib/jakarta-oro.jar

Some other intersting stuff. If I don’t copy the new myfaces-*.jar and tomahawk.jar into my webroot/WEB-INF/lib, they don’t get copied there. Also when I deploy the project to tomcat 5.5.9, these files are not copied either.

If I start typing the tag (ie a <) I don’t get any of the tags that are imported:
<%@ taglib uri=”http://java.sun.com/jsf/html&#8221; prefix=”h” %>
<%@ taglib uri=”http://java.sun.com/jsf/core&#8221; prefix=”f” %>
<%@ taglib uri=”http://myfaces.apache.org/tomahawk&#8221; prefix=”t”%>
<!– <%@ taglib uri=”http://myfaces.apache.org/extensions&#8221; prefix=”x”%> 1.0.9 –>

Instead I get a dialog that has “JSP Expression”

I did clean up my project build path too. I selected configure build path, then removed the old myfaces stuff, and added the new myfaces*.jar and tomahawk.jar (I use external lib, and I’ve tried pointing to my …./workspace/Libs/myfaces-1.1.0/myfaces*jar. I noticed on the build path that it includes the $PROJECTHOME/webclient/WEB-INF/lib/(all of the myfaces jars). so I manually copied the myfaces*.jar here, then pointed the build path to it.

I’m sure I’m missing something very obvious, and your help is MUCH appreciated.

A thought. would it be easier to just remove from the project the myfaces config, then add it again with the above config? If so, what is the safest way to remove it?

Tx again!

Randy

[Randy]

Ok, the issue has to be related to me changing the current config. I created a new project, added the JSF capability and it looks like it works (ie I can see the <t:tree2 tag).

What is the safest way for me to remove the jsf capability from the current project so I can add it again with the new stuff?

Tx!

randy

[support-eugene]

I did the following:
1. Removed all myfaces* Jars from my project.
2. Copied the 3 jars from MyFaces 1.1.0
3. Refreshed the project (the classpath was updated automatically).
When I opened the JSP editor the tomahawk tags were accessible.

[support-eugene]

1. Removed all myfaces* Jars from my project.

I meant, removed them from the classpath and deleted from the WEB-INF/lib folder.

[Randy]

Ah. the refresh. I forgot about that.

I did this (after removing the external jar references to the myfaces-*.jar and tomahawk.jar) and the new myfaces and tomahawk.jars appeared on my buildpath.

I still have the issue in my jsp editor with the tld’s not being seen (ie I can’t autocomplete the <t:tree2…>. So I created a new jsp in the updated myfaces project and it works. not sure why the original jsp is broke, but I will rename/create a new one/remove the old one.

This seems to work so far. I’ll keep you posted.

another question springs to mind (pun intended). Does the jsp editor allow the ability to show me the attribute list of a tag? Or is this something that I can add as a request?

Tx again!
Randy

[support-eugene]

Just tried again – the way I described updates the project fine 🙁

You can see the list of the custom tag attributes (and edit their value) in a property view (Advanced tab, if the component has several tabs in the properties) or in the context assist (Ctrl+Space when editing the element attributes). This list will show only attributes described in TLD file (i.e. attributes propagated by JSF components to the HTML components will not be shown).

[Randy]

I’m sure I torqued something in the jsp. I got it working now. I’m back to my original problem of the tree2 menu not being expandable, but that is my issue…

;->

That is a NEAT trick to see the attributes! This helps immensely!

Tx again for your help. Back to the fun!

Randy

[support-eugene]

Thanks for your help. You will see built-in support of MyFaces 1.1.0 in coming releases of MyEclipse.

[trapongx]

Just Extract tomahawk.jar$META-INF/tomahawk.tld to WEB-INF then you’ll get what you need.
(myfaces1.1.1)

[Author]

Posts