February 2011 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-499) All futures that was in ORM Explorer

by Krasimir Goutcev (JIRA)

All futures that was in ORM Explorer ------------------------------------ Key: JBIDE-499 URL: http://jira.jboss.com/jira/browse/JBIDE-499 Project: JBoss Tools Issue Type: Feature Request Reporter: Krasimir Goutcev - Open Mapping - Edit Source - Edit Mapping - View Table - Clear Mapping - Remove persistent class - rename class -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

4
3
0 / 0

[JBoss JIRA] Created: (JBDS-1565) Installer should use numbering of the same server names simliar as in JBT/JBDS

by Jiri Peterka (JIRA)

Installer should use numbering of the same server names simliar as in JBT/JBDS ------------------------------------------------------------------------------ Key: JBDS-1565 URL: https://issues.jboss.org/browse/JBDS-1565 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: installer, runtime Affects Versions: 4.0.0.CR3 Environment: JBDS 4.0.0.CR3 H162, Linux 64 Reporter: Jiri Peterka Attachments: installer-numbering.png, jbds-numbering.png Usual way is to have unique numbering for each name, something like this: jboss-eap-4.0 jboss-eap-4.0(1) jboss-eap-4.0(2) jboss-soa-p5 jboss-soa-p5 (1) jboss-soa-p5 (2) .. In JBDS installer there is numbering like this: jboss-eap-4.0 jboss-eap-4.0(1) jboss-eap-4.0(2) jboss-soa-p5 jboss-soa-p5 (3) jboss-soa-p5 (4) This should be changed and unified with that how runtimes are titled in JBT/JBDS via Runtime Detection. Add some brackits in JBDS would be better as well. For comparsion of the same runtime set in Installer and JBT/JBDS see screenshots. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-8315) Second step of JSF Project wizard error " Could not load server adapter. Check to make sure that the installation is complete."

by Denis Golovin (JIRA)

Second step of JSF Project wizard error " Could not load server adapter. Check to make sure that the installation is complete." ------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-8315 URL: https://issues.jboss.org/browse/JBIDE-8315 Project: Tools (JBoss Tools) Issue Type: Sub-task Reporter: Denis Golovin -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (JBIDE-7729) RichFaces 4.0 & JSF 2.0 & Tomcat 6 project template.

by Alexey Kazakov (JIRA)

RichFaces 4.0 & JSF 2.0 & Tomcat 6 project template. ---------------------------------------------------- Key: JBIDE-7729 URL: https://jira.jboss.org/browse/JBIDE-7729 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JSF Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.3.x Though Tomcat 6 doesn't support JSF 2.0 it's possible to run RichFaces 4.0 & JSF 2.0 projects on that server. But we have to create a new project template with jsf2 libs to have it worked on Tomcat 6. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBIDE-911) EJB3 component wizards are not included in Beta3

by Tyronne Wickramarathne (JIRA)

EJB3 component wizards are not included in Beta3 ------------------------------------------------ Key: JBIDE-911 URL: http://jira.jboss.com/jira/browse/JBIDE-911 Project: JBoss Tools Issue Type: Feature Request Components: ejb3 Affects Versions: 2.0.0.Beta3 Environment: all environments Reporter: Tyronne Wickramarathne Fix For: 2.0.0.Beta4 EJB3 component wizards are not included in Beta3 release. include EJB3 project creation from the IDE too. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

4
5
0 / 0

[JBoss JIRA] Created: (JBIDE-8414) Preview Edit is not working for New CSS Class Dialog

by Denis Golovin (JIRA)

Preview Edit is not working for New CSS Class Dialog ---------------------------------------------------- Key: JBIDE-8414 URL: https://issues.jboss.org/browse/JBIDE-8414 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Denis Golovin Double click in preview area doesn't let edit preview content -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

5
12
0 / 0

[JBoss JIRA] Created: (JBIDE-3120) Support webbeans typesafe xml schema

by Max Rydahl Andersen (JIRA)

Support webbeans typesafe xml schema ------------------------------------- Key: JBIDE-3120 URL: https://jira.jboss.org/jira/browse/JBIDE-3120 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: webbeans Reporter: Max Rydahl Andersen Fix For: LATER http://docs.jboss.org/webbeans/reference/1.0/en-US/html/xml.html "The advantage of this approach is that you can write an XML schema that prevents spelling errors in your XML document. It's even possible for a tool to generate the XML schema automatically from the compiled Java code. Or, an integrated development environment could perform the same validation without the need for the explicit intermediate generation step." 1) the RI will have a code->xsd generator for web-beans.xml; could maybe be used for validation....but requires that all classes can compile 2) we should have xml completions following the naming standard layed out by webbeans spec -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

5
12
0 / 0

[JBoss JIRA] Created: (JBIDE-3725) Seam components from sources are not loaded by Seam Tools model right after project creation.

by Alexey Kazakov (JIRA)

Seam components from sources are not loaded by Seam Tools model right after project creation. --------------------------------------------------------------------------------------------- Key: JBIDE-3725 URL: https://jira.jboss.org/jira/browse/JBIDE-3725 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.0.0.CR2 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.0.0.GA 1. Create Seam EAR project using New Seam Web Project (I tested on Seam 2.1) 2. Open home.xhtml 3. Ctrl+Space on #{|}. There is not "authenticator" component (see Authenticator.java). 4. Open "Open Seam Component" dialog. Type "authenticator". There is not any "authenticator" component in the project. Clean/Rebuild helps. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

5
24
0 / 0

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

by Yahor Radtsevich (JIRA)

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: Bug Components: JSF Affects Versions: 3.2.0.Beta2 Reporter: Yahor Radtsevich Assignee: Alexey Kazakov Priority: Minor STEPS TO REPRODUCE (see h_head-vs-head.png): 1. 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> =================================== 2. Place the editor cursor after '<t' and press Ctrl-Space. ACTUAL RESULT: No tags is proposed by the Content Assist. EXPECTED RESULT: 'title' tag is proposed. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
7
0 / 0

[JBoss JIRA] Created: (JBDS-1582) web.xml error on login authentication scheme

by Neil Buesing (JIRA)

web.xml error on login authentication scheme -------------------------------------------- Key: JBDS-1582 URL: https://issues.jboss.org/browse/JBDS-1582 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Affects Versions: 4.0.0.CR4 Environment: Windows 32bit Reporter: Neil Buesing In problems view we get the following error: 'Value should be one of BASIC, DIGEST, FORM, CLIENT-CERT', because we have a custom login module. According to XSD 9http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd) it states the value of <auth-method> within element <login-config> must be : BASIC, DIGEST, FORM, CLIENT-CERT or a vendor specific authentication scheme. We are using a vendor specfiic authentication scheme, and still get this red-x error in the problems view, for the project, and in the editor. I have turned off all validations of the IDE (as I can tell), and I still get this error. How do I disable this error, since our web.xml appears to be valid with the XSD. If there is a known workaround, please let me know. <xsd:complexType name="auth-methodType"> <xsd:annotation> <xsd:documentation> The auth-methodType is used to configure the authentication mechanism for the web application. As a prerequisite to gaining access to any web resources which are protected by an authorization constraint, a user must have authenticated using the configured mechanism. Legal values are "BASIC", "DIGEST", "FORM", "CLIENT-CERT", or a vendor-specific authentication scheme. Used in: login-config </xsd:documentation> </xsd:annotation> <xsd:simpleContent> <xsd:restriction base="javaee:string"/> </xsd:simpleContent> </xsd:complexType> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

4
6
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 February 2011