July 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2145) ESB bot tests - overwriting SOA downloads

by Len DiMaggio (JIRA)

Len DiMaggio created JBDS-2145: ---------------------------------- Summary: ESB bot tests - overwriting SOA downloads Key: JBDS-2145 URL: https://issues.jboss.org/browse/JBDS-2145 Project: Developer Studio (JBoss Developer Studio) Issue Type: Task Security Level: Public (Everyone can see) Reporter: Len DiMaggio <nboldt> well, I see only 5.0 and 5.3 on disk <nboldt> jboss-soa-p.5.0.0: <nboldt> jboss-soa-p.4.3.0: <nboldt> jboss-soa-p-5: (contains version.txt = JBoss SOA Platform: Embedded Server - Version 5.3.0.ER2) <nboldt> so maybe the 5.1/5.2/5.3 are overwriting each other -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
10
0 / 0

[JBoss JIRA] (JBDS-2152) Resolve issues with runtime tests

by Len DiMaggio (JIRA)

Len DiMaggio created JBDS-2152: ---------------------------------- Summary: Resolve issues with runtime tests Key: JBDS-2152 URL: https://issues.jboss.org/browse/JBDS-2152 Project: Developer Studio (JBoss Developer Studio) Issue Type: Sub-task Security Level: Public (Everyone can see) Components: SOA Tooling / Platform Reporter: Len DiMaggio Assignee: Len DiMaggio Fix For: 5.0.0.Beta3-SOA -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
3
0 / 0

[JBoss JIRA] (JBIDE-12189) AS server adapters should check and provide way to fix or enough error info for users to get deployment working

by Max Rydahl Andersen (JIRA)

13 years, 7 months

4
4
0 / 0

[JBoss JIRA] Created: (JBIDE-7316) Use hibernate 3.6.x in hibernate plugins.

by Dmitry Geraskov (JIRA)

Use hibernate 3.6.x in hibernate plugins. ----------------------------------------- Key: JBIDE-7316 URL: https://jira.jboss.org/browse/JBIDE-7316 Project: Tools (JBoss Tools) Issue Type: Task Components: Hibernate Affects Versions: 3.2.0.Beta2 Reporter: Dmitry Geraskov Assignee: Dmitry Geraskov Fix For: LATER We are going to make our plugins to use hibernate 3.6, but there are some changes required: 1. Type/NullableType hierarchy was changed, we should not use NullableType any more ( it is deprecated ), but should use AbstractSingleColumnStandardBasicType. The changes are in quiery parameters area 2. To all constructors of values classes ( SimpleValue/Array/OneToMany/... ) added Mapping parameter. We use the classes in internal creation of Configuration object before passing it to exporters ( for example when we generate hbm files based on java files ) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
3
0 / 0

[JBoss JIRA] (JBIDE-12297) Infinite loop in JPA Validator with HQL syntax Query

by Ian Carr (JIRA)

