[JBoss JIRA] (JBIDE-1443) Database view/edit support
by Josef Kopriva (Jira)
[ https://issues.redhat.com/browse/JBIDE-1443?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-1443.
--------------------------------
Closing, nothing to do.
> Database view/edit support
> --------------------------
>
> Key: JBIDE-1443
> URL: https://issues.redhat.com/browse/JBIDE-1443
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: hibernate
> Affects Versions: 2.0.0.GA
> Reporter: Alexander Chabatar
> Assignee: Dmitry Geraskov
> Priority: Minor
> Fix For: 3.2.0.M1
>
>
> We need more support for database operations:
> - Generate Select (SQL, HQL) statement (for table), DDL (for table/entire schema)
> That already exist in DTP (think about integration); no need for us to add that (for the SQL part) :
> - New Table, Foreign Key, Index
> - Delete Table, data (SQL and HQL) - so we need SQL editor
> - Edit table data
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months
[JBoss JIRA] (JBIDE-1824) Java context assist shows a lot of useless tips in the quotes
by Josef Kopriva (Jira)
[ https://issues.redhat.com/browse/JBIDE-1824?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-1824.
--------------------------------
Closing, nothing to do.
> Java context assist shows a lot of useless tips in the quotes
> -------------------------------------------------------------
>
> Key: JBIDE-1824
> URL: https://issues.redhat.com/browse/JBIDE-1824
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: hibernate
> Reporter: Vitali Yemialyanchyk
> Assignee: Max Andersen
> Priority: Minor
> Fix For: 2.1.0.CR1
>
> Attachments: JBIDE-1824.zip, screenshot-1.jpg, screenshot-2.jpg
>
>
> I edit java code and when I press Ctrl-Space in the quotes I get a lot of useless in this context tips (in annotations).
> examples:
> 1) @Table(name="ORDER_TABLE")
> 2) @OneToMany(mappedBy="item")
> 3) String s = "";
> in examples with annotations (1 & 2) I get tips which are useless.
> example 3) & screenshot-1.jpg - this is expected behaviour.
> @NamedQuery - this annotation is exeption case - should work the same way as case 3.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months
[JBoss JIRA] (JBIDE-2027) Wrong default value of height attribute of <td> tag in common.xhtml template.
by Josef Kopriva (Jira)
[ https://issues.redhat.com/browse/JBIDE-2027?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-2027.
--------------------------------
Closing, nothing to do.
> Wrong default value of height attribute of <td> tag in common.xhtml template.
> -----------------------------------------------------------------------------
>
> Key: JBIDE-2027
> URL: https://issues.redhat.com/browse/JBIDE-2027
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common
> Affects Versions: 2.1.0.beta1
> Reporter: Andrei Scherbovich
> Assignee: Alexey Kazakov
> Priority: Major
> Fix For: 2.1.0.CR1
>
> Attachments: 1.jpg
>
>
> Wrong default value of height attribute of <td> tag in common.xhtml template.
> Steps:
> 1. EXECUTE: Create JSF 1.2 KickStart project with facelets
> 2. EXECUTE: Open common.xhtml file
> 3. FAILURE: Wrong default value of height of <td> tag (SEE PICTURE ATTACHED). Now it has height="1", which is almost invisible on server.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months
[JBoss JIRA] (JBIDE-1475) NPE opening html file if JBossTools installed with Local Site
by Josef Kopriva (Jira)
[ https://issues.redhat.com/browse/JBIDE-1475?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-1475.
--------------------------------
Closing, nothing to do.
> NPE opening html file if JBossTools installed with Local Site
> -------------------------------------------------------------
>
> Key: JBIDE-1475
> URL: https://issues.redhat.com/browse/JBIDE-1475
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common
> Affects Versions: 2.0.0.CR1
> Environment: WinXP SP2
> Eclipse 3.3.1.1 for Java EE
> Reporter: Joseph Sondow
> Priority: Major
> Attachments: eclipse-error.txt
>
>
> JBossTools plugin installation has a bug where some editors throw a NullPointerException if the plugin is installed using Local Site.
> Steps to reproduce:
> 1. Install Eclipse 3.3.1.1 JEE using eclipse-jee-europa-fall2-win32.zip by unzipping to C:\eclipse
> 2. Unzip JBossTools-2.0.0.CR1-ALL-win32.zip to C:\jbosstoolsinstall
> 3. Start Eclipse with eclipse.exe -clean
> 4. Help > Software Updates > Find and Install > Search for new features to install > Next
> 5. New Local SIte > C:\jbosstoolsinstall
> 6. Finish plugin installation by following prompts. Quit Eclipse and restart it with eclipse.exe -clean
> 7. Create a new empty simple project. Create an html file. It opens automatically with the JBoss Tools HTML Editor, immediately throwing a NullPointerException (See attached error log). The same happens if you create an XHTML or JSP file, or try to open an existing file of type HTML, XHTML, or JSP.
> Tested on 2 similar computers. The behavior is consistent.
> Workaround:
> Don't use Local Site to install JBossTools plugins. Instead, just copy the contents of the features and plugins folders into the corresponding Eclipse folders, then restart Eclipse.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months
[JBoss JIRA] (JBIDE-12297) Infinite loop in JPA Validator with HQL syntax Query
by Josef Kopriva (Jira)
[ https://issues.redhat.com/browse/JBIDE-12297?page=com.atlassian.jira.plug... ]
Josef Kopriva closed JBIDE-12297.
---------------------------------
Closing, nothing to do.
> Infinite loop in JPA Validator with HQL syntax Query
> ----------------------------------------------------
>
> Key: JBIDE-12297
> URL: https://issues.redhat.com/browse/JBIDE-12297
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate, upstream
> Affects Versions: 4.0.0.Alpha1
> Environment: eclipse-jee-juno released
> jboss-tools nightly build 3.4.0.v20120706-1104-H5102-M1
> Reporter: Ian Carr
> Assignee: Dmitry Geraskov
> Priority: Major
> Fix For: 4.0.x
>
>
> 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 was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months
[JBoss JIRA] (JBIDE-3837) Move classpath providers into some common area
by Josef Kopriva (Jira)
[ https://issues.redhat.com/browse/JBIDE-3837?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-3837.
--------------------------------
Closing, nothing to do.
> Move classpath providers into some common area
> ----------------------------------------------
>
> Key: JBIDE-3837
> URL: https://issues.redhat.com/browse/JBIDE-3837
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: common
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Priority: Major
> Fix For: 3.1.0.M3
>
>
> Creation of common area is important. Whether it gets its own module or just its own plugin in as is debatable. This "core" must have zero dependencies on anything not wtp-related.
> The scope of this core (if located in the AS module) could also be a home for any and all overridden or borrowed WTP code that we find unsuitable in its current form, or any code that could have a common use but interfaces with WTP via extension points or subclassing.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 5 months