[JBoss JIRA] Created: (JBIDE-1592) Facelets taglibs from file.jar/META-INF/*.tablib.xml or registered in web.xml by facelets.LIBRARIES context param isn't used for content assists in source part of VPE
by Denis Golovin (JIRA)
Facelets taglibs from file.jar/META-INF/*.tablib.xml or registered in web.xml by facelets.LIBRARIES context param isn't used for content assists in source part of VPE
----------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-1592
URL: http://jira.jboss.com/jira/browse/JBIDE-1592
Project: Tools (JBoss Tools)
Issue Type: Bug
Reporter: Denis Golovin
Fix For: 2.1
That would be nice if <tag> declaration from *.taglib.xml are discovered and used in VPE content assists.
Here is scenario for facelets taglib registered in web.xml:
1. EXECUTE: Create JFP Project using New JSF Project Wizard
2. EXECUTE: Enter a name, select JSF environment: ['JSF 1.2 with Facelets', select Template: 'FaceletKikStartWithoutLibs' then press 'Next'
3. EXECUTE: Select Server Runtime and Target Server then press 'Finish'
4. EXECUTE: Copy attached files custom.taglib.xml and inputCurrency.xhtml to /WEB-INF
5. EXECUTE: Copy attached file show100.xhtml to WebContent/pages
6. EXECUTE: Open web.xml in any editor and add text below
<context-param>
<param-name>facelets.LIBRARIES</param-name>
<param-value>/WEB-INF/custom.taglib.xml</param-value>
</context-param>
8. EXECUTE: Open show100.xhtml in VPE
7. ASSERT: Content proposal list for <c: should contain inputCurrency tag
9. ASSERT: Ctrl+click on 'xmlns:c="http://mydomain.com/jsf/myproject"' opens custom.taglib.xml in xml editor
Scenario for facelets taglib in jar is almost the same but *.taglib.xml should be discovered in <filename>.jar/META-INF/*.taglib.xml.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years
[JBoss JIRA] Created: (JBIDE-2050) AS (running/stopped) state is not retrieved in Eclipse if the server configuration is not the "default" but another one with different port bindings.
by Mario Balaban (JIRA)
AS (running/stopped) state is not retrieved in Eclipse if the server configuration is not the "default" but another one with different port bindings.
-----------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-2050
URL: http://jira.jboss.com/jira/browse/JBIDE-2050
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 2.0.1
Environment: Linux 2.6.22-14-generic, Eclipse Europa Version: 3.3.2, JbossToolsPlugin 2.0.1GA-ALL linux, JbossAS 4.2.2.GA
Reporter: Mario Balaban
On the same machine I had to create 2 instances of JbossAS, one for testing and another for development. The instance used for testing is using the "default" configuration. The test (default) instance I am able to start and to stop correctly from the Eclipse IDE. The "devel" instance that is a copy of the "default" configuration but has different port bindings (modified jboss-service.xml by uncommenting the tag <mbean code="org.jboss.services.binding.ServiceBindingManager"..../> ) has problems when starting and stopping from eclipse IDE. In the console window of IDE I see " [Server] JBoss (MX MicroKernel) [4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139)] Started in 15s:993ms" but the state of the server in the "Servers" window of the IDE is Starting... It remains "Starting..." till an OutOfMemory is visualized in the IDE. This error happens even when no applications are deployed to the deploy directory of the "devel" configuration. It seems that the problem is associated to different port bindings used by "devel" configuration.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years