Ian Carr created JBIDE-12297: -------------------------------- Summary: Infinite loop in JPA Validator with HQL syntax Query Key: JBIDE-12297 URL: https://issues.jboss.org/browse/JBIDE-12297 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.4.x Environment: eclipse-jee-juno released jboss-tools nightly build 3.4.0.v20120706-1104-H5102-M1 Reporter: Ian Carr Expect to get a warning about the (invalid) HQL syntax. Actually behaviour makes eclipse unresponsive. An Infinite loop in JPA AbstractExpression parse method when using hibernate syntax FromClause. wordParser contains the text: OUTER JOIN gr.client clnt WITH clnt.clientId = :clientId WHERE ro.ownerId = :ownerId Uses the hibernate WITH clause. Eclipse becomes unresponsive and has high CPU usage. breaking the running instance and checking paused threads get a loop around the following stack trace: Thread [Worker-3] (Suspended) FromClause(AbstractExpression).parse(WordParser, String, boolean) line: 748 FromClause(AbstractFromClause).parse(WordParser, boolean) line: 191 SelectStatement(AbstractSelectStatement).parse(WordParser, boolean) line: 348 SelectStatement.parse(WordParser, boolean) line: 238 SelectStatementFactory.buildExpression(AbstractExpression, WordParser, String, JPQLQueryBNF, AbstractExpression, boolean) line: 55 JPQLExpression(AbstractExpression).parse(WordParser, String, ExpressionFactory, JPQLQueryBNF, AbstractExpression, boolean) line: 983 JPQLExpression(AbstractExpression).parseSingleExpression(WordParser, String, boolean) line: 1004 JPQLExpression.parse(WordParser, boolean) line: 307 JPQLExpression.<init>(CharSequence, JPQLGrammar, String, boolean) line: 129 JPQLExpression.<init>(CharSequence, JPQLGrammar, boolean) line: 91 DefaultJPQLQueryContext(JPQLQueryContext).initializeRoot() line: 700 DefaultJPQLQueryContext(JPQLQueryContext).setQuery(IQuery) line: 808 GenericJpaJpqlQueryHelper(AbstractJPQLQueryHelper).setQuery(IQuery) line: 435 GenericJpaJpqlQueryHelper(JpaJpqlQueryHelper).setQuery(NamedQuery, String) line: 223 GenericJpaJpqlQueryHelper(JpaJpqlQueryHelper).validate(NamedQuery, String, TextRange, int, List<IMessage>) line: 270 GenericJavaNamedQuery2_0.validateQuery_(JpaJpqlQueryHelper, List<IMessage>, IReporter) line: 112 GenericJavaNamedQuery2_0(AbstractJavaQuery<A>).validateQuery(JpaJpqlQueryHelper, List<IMessage>, IReporter, CompilationUnit) line: 226 GenericJavaNamedQuery2_0(AbstractJavaQuery<A>).validate(JpaJpqlQueryHelper, List<IMessage>, IReporter, CompilationUnit) line: 197 GenericPersistenceUnit(AbstractPersistenceUnit).validate(Query, JpaJpqlQueryHelper, List<IMessage>, IReporter) line: 2615 GenericPersistenceUnit(AbstractPersistenceUnit).validateQueries(List<IMessage>, IReporter) line: 2559 GenericPersistenceUnit(AbstractPersistenceUnit).validate(List<IMessage>, IReporter) line: 2249 GenericPersistence.validatePersistenceUnit(List<IMessage>, IReporter) line: 320 GenericPersistence.validate(List<IMessage>, IReporter) line: 272 GenericPersistenceXml.validate(List<IMessage>, IReporter) line: 281 GenericRootContextNode.validate(List<IMessage>, IReporter) line: 244 GenericJpaProject(AbstractJpaProject).validate(List<IMessage>, IReporter) line: 1491 GenericJpaProject(AbstractJpaProject).getValidationMessages(IReporter) line: 1481 InternalJpaProjectManager.buildValidationMessages_(IProject, IReporter) line: 553 InternalJpaProjectManager$BuildValidationMessagesCommand.execute() line: 542 CommandJobCommandAdapter.execute(IProgressMonitor) line: 39 JobCommandJob.run(IProgressMonitor) line: 42 Worker.run() line: 54 Class being parsed looks like: @Entity @Table(name="ResourceOwner") @NamedQueries({ // NB: This is an HQL query as it uses the Hibernate conditional JOIN syntax ie WITH condition @NamedQuery(name = "FindResourceOwnerAndGrantsForROIdandClientId", query = "SELECT ro,gr FROM ResourceOwner ro LEFT OUTER JOIN ro.grants gr LEFT OUTER JOIN gr.client clnt WITH clnt.clientId = :clientId WHERE ro.ownerId = :ownerId"), @NamedQuery(name = "FindResourceOwnerAndGrantsForROIdandClientIdAndScopes", query = "SELECT ro,gr FROM ResourceOwner ro LEFT OUTER JOIN ro.grants gr WITH gr.scopeId IN :scopes LEFT OUTER JOIN gr.client clnt WITH clnt.clientId = :clientId WHERE ro.ownerId = :ownerId"), }) public class ResourceOwner implements Serializable { ... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

3
13
0 / 0

[JBoss JIRA] (JBIDE-12378) Use of Java 6 API where Java 5 is declared as the execution environment

by Peter Palaga (JIRA)

