September 2012 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-5809) Add clearer error message when edi mapping model schema version is not supported.

by Daniel Bevenius (JIRA)

Add clearer error message when edi mapping model schema version is not supported. --------------------------------------------------------------------------------- Key: JBIDE-5809 URL: https://jira.jboss.org/jira/browse/JBIDE-5809 Project: Tools (JBoss Tools) Issue Type: Task Components: smooks Reporter: Daniel Bevenius Attachments: Screen shot 2010-02-08 at 1.48.16 PM.png When using a edi mapping model that has a higher schema version number then the Smooks runtime bundled with the eclipse plugin supports, the error message is simply: Check Input Task configuration. Error creating Input Model from Sample Input Data. Error "..." I'll attached a screenshot of the error. I noticed this when trying the Smook plugin using the edi-to-java example in Smooks trunk. This example uses the following schema version: http://www.milyn.org/schema/edi-message-mapping-1.3.xsd and the version of Smooks bundled with the eclipse plugin only supports 1.2 (I think). I asked Tom about this and he said that there already is some checking of the versions and perhaps this is only a case on making the error message a little more informative. The version of the Smooks plugin I used is: 1.1.0.v201002050900N-H208-CR2. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

5
16
0 / 0

[JBoss JIRA] (JBIDE-11802) ClassNotFound: WrappedException, when opening smooks configuration with ''<esbr:routeBean/>'

by Jason Shepherd (JIRA)

Jason Shepherd created JBIDE-11802: -------------------------------------- Summary: ClassNotFound: WrappedException, when opening smooks configuration with ''<esbr:routeBean/>' Key: JBIDE-11802 URL: https://issues.jboss.org/browse/JBIDE-11802 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Affects Versions: 3.2.2.Final Environment: JBoss Developer Studio 4.1.2, and 4.1.1 java.version=1.6.0_24 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US Framework arguments: -product com.jboss.jbds.product.product Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.jbds.product.product Reporter: Jason Shepherd Assignee: Brian Fitzpatrick Priority: Minor Smooks editor shows the following error at the top of the guided smooks editor window: "org.eclipse.emf.common.util.WrappedException: java.lang.ClassNotFoundException" It only happens when we include the following in the Smooks configuration: " <esbr:routeBean beanIdRef="orderItemFragment" toServiceCategory="QS" toServiceName="Receiver" routeOnElement="order-item"> <condition idRef="routeItem" /> </esbr:routeBean>" -- 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, 3 months

4
4
0 / 0

[JBoss JIRA] (JBIDE-12664) Process timeout in org.jboss.ide.eclipse.archives.test after 2400s

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-12664: ---------------------------------- Summary: Process timeout in org.jboss.ide.eclipse.archives.test after 2400s Key: JBIDE-12664 URL: https://issues.jboss.org/browse/JBIDE-12664 Project: Tools (JBoss Tools) Issue Type: Bug Components: Archives Affects Versions: 4.0.0.Alpha2 Reporter: Nick Boldt Assignee: Rob Stryker {code} [INFO] org.jboss.ide.eclipse.archives.test ............... FAILURE [40:03.848s] [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.15.0:test (default-test) on project org.jboss.ide.eclipse.archives.test: Error while executing platform: org.codehaus.plexus.util.cli.CommandLineTimeOutException: Error while executing external command, process killed. Process timeout out after 2400 seconds -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.15.0:test (default-test) on project org.jboss.ide.eclipse.archives.test: Error while executing platform {code} https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... -- 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

13 years, 3 months

3
6
0 / 0

[JBoss JIRA] (JBIDE-12637) Hibernate Tools generates @SequenceGenerator with not unique name

by Nicolas Bihan (JIRA)

Nicolas Bihan created JBIDE-12637: ------------------------------------- Summary: Hibernate Tools generates @SequenceGenerator with not unique name Key: JBIDE-12637 URL: https://issues.jboss.org/browse/JBIDE-12637 Project: Tools (JBoss Tools) Issue Type: Bug Components: hibernate Affects Versions: 4.0.0.Alpha1 Reporter: Nicolas Bihan Assignee: Dmitry Geraskov Priority: Blocker When generating entities with EJB3 annotations with a strategy set to "sequence", Hibernate tools generates POJOs with non unique javax.persistence.SequenceGenerator name "generator". But according to the Java documentation : bq. String name (Required) A unique generator name that can be referenced by one or more classes to be the generator for primary key values. See [javadoc|http://docs.oracle.com/javaee/5/api/javax/persistence/SequenceGen...] Exemple of generated code with 4.0.0 Alpha1: {code} @SequenceGenerator(name = "generator", sequenceName = "S_CLIENT") @Id @GeneratedValue(strategy = SEQUENCE, generator = "generator") @Column(name = "CLIENT_ID", unique = true, nullable = false, precision = 22, scale = 0) public long getClientId() { return this.clientId; } {code} [Source code|https://github.com/hibernate/hibernate-tools/blob/master/src/java/or...] can be seen here. So looks like the //TODO comment is right and it should generate a unique name atribute. sequencename+"generator" would be a good name. It would even be better if we could define this name in reveng.xml or/and in a DelegatingReverseEngineeringStrategy class. -- 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

