[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
12 years, 1 month
[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
12 years, 1 month
[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
12 years, 1 month
[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
12 years, 1 month
[JBoss JIRA] (JBIDE-12385) Make ArchiveNodeImpl safe to access member vars (ConcurrentModificationException)
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-12385:
-----------------------------------
Summary: Make ArchiveNodeImpl safe to access member vars (ConcurrentModificationException)
Key: JBIDE-12385
URL: https://issues.jboss.org/browse/JBIDE-12385
Project: Tools (JBoss Tools)
Issue Type: Task
Components: Archives, JBossAS/Servers
Affects Versions: 3.3.1
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 3.3.2, 3.4.0.M1
Unknown how to reproduce but stack trace indicates unsafe access of member variables.
java.util.ConcurrentModificationException
at java.util.HashMap$HashIterator.nextEntry(HashMap.java:806)
at java.util.HashMap$EntryIterator.next(HashMap.java:847)
at java.util.HashMap$EntryIterator.next(HashMap.java:845)
at java.util.HashMap.putAllForCreate(HashMap.java:451)
at java.util.HashMap.clone(HashMap.java:682)
at org.jboss.ide.eclipse.archives.core.model.internal.ArchiveNodeDeltaImpl.loadDelta(ArchiveNodeDeltaImpl.java:215)
at org.jboss.ide.eclipse.archives.core.model.internal.ArchiveNodeDeltaImpl.getDelta(ArchiveNodeDeltaImpl.java:200)
at org.jboss.ide.eclipse.archives.core.model.internal.ArchiveNodeDeltaImpl.loadAllAffectedChildren(ArchiveNodeDeltaImpl.java:150)
--
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
12 years, 2 months