January 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-10176) VPE source navigation: open css style which are referenced indirectly from my custom tag implementation does not work (Ctrl + left mouse button)

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10176?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen resolved JBIDE-10176. ----------------------------------------- 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! > VPE source navigation: open css style which are referenced indirectly from my custom tag implementation does not work (Ctrl + left mouse button) > ------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-10176 > URL: https://issues.jboss.org/browse/JBIDE-10176 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: jsp/jsf/xml/html source editing > Affects Versions: 3.3.0.M4 > Reporter: Vitali Yemialyanchyk > Assignee: Alexey Kazakov > Fix For: LATER > > Attachments: JBIDE-10176_20111115.patch > > > 1) https://issues.jboss.org/browse/JBIDE-10173 has attached projects.zip, extract 2 demo projects from projects.zip in some folder on you PC intended for such things; > all steps till step 5 are the same as https://issues.jboss.org/browse/JBIDE-10173 > ... > 6) open stopka-ui-test\src\main\webapp\test.jspx page with VPE: > {code} > <stopka:page xmlns="http://www.w3.org/1999/xhtml" > xmlns:stopka="http://stopka.us" > xmlns:jsp="http://java.sun.com/JSP/Page" > xmlns:c="http://java.sun.com/jsp/jstl/core" > xmlns:utils="http://stopka.us/ui/utils"> > <jsp:output xmlns:jsp="http://java.sun.com/JSP/Page" omit-xml-declaration="yes"/> > <c:set var="bannerType" scope="page" value="simple"/> > <html xmlns="http://www.w3.org/1999/xhtml" lang="en-us"> > <head> > <title>StopKa filemanager</title> > <stopka:css file="system/styles/stopka.css" /> > <utils:common-head-data/> > <stopka:css file="system/styles/filemanager.css" /> > </head> > <body> > <div class="component"> > <div class="subitem"> > </div> > </div> > <div class="article"/> > <div class="in_stopka"> > </div> > <div class="in_filemanager"> > </div> > </body> > </html> > </stopka:page> > {code} > 7) try to open "component" & "subitem": > {code} > <div class="component"> > <div class="subitem"> > </div> > </div> > {code} > with Ctrl + left mouse button click it does not work; > Expected result: should open related css file -> component.css & subitem.css for it particular case. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-8016) Content Assist does not propose head-specific tags inside h:head

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8016?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen resolved JBIDE-8016. ---------------------------------------- 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! > Content Assist does not propose head-specific tags inside h:head > ---------------------------------------------------------------- > > Key: JBIDE-8016 > URL: https://issues.jboss.org/browse/JBIDE-8016 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsf > Affects Versions: 3.2.0.Beta2 > Reporter: Yahor Radtsevich > Assignee: Victor Rubezhny > Priority: Minor > Labels: jsf2 > Fix For: LATER > > Attachments: h_head-vs-head.png > > > STEPS TO REPRODUCE (see h_head-vs-head.png): > 1. Create new JSF 2.0 project. > 2. Create a XHTML file with the following content: > =================================== > <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > <html xmlns="http://www.w3.org/1999/xhtml" > xmlns:h="http://java.sun.com/jsf/html"> > <h:head> > <t > </h:head> > <h:body> </h:body> > </html> > =================================== > 3. Place the editor cursor after '<t' and press Ctrl-Space. > ACTUAL RESULT: > No tags are proposed by the Content Assist. > EXPECTED RESULT: > 'title' tag is proposed. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-2141) Add to proposal list of atribute action vaule of navigation rule from pages.xml in Seam web project.

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-2141?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen resolved JBIDE-2141. ---------------------------------------- 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! > Add to proposal list of atribute action vaule of navigation rule from pages.xml in Seam web project. > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-2141 > URL: https://issues.jboss.org/browse/JBIDE-2141 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing, seam2 > Affects Versions: 2.1.0.CR1 > Reporter: Anton Klimkovich > Assignee: Alexey Kazakov > Priority: Minor > Fix For: LATER > > > EXECUTE: Create Seam web project > EXECUTE: Open pages.xml > ASSERT: > <page view-id="*"> > <navigation> > <rule if-outcome="home" > > <redirect view-id="/home.xhtml"/> > </rule> > </navigation> > </page> > EXECUTE: Open menu.xhtml > EXECUTE: add string <s:button action="" value="HomeSweetHome"></s:button> inside <rich:toolBarGroup> > EXECUTE: Set cursor to s:button action="|" > EXECUTE: Call CA > ASSERT: Value "home" should be in proposal list. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-3765) Add auto complete option in Drools drl editor for dsl files (expander)

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-3765?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen resolved JBIDE-3765. ---------------------------------------- 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! > Add auto complete option in Drools drl editor for dsl files (expander) > ---------------------------------------------------------------------- > > Key: JBIDE-3765 > URL: https://issues.jboss.org/browse/JBIDE-3765 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: drools > Affects Versions: 3.0.0.CR2 > Environment: JBDS 2.0.0.CR2 > Reporter: Joao Viragine > Priority: Minor > Fix For: LATER > > > It would be nice if Drools drl editor recognized dsl files and do auto completion (show all dsl files in project classpath) in expander tag > e.g: > expander (show a pop up with all dsl files in project classpath) -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-4869) cannot mount existing projects with custom dir structure

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-4869?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen resolved JBIDE-4869. ---------------------------------------- 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! > cannot mount existing projects with custom dir structure > -------------------------------------------------------- > > Key: JBIDE-4869 > URL: https://issues.jboss.org/browse/JBIDE-4869 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: seam2 > Affects Versions: 3.0.0.GA, 3.0.1.GA, 3.1.0.M1, 3.1.0.M2 > Environment: any > Reporter: deanhiller > Fix For: LATER > > > We currently work in MyEclipse and everything works awesome. JBoss tools has some other features we want, but alas, we can't set our project up in jboss tools. There seem to be too many issues. Not sure if this is a feature request or bug (ie. I can't use the product without this feature so does that make it a bug?) > Issue #1 : We have a dependency on an EJB3 project and those class files never get deployed to the server so the server ends up with ClassNotFoundException(ie. we can't debug unless we do attach source and then hot deploy fails unlike MyEclipse which works like a charm). > Issue #2 : As soon as we give jboss tools our webroot which is project/input/webroot/WEB-INF, it copies all the libraries and class files there which is causing havoc with our source control and our ant build system as generated files are NOT suppose to ever be put in project/input directories. We have a special output directory if you need a location OR you could change to the way MyEclipse does it and put it on the server....either way, this should be configurable so it is not screwing with people's build systems. > Our custom directory structure works for jar projects and war projects and looks like so > project > ---input > ------javasrc - the *.java files > ------libexclude - the jar files that do not go to WEB-INF/lib > ------libinclude - the jar files that should be put in WEB-INF/lib > ------webroot - all the xhtml files and jpgs > ---------WEB-INF - all descriptor files > jboss tools throws all this junk stuff in WEB-INF/lib and WEB-INF/classes when it should not generate anything unless there is an override for it. All of this stuff works in MyEclipse and we would love to switch but can't. I have seen other posts related to this same issue. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-1266) Roll TestNG plugin into the Seam feature.

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-1266?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen resolved JBIDE-1266. ---------------------------------------- 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! > Roll TestNG plugin into the Seam feature. > ----------------------------------------- > > Key: JBIDE-1266 > URL: https://issues.jboss.org/browse/JBIDE-1266 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: seam2 > Reporter: Gavin King > Fix For: LATER > > > The TestNG plugin should be part of the Seam support. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-6942) Prompt for Basic Auth when accessing secured WSDL

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-6942?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen resolved JBIDE-6942. ---------------------------------------- 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! > Prompt for Basic Auth when accessing secured WSDL > ------------------------------------------------- > > Key: JBIDE-6942 > URL: https://issues.jboss.org/browse/JBIDE-6942 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: webservices > Affects Versions: 3.2.0.M2 > Reporter: Juergen Zimmermann > Assignee: Brian Fitzpatrick > Fix For: 3.3.x > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > A SOAP based Web Service can be defined as follows: > @WebService(name = "MyService") > @WebContext(contextRoot = "/myRoot", authMethod = "BASIC", secureWSDLAccess = true) > @EndpointConfig(configName = "Standard WSSecurity Endpoint") > Now the WSDL cannot be accessed without BASIC authentication. > Therefore, it would be fine, if you could provide a checkbox within the dialog "Select WSDL", so that username and password could be prompted. Just as the checkbox below "Request details" in the main window. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-7885) jboss tools property editor enhancements for I18N

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-7885?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen resolved JBIDE-7885. ---------------------------------------- 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! > jboss tools property editor enhancements for I18N > ------------------------------------------------- > > Key: JBIDE-7885 > URL: https://issues.jboss.org/browse/JBIDE-7885 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Environment: jboss tools, eclipse > Reporter: nimo stephan > Assignee: Viacheslav Kabanovich > Labels: new_and_noteworthy > Fix For: LATER > > > It would be nice to enhance the property editor of jboss tools with the ability to provide a comfortable way for editing i18n. > Look at http://sourceforge.net/projects/eclipse-rbe/ (screenshots) which comes very handy when editing multiple language-files. > JSF provides I18N out of the box with .property files, but there is no way in jboss tools to handle (edit/create/view) different locations in a comfortable way. It should be possible, for example, to have a table-overview of all avaiable keys with their values without opening each property-file and toggling from one to another. Look at http://sourceforge.net/projects/eclipse-rbe/ for impressions. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-4269) Provide a way to filter out elements which will be generated by exporter.

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-4269?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen resolved JBIDE-4269. ---------------------------------------- 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! > Provide a way to filter out elements which will be generated by exporter. > ------------------------------------------------------------------------- > > Key: JBIDE-4269 > URL: https://issues.jboss.org/browse/JBIDE-4269 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: hibernate > Affects Versions: 3.1.0.M1 > Reporter: Dmitry Geraskov > Assignee: Max Rydahl Andersen > Priority: Blocker > Fix For: 3.3.x > > Attachments: patch.txt > > > Now exporter uses Configuration object to get for example pojo's for generation. > After this it calls generation for each of them. > We need to add some filter for this. > First place for such injection is ArtifactCollector as developer can easily specify subclass of this class and set it to exporter. > Also TemplateProducer which used for files generating always gets ArtifactCollector object in constructor from exporter and has access to it. > I' going to add methods filter(Map context), setFilter(Filter) to ArtifactCollector class and call it when necessary in template producer. > Method 'filter' by default will not filter out anything. Non default realizations should use context map to get any objects which is passed to template producer. > Second variant is to add Filter field to Generic exporter and call for filtering in GenericExporter.exportPOJO() method(or in each realization of ModelIterator.process()). > I prefer first way. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-995) Hibernate DB type and dialect should be calculated by selected connection profile.

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-995?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen resolved JBIDE-995. --------------------------------------- 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! > Hibernate DB type and dialect should be calculated by selected connection profile. > ---------------------------------------------------------------------------------- > > Key: JBIDE-995 > URL: https://issues.jboss.org/browse/JBIDE-995 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: hibernate > Affects Versions: 2.0.0.Beta4 > Reporter: Denis Golovin > Priority: Minor > Fix For: LATER > > > Now User select DB type and connection profile and wizard doesn't check if selected DB Type corresponds to selected connection profile. -- 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, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2014