[JBoss JIRA] Created: (JBIDE-7975) jsf validation gives property does not exist warning on messagebundle properties
by erik van altena (JIRA)
jsf validation gives property does not exist warning on messagebundle properties
--------------------------------------------------------------------------------
Key: JBIDE-7975
URL: https://issues.jboss.org/browse/JBIDE-7975
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsp/jsf/xml source editing
Affects Versions: 3.2.0.Beta2
Reporter: erik van altena
Assignee: Alexey Kazakov
Priority: Minor
I have one issue that I did not have with beta 1. In my facelets pages (jsf 1.2 capabilities) I use a message bundle (loaded through f:loadBundle) that I reference like "#{msg.keyname}". Since beta 2 the validator flags all the message bundle properties as non-existing; that did not happen before the update. After changing the references to the map way, as "#{msg['keyname']}", the validator was happy again.
It does not happen for all my files; I have a set of richfaces modal panels that I include using facelets ui:include, stored in a separate subdirectory. These did not trigger any validation errors. Seems it only happens for files I reference in the jsf navigation rules. Although I did get the issue in a facelets template also.
Just to make it clear: I was using beta 1 and had no problems. Upon updating my installed plugins I got beta 2 and after rebooting Eclipse this issue instantly popped up without any changes to the project. I tried the following without success:
- clean the project
- manually validate the entire project
- change the JSF validation settings
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months
[JBoss JIRA] Created: (JBIDE-7987) There is a cycling dependency between jst.jsp and jsf plugins.
by Alexey Kazakov (JIRA)
There is a cycling dependency between jst.jsp and jsf plugins.
--------------------------------------------------------------
Key: JBIDE-7987
URL: https://issues.jboss.org/browse/JBIDE-7987
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsp/jsf/xml source editing
Reporter: Alexey Kazakov
Assignee: Denis Maliarevich
Priority: Critical
Fix For: 3.2.0.CR1
org.jboss.tools.jst.jsp.i18n.ExternalizeStringsWizard (jst.jsp module) uses o.j.t.jsf which is not correct.
I see you added "Import-Package: org.jboss.tools.jsf.model.pv" to org.jboss.tools.jst.jsp/META-INF/MANIFEST.MF to create this hidden cycling dependency.
We should not do it. This cause problems (for instance for thyco build). Please use extension point mechanism to plug in JSF functionality to ExternalizeStringsWizard.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months
[JBoss JIRA] Created: (JBIDE-7945) KB Builder warning is confusing
by Max Andersen (JIRA)
KB Builder warning is confusing
-------------------------------
Key: JBIDE-7945
URL: https://issues.jboss.org/browse/JBIDE-7945
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Reporter: Max Andersen
Assignee: Alexey Kazakov
Fix For: 3.2.0.CR1
I imported seam-forge into my workspace and noticed that after a while (might have been when I enabled CDI on some projects) I started getting this message as warning in problem view:
Description Resource Path Location Type
KB Problem: KB Nature is not installed. KB Builder is not installed. Use Quick Fix to allow JSF Content Assistant and Validation. forge-shell-api Unknown KB Builder Problem
1) KB is not really informative - call it JBoss Tools Knowledge Base or something else than just "KB" so users have an idea what it is about
2) The warning talks about JSF content assit and validation but that is not what my project needs - its CDI Content assistance and validation
3) The location is empty so not sure what in the project is actually triggering this?
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months
[JBoss JIRA] Created: (JBIDE-7688) Loading (instances, images) freezes the UI
by Andre Dietisheim (JIRA)
Loading (instances, images) freezes the UI
------------------------------------------
Key: JBIDE-7688
URL: https://jira.jboss.org/browse/JBIDE-7688
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: deltacloud
Affects Versions: 3.2.0.Beta2
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 3.2.0.CR1
If you go to the cloud viewer and list a clouds instances or images for the first time, instances/images get loaded from the server. This is not done in a background job and UI freezes while the client is waiting for the server response.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months
[JBoss JIRA] Created: (JBIDE-7522) InstanceView: should change selected cloud if another cloud gets selected in the cloud viewer
by Andre Dietisheim (JIRA)
InstanceView: should change selected cloud if another cloud gets selected in the cloud viewer
---------------------------------------------------------------------------------------------
Key: JBIDE-7522
URL: https://jira.jboss.org/browse/JBIDE-7522
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: deltacloud
Affects Versions: 3.2.0.Beta2
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 3.2.0.Beta2
the instance viewer has its own current cloud. It may be changed by a combobox on top of the table that shows the available instances to it.
It would be nice if the instance view would react to selection changes in the cloud viewer
how to reproduce:
1) select a cloud in the instance view
2) select a cloud in the cloud view
Result:
no change of the selected cloud in the instance view
Expected result:
the instance view reacts to the selection changes in the cloud viewer: You select another cloud in the cloud viewer and the instance view changes the selected cloud in its combo & the table shows the available instances in it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months
[JBoss JIRA] Created: (TOOLSDOC-134) Moving Typographical conventions into a seperate book for JBDS
by Isaac Rooskov (JIRA)
Moving Typographical conventions into a seperate book for JBDS
--------------------------------------------------------------
Key: TOOLSDOC-134
URL: https://issues.jboss.org/browse/TOOLSDOC-134
Project: Documentation for JBoss Tools and Developer Studio
Issue Type: Task
Security Level: Public (Everyone can see)
Components: General documentation issues
Reporter: Max Andersen
Assignee: Matthew Casperson
Priority: Critical
Fix For: 3.2.0.Final
We need to shorten the Preface chapter content in the front-matter of our books (from a usability standpoint). To do this we will be separating the typographic convention information into a new book on its own, and referring to it in the Preface for each book.
To do this undertake the following:
To remove, just comment out the following
in Preface.xml:
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
href="Common_Content/Conventions.xml">
<xi:fallback xmlns:xi="http://www.w3.org/2001/XInclude">
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
href="fallback_content/Conventions.xml"/>
</xi:fallback>
</xi:include>
1. Make a book called "JBoss Developer Studio Documentation Typographic
Conventions".
2. Put the Typographic Conventions in it and nothing else.
3. Publish the book.
4. Write a new Preface.xml for all the other JBDS books.
5. Mention the Typographic Conventions book in the new Preface.xml as the place readers should go to for the convention information.
Be sure not to actually place a hard url link to the new typographic conventions book as if the location ever changes all the links will become useless and it presents a huge maintenance issue. When referring to any other book (ever), refer to it by name and users will find it in the list of JBDS books for the release.
When you create the book, store it in the SVN repo for JBT in the documentation/guides folder with the release notes, beginners guide etc...
Note: I have made Max the reporter of this issue as it originally came out of his query on the issue.
Note 2: Make sure to note the creation of this new book and the reasoning for it as a release note for JBDS 4.0
Thanks,
Isaac
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months