[JBoss JIRA] (JBIDE-15797) correct icons
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15797?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-15797.
---------------------------------
Verified in JBDS 7.1.0.Beta1
Build id: Beta1-v20131026-0928-B470
> correct icons
> --------------
>
> Key: JBIDE-15797
> URL: https://issues.jboss.org/browse/JBIDE-15797
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.Beta1, 4.2.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.1.Beta1, 4.2.0.Alpha1
>
>
> There are a few quirks that we should fix for the icons:
> * the domain icon (globe) is cropped in MacOS
> * the "new connection" icon (in the explorer toolbar) is lacking some "+" and does not match the connection-icon in the explorer
> * "edit connection" is not matching the connection icon either (its a pen, should be pen with connection 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, 5 months
[JBoss JIRA] (JBIDE-14534) Errors in Spring project archetypes
by Joshua Wilson (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14534?page=com.atlassian.jira.plugi... ]
Joshua Wilson commented on JBIDE-14534:
---------------------------------------
Regarding how changing the version makes the error go away in Eclipse. While this is true it does not actually allow you to deploy the application to JBoss (where the schema lives).
After looking deeper into this I believe that they are right on JBIDE-14629, and that the elementFormDefault="unqualified" needs to be changed to elementFormDefault="qualified".
> Errors in Spring project archetypes
> -----------------------------------
>
> Key: JBIDE-14534
> URL: https://issues.jboss.org/browse/JBIDE-14534
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, project-examples, upstream
> Affects Versions: 4.1.0.Beta1
> Environment: JBT 4.1.0.Beta1
> Reporter: Radim Hopp
> Assignee: Snjezana Peco
> Fix For: 4.1.x
>
>
> There are 2 errors in Spring Project archetype:
> {code}
> Description Resource Path Location Type
> cvc-complex-type.2.4.a: Invalid content was found starting with element 'deployment'. One of '{ear-subdeployments-isolated, deployment, sub-deployment, module}' is expected. jboss-deployment-structure.xml /jboss-springmvc-webapp/src/main/webapp/WEB-INF line 2 XML Problem
> cvc-complex-type.2.4.a: Invalid content was found starting with element 'deployment'. One of '{ear-subdeployments-isolated, deployment, sub-deployment, module}' is expected. jboss-deployment-structure.xml /jboss-springmvc-webapp/src/main/webapp/WEB-INF line 2 XML Problem
> {code}
> [0] https://bugzilla.redhat.com/show_bug.cgi?id=996680
> [1] https://issues.jboss.org/browse/WFLY-943
--
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, 5 months
[JBoss JIRA] (JBDS-2641) jboss-deployment-structure file validation problem
by Joshua Wilson (JIRA)
[ https://issues.jboss.org/browse/JBDS-2641?page=com.atlassian.jira.plugin.... ]
Joshua Wilson commented on JBDS-2641:
-------------------------------------
In my last comment I wrote about how changing the version makes the error go away in Eclipse. While this is true it does not actually allow you to deploy the application to JBoss (where the schema lives).
After looking deeper into this I believe that they are right on JBIDE-14629, that the elementFormDefault="unqualified" needs to be changed to elementFormDefault="qualified".
> jboss-deployment-structure file validation problem
> --------------------------------------------------
>
> Key: JBDS-2641
> URL: https://issues.jboss.org/browse/JBDS-2641
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 7.0.0.Beta1
> Reporter: Tomas Remes
> Fix For: 7.0.0.Beta2
>
>
> E.g. try to create new Seam2.3 project. There will be created jboss-deployment-structure.xml descriptor in WebContent/WEB-INF directory. Notice the following error:
> {noformat}
> vc-complex-type.2.4.a: Invalid content was found starting with element 'deployment'. One of '{ear-subdeployments-isolated, deployment, sub-deployment, module}' is expected. jboss-deployment-structure.xml /testproject/WebContent/WEB-INF line 2 XML Problem
> {noformat}
--
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, 5 months
[JBoss JIRA] (JBIDE-14629) Errors when creating and deploying seam2 project with Seam 2.3.Final
by Joshua Wilson (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14629?page=com.atlassian.jira.plugi... ]
Joshua Wilson commented on JBIDE-14629:
---------------------------------------
In my last comment I wrote about how changing the version makes the error go away in Eclipse. While this is true it does not actually allow you to deploy the application to JBoss (where the schema lives).
After looking deeper into this I believe that [~scabanovich] is right and the elementFormDefault="unqualified" needs to be changed to elementFormDefault="qualified".
> Errors when creating and deploying seam2 project with Seam 2.3.Final
> ---------------------------------------------------------------------
>
> 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.1.Final
>
> 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, 5 months
[JBoss JIRA] (JBDS-2064) Creating Spring or Richfaces projects - tied to EAP6 runtime fails
by Joshua Wilson (JIRA)
[ https://issues.jboss.org/browse/JBDS-2064?page=com.atlassian.jira.plugin.... ]
Joshua Wilson commented on JBDS-2064:
-------------------------------------
Sorry, my comment doesn't actually have anything to do with this issue.
> Creating Spring or Richfaces projects - tied to EAP6 runtime fails
> ------------------------------------------------------------------
>
> Key: JBDS-2064
> URL: https://issues.jboss.org/browse/JBDS-2064
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: runtime
> Affects Versions: 5.0.0.Beta1
> Environment: Version: 5.0.0.Beta1
> Build id: v20120307-0626-H98-Beta1
> Build date: 20120307-0626
> Reporter: Len DiMaggio
> Assignee: Fred Bricon
> Priority: Blocker
> Fix For: 5.0.0.Beta1
>
>
> The version of the Spring archetype that is currently used by JBDS for Spring or Richfaces projects pulls in an older version of the Spring BOM which is not found in the ER2 WFK repo.
--
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, 5 months