| Author |
Message |
|
|
khandur,
>>there is NO ICEfaces plugins.
Are you sure?
Have you added ICEFaces facet When you created dynamic web project?
|
 |
|
|
|
You can also check ICEfaces tutorial on how to use the ICEfaces InputFile component at http://facestutorials.icefaces.org/tutorial/inputFile-tutorial.html
|
 |
|
|
Please check ICEfaces demo application component showcase ICEfaces Component Suite -> Components -> File Upload at http://component-showcase.icefaces.org/component-showcase/ for how to use ice:inputFile component.
|
 |
|
|
Please double check the location of directory com.icesoft.ide.myeclipse.integration_1.5.3 to see if it is located under {MYECLIPSE_INSTALL_HOME}/myeclipse/eclipse/plugins. On windows, normally the path should be
c:\program files\MyEclipse 5.5 M1\myeclipse\eclipse\plugins\com.icesoft.ide.myeclipse.integration_1.5.3
Regards
Liming
|
 |
|
|
Exceptions or error messages?
|
 |
|
|
This integration officially support MyEclipse 5.1 which is current release version of MyEclipse. I have tested it on MyEclipse 5.5 Milestone 1 and it looks ok. I think you are using MyEclipse 5.5 Milestone 1.
If you project is a web project and JSF capabilities have been successfully added, you should see "Add ICEfaces capabilities" under "MyEclipse" on the web project's popup menu.
If you cannot see "Add ICEfaces capabilities" menu item, could you please check to see if the plugin has been installed properly by
clicking Help->About MyEclipse Enterprise Workbench->Plug-in Details and find the row with following info in the long list.
Provider: ICEsoft Technologies Inc.
Plug-in name: ICEfaces MyEclipse 5.0/5.1 Integration
Version: 1.5.3
Plug-in Id: com.icesoft.ide.myeclipse.integration
Regards
Liming
|
 |
|
|
|
I have just tested using eclipse, icefaces-eclipse-integration bundle 1.5.3, address demo running tomcat 5.5.23. After removed "header" and "addressLogo" block in address.jspx, saved my change, and refresh firefox 2.0.0.2, I can see the changes take effect right away. I am using sun jdk 1.5 but I don't think it causes the problem.
|
 |
|
|
It was an issue about the need to restart tomcat after page gets modified. But it has been fixed in 1.5.3.
You shouldn't need to restart eclipse.
|
 |
|
|
This issue has been fixed in iceface 1.5.3. You may need to update icefaces to v1.5.3. Note: after making changes to your page and save the changes, you need to reload the page in your browser.
|
 |
|
|
The context menu can only be enabled in either J2EE or WEB perspective.
After you switch to WEB or J2EE perspective, in Project Explorer view your dynamic web project should be under "Dynamic Web Projects" category. right click the dynamic web project node, you should see "ICEfaces Integration" item.
Regards
Liming
|
 |
|
|
We haven't tested it on v3.3 yet as mentioned in Readme.html. For now I'd recommend you to refresh your project to see if the tld gets picked up.
right click the project and select Refresh!
Liming
|
 |
|
|
Currently the extent of BEA Workshop integration is restricted to project level integration which includes library and configuration aid. It doesn't provide design-time integration in current release as you've noticed no icon in component palette and design view doesn't recognize ice component. As for tld, it is included under icefaces-comps.jar/META-INF. Yes, you are correct. extract it to WEB-INF/tld directory can eliminate some warning messages re ice components. Actually tld directory has already been created by workshop by default.
Thanx. Liming
|
 |
|
|
bpaduraru,
As Philip has indicated in http://www.icefaces.org/JForum/posts/list/3082.page, files generated from the template provided is a jsp file, not jspx file and should be named as .jsp. ICEfaces parser will accept this kind of non xml jsp and convert it to xml document. if you name the template as .jspx, some servers assume it is a xml document and report validation failure even though ICEfaces accepts it. We provide the template is to get tag and attribute auto-completion working in Eclipse specific environment.
"If I make the jspx as a jsp, then it tells that my index.jsp forward directive is not bound... "
It will be much easier for me if you can post a very small example shows the problem.
|
 |
|
|
Sorry. I missed that there is no "." in your property name.
Based on your files you posted, I can run it on tomcat 5.5.20 without problem using workshop with icefaces capabilities added.
I attached war file here. Note faces-config has been slightly changed and dependent jar files are not included.
|
 |
|
|
|
We should have put a special note on using provided template. The template is added into eclipse-based integration bundles in order to get the auto-completion working.
|
 |
|
|