May 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-14657) Typo in new JSF project wizard: 'ServletVersion' -> 'Servlet Version'

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14657?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-14657: ---------------------------------- Attachment: ServletVersion.png > Typo in new JSF project wizard: 'ServletVersion' -> 'Servlet Version' > --------------------------------------------------------------------- > > Key: JBIDE-14657 > URL: https://issues.jboss.org/browse/JBIDE-14657 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JSF > Affects Versions: 4.1.0.Beta1 > Reporter: Michelle Murray > Assignee: Daniel Azarov > Fix For: 4.1.0.Beta2 > > Attachments: JSF_Servletversion.png, ServletVersion.png > > > Typo in new JSF project wizard: 'ServletVersion' -> 'Servlet Version' > (screen caption 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14629) Errors when creating and deploying seam2 project

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14629?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich edited comment on JBIDE-14629 at 5/29/13 7:08 PM: ------------------------------------------------------------------------ It looks as a mistake in shema jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.core/dtd/jboss-deployment-structure-1_0.xsd, which sets elementFormDefault="unqualified", and after that defines child elements locally within xsd:complexType element. If elementFormDefault="unqualified", then all elements that are to be used in xml complying with the schema must be defined as top-level elements in that schema, and referenced from xsd:complexType using 'ref' attribute. When I change it to elementFormDefault="qualified", validation works correctly. was (Author: scabanovich): It looks as a mistake in shema, which sets elementFormDefault="unqualified", and after that defines child elements locally within xsd:complexType element. If elementFormDefault="unqualified", then all elements that are to be used in xml complying with the schema must be defined as top-level elements in that schema, and referenced from xsd:complexType using 'ref' attribute. When I change it to elementFormDefault="qualified", validation works correctly. > Errors when creating and deploying seam2 project > ------------------------------------------------ > > Key: JBIDE-14629 > URL: https://issues.jboss.org/browse/JBIDE-14629 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.1.0.Beta1 > Environment: JBDS 7.0.0.Beta1-v20130519-0601-B206 with bundled JBoss EAP 6.1.0.Beta1 > Reporter: Vlado Pakan > Assignee: Alexey Kazakov > Fix For: 4.1.0.Beta2 > > Attachments: seamerror.png > > > ERROR: DefaultDS Database connection is defined with incorrect link to hsqldb.jar file with JDBC driver for HSQLDB. > 1. Fix DefaultDS Database connection definition > ASSERT: It's possible to connect to DefaultDS > 2. Create new seam project with bundled JBoss EAP and JBoss Seam 2.3.Final > ERROR: There is error in Problems view: > !seamerror.png! > 3. Start seam project on server > ERROR: This error appear in Server log. Application is not deployed: > {noformat} > 3:58:45,950 WARN [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016012: Deployment deployment "seam.war" contains CDI annotations but beans.xml was not found. > 13:58:46,430 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "seam-ds.xml" (runtime-name : "seam-ds.xml") > 13:58:46,430 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "seam.war" (runtime-name : "seam.war") > 13:58:46,431 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "hsqldb.jar" (runtime-name : "hsqldb.jar") > 13:58:46,436 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report > JBAS014775: New missing/unsatisfied dependencies: > service jboss.jdbc-driver.hsqldb_jar (missing) dependents: [service jboss.data-source.java:/seamDatasource] > {noformat} > Is this supported scenario? -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14629) Errors when creating and deploying seam2 project

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14629?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-14629: ----------------------------------- Component/s: upstream (was: Seam 2) > Errors when creating and deploying seam2 project > ------------------------------------------------ > > Key: JBIDE-14629 > URL: https://issues.jboss.org/browse/JBIDE-14629 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.1.0.Beta1 > Environment: JBDS 7.0.0.Beta1-v20130519-0601-B206 with bundled JBoss EAP 6.1.0.Beta1 > Reporter: Vlado Pakan > Assignee: Alexey Kazakov > Fix For: 4.1.0.Beta2 > > Attachments: seamerror.png > > > ERROR: DefaultDS Database connection is defined with incorrect link to hsqldb.jar file with JDBC driver for HSQLDB. > 1. Fix DefaultDS Database connection definition > ASSERT: It's possible to connect to DefaultDS > 2. Create new seam project with bundled JBoss EAP and JBoss Seam 2.3.Final > ERROR: There is error in Problems view: > !seamerror.png! > 3. Start seam project on server > ERROR: This error appear in Server log. Application is not deployed: > {noformat} > 3:58:45,950 WARN [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016012: Deployment deployment "seam.war" contains CDI annotations but beans.xml was not found. > 13:58:46,430 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "seam-ds.xml" (runtime-name : "seam-ds.xml") > 13:58:46,430 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "seam.war" (runtime-name : "seam.war") > 13:58:46,431 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "hsqldb.jar" (runtime-name : "hsqldb.jar") > 13:58:46,436 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report > JBAS014775: New missing/unsatisfied dependencies: > service jboss.jdbc-driver.hsqldb_jar (missing) dependents: [service jboss.data-source.java:/seamDatasource] > {noformat} > Is this supported scenario? -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14497) JBoss Central New and Noteworthy for 4.1.0.Beta1

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14497?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-14497: ----------------------------------- Assignee: Max Rydahl Andersen (was: Fred Bricon) Max, please review https://github.com/jbosstools/jbosstools-documentation/pull/78 > JBoss Central New and Noteworthy for 4.1.0.Beta1 > ------------------------------------------------ > > Key: JBIDE-14497 > URL: https://issues.jboss.org/browse/JBIDE-14497 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Priority: Critical > Fix For: 4.1.0.Beta1 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If JBoss Central is not listed here check if there are issues that should be added and add them. > Document the ones relevant for JBoss Central by adding to [whatsnew|https://github.com/jbosstools/jbosstools-documentation/tree/mast...] and submit a pullrequest. > If no news for this component please reject and close this 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14330) Create an OpenShift connector in the JBoss Tools discovery catalog

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14330?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-14330. --------------------------------- Resolution: Done > Create an OpenShift connector in the JBoss Tools discovery catalog > ------------------------------------------------------------------ > > Key: JBIDE-14330 > URL: https://issues.jboss.org/browse/JBIDE-14330 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Affects Versions: 4.1.0.Alpha2 > Reporter: Fred Bricon > Assignee: Fred Bricon > Labels: new_and_noteworthy > Fix For: 4.1.0.Beta1 > > Attachments: openshift-discovery.png > > > JBoss Central will now always display the OpenShift wizard, even if not installed already (see JBIDE-13987). > If the OpenShift feature is missing, we should install it via the discovery mechanism. > Hence, OpenShift must be added to the JBT discovery catalog (JBDS has it installed by default) -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14330) Create an OpenShift connector in the JBoss Tools discovery catalog

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14330?page=com.atlassian.jira.plugi... ] Fred Bricon closed JBIDE-14330. ------------------------------- > Create an OpenShift connector in the JBoss Tools discovery catalog > ------------------------------------------------------------------ > > Key: JBIDE-14330 > URL: https://issues.jboss.org/browse/JBIDE-14330 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Affects Versions: 4.1.0.Alpha2 > Reporter: Fred Bricon > Assignee: Fred Bricon > Labels: new_and_noteworthy > Fix For: 4.1.0.Beta1 > > Attachments: openshift-discovery.png > > > JBoss Central will now always display the OpenShift wizard, even if not installed already (see JBIDE-13987). > If the OpenShift feature is missing, we should install it via the discovery mechanism. > Hence, OpenShift must be added to the JBT discovery catalog (JBDS has it installed by default) -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14330) Create an OpenShift connector in the JBoss Tools discovery catalog

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14330?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-14330: -------------------------------- Release Notes Text: OpenShift Tools have been added to the JBoss Central Software discovery page, giving users easier access to developing on and for the Cloud. > Create an OpenShift connector in the JBoss Tools discovery catalog > ------------------------------------------------------------------ > > Key: JBIDE-14330 > URL: https://issues.jboss.org/browse/JBIDE-14330 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Affects Versions: 4.1.0.Alpha2 > Reporter: Fred Bricon > Assignee: Fred Bricon > Labels: new_and_noteworthy > Fix For: 4.1.0.Beta1 > > Attachments: openshift-discovery.png > > > JBoss Central will now always display the OpenShift wizard, even if not installed already (see JBIDE-13987). > If the OpenShift feature is missing, we should install it via the discovery mechanism. > Hence, OpenShift must be added to the JBT discovery catalog (JBDS has it installed by default) -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14330) Create an OpenShift connector in the JBoss Tools discovery catalog

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14330?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-14330: -------------------------------- Labels: new_and_noteworthy (was: ) > Create an OpenShift connector in the JBoss Tools discovery catalog > ------------------------------------------------------------------ > > Key: JBIDE-14330 > URL: https://issues.jboss.org/browse/JBIDE-14330 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Affects Versions: 4.1.0.Alpha2 > Reporter: Fred Bricon > Assignee: Fred Bricon > Labels: new_and_noteworthy > Fix For: 4.1.0.Beta1 > > Attachments: openshift-discovery.png > > > JBoss Central will now always display the OpenShift wizard, even if not installed already (see JBIDE-13987). > If the OpenShift feature is missing, we should install it via the discovery mechanism. > Hence, OpenShift must be added to the JBT discovery catalog (JBDS has it installed by default) -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14445) Remove GWT Project from JBoss Central

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14445?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-14445. --------------------------------- Resolution: Done > Remove GWT Project from JBoss Central > ------------------------------------- > > Key: JBIDE-14445 > URL: https://issues.jboss.org/browse/JBIDE-14445 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Fred Bricon > Assignee: Fred Bricon > Labels: new_and_noteworthy > Fix For: 4.1.0.Beta1 > > > From [~burrsutter] : > {quote} > Please remove GWT from "Start from Scratch" in JBoss Central as well as File New menu. > For "Start from Scratch", please replace with "Maven Project". > {quote} -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14445) Remove GWT Project from JBoss Central

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14445?page=com.atlassian.jira.plugi... ] Fred Bricon closed JBIDE-14445. ------------------------------- > Remove GWT Project from JBoss Central > ------------------------------------- > > Key: JBIDE-14445 > URL: https://issues.jboss.org/browse/JBIDE-14445 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Fred Bricon > Assignee: Fred Bricon > Labels: new_and_noteworthy > Fix For: 4.1.0.Beta1 > > > From [~burrsutter] : > {quote} > Please remove GWT from "Start from Scratch" in JBoss Central as well as File New menu. > For "Start from Scratch", please replace with "Maven Project". > {quote} -- 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, 10 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 May 2013