[JBoss JIRA] (JBIDE-10101) Support multiple namespaces in JSP fragments dropped from palette
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-10101?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen resolved JBIDE-10101.
-----------------------------------------
Resolution: Out of Date
Thank you for reporting this issue but this issue have been resolved as out-of-date since it has not had any updates for the last 2+ years (730 days).
If you believe this issue is still relevant and important then please reopen the issue or create a new one mentioning/linking this jira for background information.
Thank you!
> Support multiple namespaces in JSP fragments dropped from palette
> -----------------------------------------------------------------
>
> Key: JBIDE-10101
> URL: https://issues.jboss.org/browse/JBIDE-10101
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 3.3.0.M3
> Reporter: Maxim Shmidov
> Assignee: Alexey Kazakov
> Priority: Minor
> Fix For: LATER
>
>
> Insertion of jsp fragments from palette is managed by org.jboss.tools.jst.jsp.jspeditor.dnd.JSPPaletteInsertHelper class.
> On insertion it defines a namespace for inserted tag in the root document element. Namespace and prefix are received from palette.
> Sometimes it is required to define a several namespaces for one fragment from palette. For example, fragment is some jsp tag, containing a "<jsp:attribute>" child element, so "jsp" namespace should be defined in concert with those tag namespace.
> Potentially i can implement this functionality myself and submit you a patch, but i'd prefer to do it in accordance with DND code owner's considerations.
--
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
12 years, 4 months
[JBoss JIRA] (JBIDE-6248) .brl files from Guvnor examples are not properly read-only.
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-6248?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen resolved JBIDE-6248.
----------------------------------------
Resolution: Out of Date
Thank you for reporting this issue but this issue have been resolved as out-of-date since it has not had any updates for the last 2+ years (730 days).
If you believe this issue is still relevant and important then please reopen the issue or create a new one mentioning/linking this jira for background information.
Thank you!
> .brl files from Guvnor examples are not properly read-only.
> -----------------------------------------------------------
>
> Key: JBIDE-6248
> URL: https://issues.jboss.org/browse/JBIDE-6248
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: drools
> Affects Versions: 3.1.x
> Environment: Fedora Linux v.11
> JBossTools-Update-3.1.0.v201004291720R-H72-GA
> Java 1.6Sun JDK
> JBoss EAP 5.0
> Reporter: Vlado Pakan
> Fix For: LATER
>
>
> .brl files from Guvnor Repository examples are opened as read-only but it's possible to modified them via .brl file editor in JBT.
> It's even possible to save modified file and everything looks correctly saved. But when file is reopened there are no changes saved.
> It should not be possible to edit read-only .brl file.
> 1. deploy guvnor to server and start server
> 2. open guvnor perspective
> 3. add default guvnor repository connection using Guvnor Repositories view
> 4. right click on newly created Guvnor connection and open Guvnor Console
> 5. choose ok to empty login dialog and click yes to install Guvnor examples
> 6. open <Guvnor connection> > pacakges > mortages > CheckBoxDslRule.brl file from Guvnor Repositories view
> 7. add new free form drl to condition save button gets enabled file looks like modified
> 8. save file everything looks like file is saved
> 9. Reopen the file and changes are not saved
--
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
12 years, 4 months
[JBoss JIRA] (JBIDE-863) Option for creating of page.xml file when selected jsp/xhtml file in the package explorer
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-863?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen resolved JBIDE-863.
---------------------------------------
Resolution: Out of Date
Thank you for reporting this issue but this issue have been resolved as out-of-date since it has not had any updates for the last 2+ years (730 days).
If you believe this issue is still relevant and important then please reopen the issue or create a new one mentioning/linking this jira for background information.
Thank you!
> Option for creating of page.xml file when selected jsp/xhtml file in the package explorer
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-863
> URL: https://issues.jboss.org/browse/JBIDE-863
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: seam2
> Reporter: Adrian Mitev
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Fix For: LATER
>
>
> Example:
> when /view/preview.xhtml file is selected, option that will create file /view/preview.page.xml
--
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
12 years, 4 months
[JBoss JIRA] (JBIDE-4846) CDI completions
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-4846?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen resolved JBIDE-4846.
----------------------------------------
Resolution: Out of Date
Thank you for reporting this issue but this issue have been resolved as out-of-date since it has not had any updates for the last 2+ years (730 days).
If you believe this issue is still relevant and important then please reopen the issue or create a new one mentioning/linking this jira for background information.
Thank you!
> CDI completions
> ---------------
>
> Key: JBIDE-4846
> URL: https://issues.jboss.org/browse/JBIDE-4846
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdi
> Reporter: Pete Muir
> Assignee: Victor Rubezhny
> Fix For: LATER
>
>
> Show e.g. qualifiers with a different icon
--
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
12 years, 4 months
[JBoss JIRA] (JBIDE-8071) External process for hibernate code generation cannot work with 3.2-3.5 and 3.6 at the same time
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-8071?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen resolved JBIDE-8071.
----------------------------------------
Resolution: Out of Date
Thank you for reporting this issue but this issue have been resolved as out-of-date since it has not had any updates for the last 2+ years (730 days).
If you believe this issue is still relevant and important then please reopen the issue or create a new one mentioning/linking this jira for background information.
Thank you!
> External process for hibernate code generation cannot work with 3.2-3.5 and 3.6 at the same time
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-8071
> URL: https://issues.jboss.org/browse/JBIDE-8071
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 3.2.0.CR1
> Reporter: Max Rydahl Andersen
> Assignee: Max Rydahl Andersen
> Priority: Critical
> Fix For: 3.3.x
>
>
> If you compile Hibernate Tools against 3.5 it cant run on 3.6; and if you compile against 3.6 it can't run on 3.5 (even though the code is source compatible)
> Since we want to support Hibernate JPA 2 we need to upgrade to 3.6 but then we cannot at the same time provide the "external process for hibernate code generation" since that will almost always collide with users classpath and thus you get errors like:
> java.lang.IncompatibleClassChangeError: Found class org.hibernate.cfg.Mappings, but interface was expected
> Because the interface Mappings in 3.6 is a class in 3.5 and previous versions.
> I don't know a good way to work around this thus for now we will have rollback JBIDE-6423
--
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
12 years, 4 months
[JBoss JIRA] (JBIDE-6768) Migrate CDI/Seam/EL validators (KB Validation framwork) to WST validation V2.
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-6768?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen resolved JBIDE-6768.
----------------------------------------
Resolution: Out of Date
Thank you for reporting this issue but this issue have been resolved as out-of-date since it has not had any updates for the last 2+ years (730 days).
If you believe this issue is still relevant and important then please reopen the issue or create a new one mentioning/linking this jira for background information.
Thank you!
> Migrate CDI/Seam/EL validators (KB Validation framwork) to WST validation V2.
> -----------------------------------------------------------------------------
>
> Key: JBIDE-6768
> URL: https://issues.jboss.org/browse/JBIDE-6768
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsf
> Reporter: Alexey Kazakov
> Assignee: Alexey Kazakov
> Fix For: LATER
>
>
> Now we use V1. V2 has some improvements. For instance we can use Validation->Settings page for include/exclude rules.
> This framework is being developed yet but seems to be stable enough.
--
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
12 years, 4 months
[JBoss JIRA] (JBIDE-4293) Recreate message mechanism for wizards
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-4293?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen resolved JBIDE-4293.
----------------------------------------
Resolution: Out of Date
Thank you for reporting this issue but this issue have been resolved as out-of-date since it has not had any updates for the last 2+ years (730 days).
If you believe this issue is still relevant and important then please reopen the issue or create a new one mentioning/linking this jira for background information.
Thank you!
> Recreate message mechanism for wizards
> --------------------------------------
>
> Key: JBIDE-4293
> URL: https://issues.jboss.org/browse/JBIDE-4293
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: common/jst/core
> Affects Versions: 3.1.0.M1
> Reporter: Yura Zhishko
> Assignee: Viacheslav Kabanovich
> Priority: Optional
> Labels: usability
> Fix For: LATER
>
> Attachments: screenshot-1.jpg, screenshot-2.jpg
>
>
> Well, my opinion according to file and project wizards, that they don't clearly correspond to Eclipse UI part (http://wiki.eclipse.org/User_Interface_Guidelines#Wizards).
>
> 1) First of all when we open any of our wizards, for example, JSP File wizard, we see Next validation message: Attribute Name must be set (screenshot-1). According to Eclipse UI user should see something like this: Create a new JSP file.
> 2) Now begin to print some name in corresponding field -> Result: there is no any validation message (screenshot-2). According to Eclipse UI user should see default message: Create a new JSP file, if the file name doesn't equal to exist page in project.
> From other aspects there are OK. You can exam Eclipse UI behavior of wizards, for example, using standard JSP wizard or wizard for folders' creating.
--
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
12 years, 4 months
[JBoss JIRA] (JBIDE-9557) improve the ws facet page
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-9557?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen resolved JBIDE-9557.
----------------------------------------
Resolution: Out of Date
Thank you for reporting this issue but this issue have been resolved as out-of-date since it has not had any updates for the last 2+ years (730 days).
If you believe this issue is still relevant and important then please reopen the issue or create a new one mentioning/linking this jira for background information.
Thank you!
> improve the ws facet page
> -------------------------
>
> Key: JBIDE-9557
> URL: https://issues.jboss.org/browse/JBIDE-9557
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: webservices
> Affects Versions: 3.2.1.Final
> Reporter: Feng Qian
> Assignee: Brian Fitzpatrick
> Fix For: LATER
>
>
> This is a sub-task, based on https://docspace.corp.redhat.com/docs/DOC-62753.
> JBossWS Runtime combo box - lists all available JBossWS runtimes defined in the IDE including Server Supplied entry; default selection is:
> default JBossWS Runtime as set in Tools -> Preferences -> Web Services -> JBossWS Preferences if set
> server supplied if there's some available in the targeted runtime
--
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
12 years, 4 months
[JBoss JIRA] (JBIDE-7394) location field should be disabled in the new struts project wizard
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-7394?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen resolved JBIDE-7394.
----------------------------------------
Resolution: Out of Date
Thank you for reporting this issue but this issue have been resolved as out-of-date since it has not had any updates for the last 2+ years (730 days).
If you believe this issue is still relevant and important then please reopen the issue or create a new one mentioning/linking this jira for background information.
Thank you!
> location field should be disabled in the new struts project wizard
> ------------------------------------------------------------------
>
> Key: JBIDE-7394
> URL: https://issues.jboss.org/browse/JBIDE-7394
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: struts/shale
> Affects Versions: 3.2.0.Beta1
> Reporter: Lukas Jungmann
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Fix For: LATER
>
>
> -open new struts project wizard
> => since 'Use default location" checkbox is checked, location text field should be disabled as it is in other eclipse wizards
--
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
12 years, 4 months