13 years, 3 months

3
5
0 / 0

[JBoss JIRA] (JBIDE-11975) JPA Tooling - Adding JPA Annotations to a POJO - Allow users to choose the field to be marked as PK

by Vimal Kansal (JIRA)

Vimal Kansal created JBIDE-11975: ------------------------------------ Summary: JPA Tooling - Adding JPA Annotations to a POJO - Allow users to choose the field to be marked as PK Key: JBIDE-11975 URL: https://issues.jboss.org/browse/JBIDE-11975 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Vimal Kansal Hi, I am using JBDS 5.0 Beta 3. I created a POJO with follwoing attributes : String username; String password String loginCount; Then I invoked conetxt menu option "Generate Hibernate/JPA annotations", it generates only @Entity annotation. Obviously there is no way for the wizard to find out which attribute should act as PK. However if I include a string "id" anywhere in "username" e.g idusername, usernameid, useridname, it assumes it to be the PK and generates @Id and @GeneratedValue annotation. I wonder if this is by design? I think a better approach would be to let the user choose on the wizard, which field he wants to mark as PK. -- 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, 3 months

4
7
0 / 0

[JBoss JIRA] (JBIDE-12200) Forge: bad location exception in pick-up command, forge runtime cannot recover

by Pavol Srna (JIRA)

13 years, 3 months

4
11
0 / 0

[JBoss JIRA] (JBIDE-12704) Erroneous description in forge console update screen

by George Gastaldi (JIRA)

George Gastaldi created JBIDE-12704: --------------------------------------- Summary: Erroneous description in forge console update screen Key: JBIDE-12704 URL: https://issues.jboss.org/browse/JBIDE-12704 Project: Tools (JBoss Tools) Issue Type: Task Components: forge, updatesite Reporter: George Gastaldi Assignee: Koen Aers Priority: Trivial The current description for Forge Console when selecting to update is: {panel} Plugins for using Seam Forge from within Eclipse. {panel} It should be: {panel} Plugins for using JBoss Forge from within Eclipse. {panel} -- 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

13 years, 3 months

2
3
0 / 0

[JBoss JIRA] (JBIDE-12532) OpenPlugin doesn't open URLs in JBoss Tools

by George Gastaldi (JIRA)

George Gastaldi created JBIDE-12532: --------------------------------------- Summary: OpenPlugin doesn't open URLs in JBoss Tools Key: JBIDE-12532 URL: https://issues.jboss.org/browse/JBIDE-12532 Project: Tools (JBoss Tools) Issue Type: Bug Components: forge Reporter: George Gastaldi Assignee: Koen Aers As of FORGE-611, now it's possible for the OpenPlugin to open URLs. This works when running Forge in console mode, but does not on JBoss Tools. -- 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

13 years, 3 months

2
5
0 / 0

[JBoss JIRA] (JBIDE-12611) Rm plugin is not refreshing the project

by George Gastaldi (JIRA)

George Gastaldi created JBIDE-12611: --------------------------------------- Summary: Rm plugin is not refreshing the project Key: JBIDE-12611 URL: https://issues.jboss.org/browse/JBIDE-12611 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: forge Affects Versions: 3.3.1 Reporter: George Gastaldi Assignee: Koen Aers The rm command is not refreshing the project after deleting a package or a class. -- 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

13 years, 3 months

3
3
0 / 0

[JBoss JIRA] (JBIDE-12571) Eclipse preferences: allow users to define a default server

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-12571: ---------------------------------------- Summary: Eclipse preferences: allow users to define a default server Key: JBIDE-12571 URL: https://issues.jboss.org/browse/JBIDE-12571 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: openshift Affects Versions: 3.3.0.Final Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 4.0.0.Alpha1 Add UI to the preferences that allows users to provide a default OpenShift server to connect to. In terms of widget we need a text-field for the server url and a checkbox that allows people to refer to the default server that is defined in the openshift configfurations (~/.openshift/express.conf and /etc/openshift/express.conf). If the checkbox is checked, the text-field is disabled. Once unchecked the user can enter a default server and override the openshift server that is configured in the openshift (rhc cli-tooling) configuration. -- 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

13 years, 3 months

2
15
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 September 2012