June 2012 - jbosstools-issues - Jboss List Archives

[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

11 years, 6 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

11 years, 6 months

4
4
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

11 years, 6 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)

11 years, 6 months

4
11
0 / 0

[JBoss JIRA] (JBIDE-11679) Provide Support Provider and Products to let report issues and enhancement trough Mylin in "Help->Report Bug or Enhancement..." dialog

by Denis Golovin (JIRA)

Denis Golovin created JBIDE-11679: ------------------------------------- Summary: Provide Support Provider and Products to let report issues and enhancement trough Mylin in "Help->Report Bug or Enhancement..." dialog Key: JBIDE-11679 URL: https://issues.jboss.org/browse/JBIDE-11679 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: QA Affects Versions: 3.3.0.Beta3 Reporter: Denis Golovin Assignee: Len DiMaggio Attachments: 1.png, 2.png, 3.png, 4.png We have JIRA project defined in o.j.t.common.mylyn, but it really worthless without integration with "Help->Report Bug or Enhancement..." dialog !1.png! Would be good to define JBossTools Support Provider !2.png! and products (AS Tools in example below) !3.png! Products could be not just JBoss Tools components, but any JBoss Community project that JBoss Tools supports Finish ends in New Task editor for selected product !4.png! -- 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

11 years, 6 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-6082) Remove unused code

by Denis Golovin (JIRA)

Remove unused code ------------------ Key: JBIDE-6082 URL: https://jira.jboss.org/jira/browse/JBIDE-6082 Project: Tools (JBoss Tools) Issue Type: Task Components: QA Affects Versions: 3.1.0.GA Reporter: Denis Golovin Fix For: 3.2.next use http://www.ucdetector.org/ to achieve that -- 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

11 years, 6 months

1
8
0 / 0

[JBoss JIRA] Created: (JBIDE-3060) VPE template dialog ui suggestions

by Max Rydahl Andersen (JIRA)

VPE template dialog ui suggestions ---------------------------------- Key: JBIDE-3060 URL: https://jira.jboss.org/jira/browse/JBIDE-3060 Project: Tools (JBoss Tools) Issue Type: Task Components: Visual Page Editor core Affects Versions: 2.1.2 Reporter: Max Rydahl Andersen Assignee: Denis Golovin Fix For: 3.0.0.beta1 The "custom template" for unknown tags is really useful but extremely well hidden and rather quirky to use 1) The shortcut in the context menu just says "Template" ...no indication of what it does. I suggest we call it something like "Setup template for <the tag name>..." ; that describes what it does plus has ... to show a dialog will come up 2) The actual dialog allow me to type in *any* text for the tag, I instantly tried <button> but that is wrong it should be just button. Help the user here ;) I also tried putting rich:calendar but it does not look like it supports template translation, only simple basic tags - then we should just have editable combo list with choices here. 3) Give a preview of how the tag will look like in the dialog 4) The Template editor in preferences has no instructions and no Add button; at least explain the the tables contain existing prefreences for already configured templates and tell them about the "Setup template.." action in the context menu. ....It also contains 2 lines with some names I never setup (i.e. unknowntag-1, unknwontag-2) - remove them. -- 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

11 years, 6 months

4
13
0 / 0

[JBoss JIRA] Created: (JBIDE-4474) Clean up unused dependencies from plug-ins

by Denis Golovin (JIRA)

Clean up unused dependencies from plug-ins ------------------------------------------ Key: JBIDE-4474 URL: https://jira.jboss.org/jira/browse/JBIDE-4474 Project: Tools (JBoss Tools) Issue Type: Task Affects Versions: 3.1.0.M2 Reporter: Denis Golovin Fix For: 3.1.0.M2 -- 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

11 years, 6 months

2
12
0 / 0

[JBoss JIRA] Created: (JBIDE-1600) VPE templates designer

by Denis Golovin (JIRA)

VPE templates designer ---------------------- Key: JBIDE-1600 URL: http://jira.jboss.com/jira/browse/JBIDE-1600 Project: Tools (JBoss Tools) Issue Type: Feature Request Affects Versions: 2.0.0.GA Reporter: Denis Golovin Assigned To: Denis Golovin The idea is to allow developer see how designed element will look like in VPE during creating VPE template. It could be split editor as VPE is and shows in preview how elements defined in template will look like in VPE. The source used to show preview could be customized, so template developer is able to set up his own xhtml/jsp source used during preview. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

3
18
0 / 0

[JBoss JIRA] Created: (JBIDE-3876) Page structure validation to discover logical errors like tags without required parent tags and etc

by Denis Golovin (JIRA)

Page structure validation to discover logical errors like tags without required parent tags and etc --------------------------------------------------------------------------------------------------- Key: JBIDE-3876 URL: https://jira.jboss.org/jira/browse/JBIDE-3876 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Visual Page Editor core Affects Versions: 3.0.0.GA Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 3.1.0 -- 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

11 years, 6 months

4
11
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues June 2012