Peter Palaga created JBIDE-12378: ------------------------------------ Summary: Use of Java 6 API where Java 5 is declared as the execution environment Key: JBIDE-12378 URL: https://issues.jboss.org/browse/JBIDE-12378 Project: Tools (JBoss Tools) Issue Type: Task Components: JBossAS/Servers, maven Reporter: Peter Palaga Assignee: Rob Stryker Priority: Trivial (1) The project org.jboss.tools.maven.ui uses java.lang.String.isEmpty() which is available since Java 6 but the project's MANIFEST.MF states Bundle-RequiredExecutionEnvironment: J2SE-1.5 (2) There is a similar problem in org.jboss.ide.eclipse.as.ui where in its MANIFEST.MF the execution environment is declared properly as JavaSE-1.6 but the .classpath file contains something else, namely J2SE-1.5. I will provide a patch for both (1) and (2). A similar issue has recently been fixed in org.jboss.tools.seam.ui by changing the declared execution environment in MANIFEST.MF to JavaSE-1.6. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

4
4
0 / 0

[JBoss JIRA] (JBIDE-12346) Remember the last edited i18n bundle

by Daniel Sachse (JIRA)

Daniel Sachse created JBIDE-12346: ------------------------------------- Summary: Remember the last edited i18n bundle Key: JBIDE-12346 URL: https://issues.jboss.org/browse/JBIDE-12346 Project: Tools (JBoss Tools) Issue Type: Feature Request Affects Versions: 3.3.0.Final Reporter: Daniel Sachse I mostly do i18n stuff after integrating the design provided by the designers. At this time, I am doing batch i18n and I would find it very handsome if the i18n tool would remember the last edited bundle instead of choosing the first one in the list. At the moment I always have to choose the correct one and sometimes I miss it and i18n keys and values are in the wrong bundle. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
1
0 / 0

[JBoss JIRA] (JBIDE-12325) Getting Started Guide is too large (over 140 pages)

by Pavol Srna (JIRA)

Pavol Srna created JBIDE-12325: ---------------------------------- Summary: Getting Started Guide is too large (over 140 pages) Key: JBIDE-12325 URL: https://issues.jboss.org/browse/JBIDE-12325 Project: Tools (JBoss Tools) Issue Type: Enhancement Affects Versions: 3.3.0.Final Reporter: Pavol Srna Fix For: 3.4.0.M1 Getting Started Guide is currently over 140 pages large. Please consider moving some chapters which are not so necessary to get started. For example chapter 8, 9, 10 could be moved to their particular component docs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-8849) JPA project revalidation after export to db

by Jiri Peterka (JIRA)

JPA project revalidation after export to db ------------------------------------------- Key: JBIDE-8849 URL: https://issues.jboss.org/browse/JBIDE-8849 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Hibernate Affects Versions: 3.2.1.M1 Environment: JBDS 4.1.0 m1 H359 Reporter: Jiri Peterka Let's have JPA Project Create entity M, you'll get Table "Z" cannot be resolved Project -> JPA Tools -> Generate Tables from Entities Check Export to database Finish After doing this project entity is not yet valid It would be nice, if connection could be refreshed and code revalidated automatically after export to db (it could be also configurable if desired) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

3
3
0 / 0

[JBoss JIRA] (JBIDE-11288) Investigate name exceptions of OpenShift Application

by Stefan Bunciak (JIRA)

Stefan Bunciak created JBIDE-11288: -------------------------------------- Summary: Investigate name exceptions of OpenShift Application Key: JBIDE-11288 URL: https://issues.jboss.org/browse/JBIDE-11288 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 3.3.0.Beta1 Reporter: Stefan Bunciak Assignee: Andre Dietisheim Priority: Critical Fix For: 3.3.0.Beta2 We should find out which names can be used as OpenShift Application name. I've encountered a problem trying to create aplication called "*richfaces*": Could not create application "richfaces": The supplied application name 'richfaces' is not allowed Could not configure application "richfaces" at "https://openshift.redhat.com/broker/cartridge" After investigating all "naming exceptions" we should add some validation to the OpenShift wizard. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

3
18
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 July 2012