[JBoss JIRA] (JBIDE-2475) Suggest some useful HiperLinks for unknown tags.
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2475?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen resolved JBIDE-2475.
----------------------------------------
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!
> Suggest some useful HiperLinks for unknown tags.
> ------------------------------------------------
>
> Key: JBIDE-2475
> URL: https://issues.jboss.org/browse/JBIDE-2475
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Reporter: Alexey Kazakov
> Assignee: Victor Rubezhny
> Fix For: LATER
>
>
> Now we suggest the particular hiperlinks for the particular xml/jsp/xhtml axis. But we if we don't know some tags/attributes we suggest nothing.
> The idea is suggesting some common Hiperlinks (open file/java class/...) for tags/attributes which are unknown for us.
--
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
[JBoss JIRA] (JBIDE-1840) Error when creating JSF with Facelets project (and when already exists Seam War project)
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-1840?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen resolved JBIDE-1840.
----------------------------------------
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!
> Error when creating JSF with Facelets project (and when already exists Seam War project)
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-1840
> URL: https://issues.jboss.org/browse/JBIDE-1840
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf, seam2
> Affects Versions: 2.0.1
> Environment: WindowsXP SP2
> jbds-win32-1.0.0.GA.jar
> JBoss Developer Studio
> Version: 1.0.0.GA
> Build: JBossTools-200802280019-nightly-ALL-win32.zip
> JDK 1.5_08
> Reporter: Aliaksey Nis
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Fix For: LATER
>
> Attachments: Facelets.txt
>
>
> EXECUTE: Create default Seam WAR project.
> EXECUTE: Create JSF 1.2 with facelets Kickstart w/o libs project.
> FAILURE : Errors appears in error log.
> For each Seam war project (if in workspace more then one seam war project) same error appears.
> Error log attached.
--
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
[JBoss JIRA] (JBIDE-5235) Error during struts kick start project execution on bundled EAP 5.0
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-5235?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen resolved JBIDE-5235.
----------------------------------------
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!
> Error during struts kick start project execution on bundled EAP 5.0
> -------------------------------------------------------------------
>
> Key: JBIDE-5235
> URL: https://issues.jboss.org/browse/JBIDE-5235
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: struts/shale
> Affects Versions: 3.1.0.CR1
> Environment: jbdevstudio-eap-linux-gtk-x86_64-3.0.0.v200911180352M-H96-M4
> sun jdk-6u17-linux-x64
> Reporter: Jiri Peterka
> Assignee: Alexey Kazakov
> Fix For: LATER
>
>
> Steps to reproduce:
> 1. Use bundled EAP 5.0 as runtime
> 2. Create Struts kick start project
> 3. Run it on the server
> 4. Open page in eclipse web browser
> Error message:
> TTP Status 500 -
> type Exception report
> message
> description The server encountered an internal error () that prevented it from fulfilling this request.
> exception
> org.apache.jasper.JasperException: An exception occurred processing JSP page /pages/inputname.jsp at line 8
> 5: <title>KickStart: Input name</title>
> 6: </head>
> 7: <body>
> 8: <html:form action="/greeting.do">
> 9: <table border="0" cellspacing="0" cellpadding="0">
> 10: <tr>
> 11: <td><b>Input name:</b></td>
> 0:05:19,647 ERROR [RequestUtils] Error creating form bean of class demo.GetNameForm
> java.lang.ClassNotFoundException: demo.GetNameForm
> at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:303)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
> at org.apache.struts.util.RequestUtils.applicationClass(RequestUtils.java:207)
> at org.apache.struts.util.RequestUtils.applicationInstance(RequestUtils.java:231)
> at org.apache.struts.util.RequestUtils.createActionForm(RequestUtils.java:837)
> at org.apache.struts.taglib.html.FormTag.initFormBean(FormTag.java:552)
> at org.apache.struts.taglib.html.FormTag.doStartTag(FormTag.java:520)
> at org.apache.jsp.pages.inputname_jsp._jspx_meth_html_005fform_005f0(inputname_jsp.java:133)
> at org.apache.jsp.pages.inputname_jsp._jspx_meth_html_005fhtml_005f0(inputname_jsp.java:106)
> at org.apache.jsp.pages.inputname_jsp._jspService(inputname_jsp.java:73)
> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:369)
> at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:322)
> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:249)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
> at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
> at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
> at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
> at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
> at java.lang.Thread.run(Thread.java:619)
> Workaround: After server restart it works.
> Note: Unable to simulate this without JBDS/JBT so it seems like JBDS/JBT 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
[JBoss JIRA] (JBIDE-7281) Wizards should not allow user to select unsupported JAX-WS spec version
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-7281?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen resolved JBIDE-7281.
----------------------------------------
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!
> Wizards should not allow user to select unsupported JAX-WS spec version
> -----------------------------------------------------------------------
>
> Key: JBIDE-7281
> URL: https://issues.jboss.org/browse/JBIDE-7281
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 3.2.0.Beta1
> Reporter: Lukas Jungmann
> Assignee: Feng Qian
> Fix For: 3.3.x
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> -create a dynamic web project with target runtime set to JBossAS6-M5
> -create a ws client there with JAX-WS spec set to 2.1 and finish the wizard
> => generated code is of JAX-WS version 2.2
> default ws stack in JBossAS6-M5 does not seem to allow user to set JAX-WS spec version. Even though the wsconsume's output says it is generating JAX-WS 2.1 code, it in fact generates code of version 2.2
> jlukas@lukas-laptop:~/latest/jboss-6.0.0.20100911-M5/bin$ ./wsconsume.sh --target=2.2 -o /tmp/fff -k http://footballpool.dataaccess.eu/data/info.wso?WSDL
> Could not find log4j.xml configuration, logging to console.
> WSConsume (CXF) does not allow to setup the JAX-WS specification target, using JAX-WS 2.1.
> log4j:WARN No appenders could be found for logger (org.apache.cxf.common.logging.LogUtils).
> log4j:WARN Please initialize the log4j system properly.
> Loading FrontEnd jaxws ...
> Loading DataBinding jaxb ...
> wsdl2java -compile -exsh false -d /tmp/fff -verbose -classdir /tmp/fff -allowElementReferences http://footballpool.dataaccess.eu/data/info.wso?WSDL
> wsdl2java - Apache CXF 2.2.10
--
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
[JBoss JIRA] (JBIDE-7888) RevEng not allows to extend Beans
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-7888?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen resolved JBIDE-7888.
----------------------------------------
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!
> RevEng not allows to extend Beans
> ---------------------------------
>
> Key: JBIDE-7888
> URL: https://issues.jboss.org/browse/JBIDE-7888
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Environment: winxp jdk6
> Reporter: Peter Rader
> Assignee: Max Rydahl Andersen
> Priority: Minor
> Fix For: 3.3.x
>
>
> hibernate.reveng.xml:
> <hibernate-reverse-engineering>
> <table-filter match-schema="public" match-name=".*">
> <meta attribute="extends">xx.xxx.Base</meta>
> </table-filter>
> </hibernate-reverse-engineering>
> Beans does not extends from "xx.xxx.Base"!
--
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
[JBoss JIRA] (JBIDE-3392) Possibility to overide general seam settings (src target folder) in New Seam Entity/Action... Wizards.
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-3392?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen resolved JBIDE-3392.
----------------------------------------
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!
> Possibility to overide general seam settings (src target folder) in New Seam Entity/Action... Wizards.
> ------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-3392
> URL: https://issues.jboss.org/browse/JBIDE-3392
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: seam2
> Affects Versions: 3.0.0.cr1
> Reporter: Alexey Kazakov
> Assignee: Alexey Kazakov
> Fix For: LATER
>
>
> Seam Action/Form/Entity/... wizards don't use seam settings for EJB projects if they have parent war seam project. In this case only parent war settings will be used. So we have one preference store for seam settings for all releated seam projects. It works well if there is only one Seam EJB Module but it's not convenient for seam project with a few EJB modules. IMO it's not critical issue for 3.0.0.
--
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
[JBoss JIRA] (JBIDE-3625) Option to Expand/Collapse (Code Folding?) for <#if> and <#foreach> keywords in FreeMarker editor
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-3625?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen resolved JBIDE-3625.
----------------------------------------
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 to Expand/Collapse (Code Folding?) for <#if> and <#foreach> keywords in FreeMarker editor
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-3625
> URL: https://issues.jboss.org/browse/JBIDE-3625
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: freemarker
> Reporter: Francisco Jose Peredo Noguez
> Assignee: Denis Golovin
> Fix For: LATER
>
>
> Option to Expand/Collapse (Code Folding?) for <#if> and <#foreach> keywords in FreeMarker editor
--
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
[JBoss JIRA] (JBIDE-6914) Allow seam-gen style profiles for different environments such as prod and dev
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-6914?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen resolved JBIDE-6914.
----------------------------------------
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!
> Allow seam-gen style profiles for different environments such as prod and dev
> -----------------------------------------------------------------------------
>
> Key: JBIDE-6914
> URL: https://issues.jboss.org/browse/JBIDE-6914
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: seam2
> Affects Versions: 3.1.1
> Reporter: Samuel Mendenhall
> Assignee: Alexey Kazakov
> Labels: new_and_noteworthy
> Fix For: LATER
>
>
> A nice feature would be able to build a Seam EAR/WAR based on a defined profile that can be quickly changes such as -Dprofile=prod or -Dprofile-dev, which will allow for say persistence-prod.xml and persistence-dev.xml like in seam-gen. Currently this feature is not in JBDS so deploying to various environments is an added effort when it should be transparent.
--
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
[JBoss JIRA] (JBIDE-7867) Insert tag dialog is very-very annoying
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-7867?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen resolved JBIDE-7867.
----------------------------------------
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!
> Insert tag dialog is very-very annoying
> ---------------------------------------
>
> Key: JBIDE-7867
> URL: https://issues.jboss.org/browse/JBIDE-7867
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: jsf
> Affects Versions: 3.2.0.Beta2
> Reporter: Vitali Yemialyanchyk
> Assignee: Alexey Kazakov
> Priority: Minor
> Labels: new_and_noteworthy
> Fix For: LATER
>
> Attachments: dataTable.png, inputText.png
>
>
> there is no sense in this dialog for normal edit process.
> normal behavior is insert item with all properties by default and then edit this properties in properties view.
> for old users who like this option my recommendation add this as configurable option in Preferences dialog,
> add checkbox "Show "Insert Tag" dialog before drop tag on editor" and mark this unchecked by default.
> IMO, this option will be useless for all, i.e. it is possible to remove this dialog without some loss of functionality.
--
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
[JBoss JIRA] (JBIDE-8427) Really slow deployment while dialog visible
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-8427?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen resolved JBIDE-8427.
----------------------------------------
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!
> Really slow deployment while dialog visible
> -------------------------------------------
>
> Key: JBIDE-8427
> URL: https://issues.jboss.org/browse/JBIDE-8427
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server, upstream
> Affects Versions: 3.2.0.CR1
> Environment: Mac OS X 10.6.4, Eclipse 3.6.1 (64 bits)
> Reporter: henk de boer
> Assignee: Max Rydahl Andersen
> Priority: Minor
> Labels: cocoa, deployment, gui, mac
> Fix For: LATER
>
>
> When a project is deployed using the Jboss tools WTP adapter with the progress dialog visible the operation is really slow. As soon as the operation is send to the background it's fast again.
> It seems the code tries to display every file name on screen, which results in a maximum copy rate of 60 files/second (screen refresh).
--
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