[JBoss JIRA] (JBIDE-12627) EL resolver for expresions which use <ui:param> doesn't work after eclipse restarting
by Alexey Kazakov (JIRA)
Alexey Kazakov created JBIDE-12627:
--------------------------------------
Summary: EL resolver for expresions which use <ui:param> doesn't work after eclipse restarting
Key: JBIDE-12627
URL: https://issues.jboss.org/browse/JBIDE-12627
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsp/jsf/xml source editing
Affects Versions: 4.0.0.Alpha2
Reporter: Alexey Kazakov
Assignee: Viacheslav Kabanovich
Fix For: 4.0.x
1. Create JSF 2 KickStart project
2. Open inputname.xhtml
3. Add <ui:param name="client" value="#{user}" /> inside <ui:composition> (line #9)
4. Save the file.
5. Open common.xhtml
6. Add <h:outputText value="#{client.}" />
7. Try Ctrl+Space for #{client.|}
8. ASSERT: There is "name" in the list of proposals.
9. Close all the editors.
10. Re-start the eclipse
11. Open common.xhtml
12. FAILURE: Try Ctrl+Space for #{client.|}. It's not working anymore.
13. Clean/build the project.
14. Try Ctrl+Space for #{client.|}
15. ASSERT: There is "name" in the list of proposals.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] (JBIDE-12586) editing remote server home does not take affect unless using the browse button
by Max Rydahl Andersen (JIRA)
Max Rydahl Andersen created JBIDE-12586:
-------------------------------------------
Summary: editing remote server home does not take affect unless using the browse button
Key: JBIDE-12586
URL: https://issues.jboss.org/browse/JBIDE-12586
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Reporter: Max Rydahl Andersen
1) EXEC: create a server with remote deployment and point to a directory that does not have standalone/deployments.
2) EXEC: perform publish
3) ASSERT: weird error message and fail to publish because of JBIDE-12585. The path listed is though correct.
4) EXEC: edit the path manually by hand to be correct
5) EXEC: save and perform publish
6) ASSERT: publishining should work now.
Currently #6 fails with same error as #3 and even listing the old path and not the new.
7) EXEC: restart
8) ASSERT: the field contains the hand edited value.
#8 fails too - its as if the handedited changes does not take affect - only the browse button works.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] (JBIDE-12585) remote publishing gives weird error when not pointing to exact expected directory layout
by Max Rydahl Andersen (JIRA)
Max Rydahl Andersen created JBIDE-12585:
-------------------------------------------
Summary: remote publishing gives weird error when not pointing to exact expected directory layout
Key: JBIDE-12585
URL: https://issues.jboss.org/browse/JBIDE-12585
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Reporter: Max Rydahl Andersen
setup an ASx server to deploy remotely (i.e. on openshift) and point to a directory that *does not* have standalone/deployments already in it - then at publish time you get errors like:
"failed to copy to /home/max/work/standalone/deployments/test.war/META-INF/MANIFEST.MF on host neo6.gva.redhat.com
Missing element for : ''"
Not very informative.
If you fix the server to point to a directory that have standalone/deployments already things starts working again.
The error should be more informative - optimally ask the user if the missing directories should be made ?
Didnt we at some point have a "verify" button for the remote setup to check if directories were present?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] (JBIDE-10592) deployments tab war module deployment location is ignored
by erik van altena (Created) (JIRA)
deployments tab war module deployment location is ignored
---------------------------------------------------------
Key: JBIDE-10592
URL: https://issues.jboss.org/browse/JBIDE-10592
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Eclipse Indigo SR1
Reporter: erik van altena
Assignee: Rob Stryker
Priority: Minor
This bug report is created as per requested in this closed issue:
https://issues.jboss.org/browse/JBIDE-10590
I have a Mavenized project (m2eclipse, JBoss Tools Maven Integration) which I publish to a JBoss 7 runtime (standalone) by dragging it to the runtime instance. To work around the publish directory names not matching the maven pom configuration, I use the runtime deployment tab to override the directory names that the project modules are deployed under in the deployments folder of the server.
(next part copy/pasted from original issue comments)
But then I run into the next oddity: the settings for the war module seem to be ignored out of the box. The deployment tab mentions the war module as being deployed as 'app-web.war' while in fact it ends up in the deployments directory as 'app-web-1.0.0-SNAPSHOT.war', just like Maven would name it if you don't provide a finalName. However, as soon as I tab over the deployment locations and save the changes to the runtime configuration, upon full publish the web module gets the directory name as it is listed in the deployments tab.
To be a little more specific: I get this behavior when I haven't made changes yet to the war entry in the deployment tab; the tab indicates the correct name but the result after publishing is wrong. When I then press tab to navigate to the deployment-location of the war, I don't change anything but I hit CTRL+S to save changes, upon full publish the name is then correct.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months