July 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-11430) Multiple selection in Source Editor is not properly reflected in Visual Editor

by Vlado Pakan (JIRA)

Vlado Pakan created JBIDE-11430: ----------------------------------- Summary: Multiple selection in Source Editor is not properly reflected in Visual Editor Key: JBIDE-11430 URL: https://issues.jboss.org/browse/JBIDE-11430 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.3.0.Beta2 Environment: Linux 32 bit, JBT Beta2 H134 Reporter: Vlado Pakan Assignee: Yahor Radtsevich Priority: Minor Fix For: 3.3.0.Beta3 1. Create JSF 1.2 Kickstart project 2. Open hello.jsp page 3. Select this part of page source code via mouse: {noformat} <h:outputText value="#{Message.hello_message}" />, <h:outputText value="#{user.name}" />! {noformat} 4. Selection displayed within Visual Editor is proper !correctVisualSelection.png! 5. Select the same text with keyboard 6. Even the same text is selected within Source Editor selection in Visual Editor is different and incorrect. !incorrectVisualSelection.png! After 30 seconds multiple selection appears in Visual Editor but it's really to late. Should be much faster. -- 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, 7 months

3
9
0 / 0

[JBoss JIRA] (JBIDE-12106) JAX-RS RESTful explorer out of sync

by Jaroslav Jankovič (JIRA)

Jaroslav Jankovič created JBIDE-12106: ----------------------------------------- Summary: JAX-RS RESTful explorer out of sync Key: JBIDE-12106 URL: https://issues.jboss.org/browse/JBIDE-12106 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.3.0.CR1 Reporter: Jaroslav Jankovič Assignee: Brian Fitzpatrick Fix For: 3.4.0.M1 -- 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, 7 months

3
13
0 / 0

[JBoss JIRA] (JBIDE-10748) Sometimes there is no update in JAX-RS explorer as it should be

by Jaroslav Jankovič (JIRA)

Jaroslav Jankovič created JBIDE-10748: ----------------------------------------- Summary: Sometimes there is no update in JAX-RS explorer as it should be Key: JBIDE-10748 URL: https://issues.jboss.org/browse/JBIDE-10748 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.3.0.M5 Reporter: Jaroslav Jankovič Assignee: Xavier Coulon Fix For: 3.3.0.Beta1 When replacing annotation by another only by typing it manually, there is no bug. But if you would like to replace it with Copy-Paste way, there is no change in JAX-RS explorer. Clean build won't help as well. -- 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, 7 months

3
16
0 / 0

[JBoss JIRA] (JBDS-2242) Set up installation/update tests on JBDS

by Mickael Istria (JIRA)

Mickael Istria created JBDS-2242: ------------------------------------ Summary: Set up installation/update tests on JBDS Key: JBDS-2242 URL: https://issues.jboss.org/browse/JBDS-2242 Project: Developer Studio (JBoss Developer Studio) Issue Type: Task Security Level: Public (Everyone can see) Components: Build Reporter: Mickael Istria Assignee: Len DiMaggio Fix For: 5.0.2.GA, 6.0.0.M1 We need do define and set up scenarios of installation/updates for JBDS, the same way we set up jobs to ensure installation work for JBT. Len: what scenarios do you think are good to automate? -- 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, 7 months

4
7
0 / 0

[JBoss JIRA] (JBIDE-11065) Replace build.xml by a Maven plugin

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-11065: -------------------------------------- Summary: Replace build.xml by a Maven plugin Key: JBIDE-11065 URL: https://issues.jboss.org/browse/JBIDE-11065 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: Build/Releng Reporter: Mickael Istria Assignee: Mickael Istria In order to improve the build infrastructure and make it easier to share and consumes with all components, we should replace build.xml by a Maven plugin and make it available througn Nexus. It should follow the parent pom versioning. -- 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, 7 months

3
11
0 / 0

[JBoss JIRA] (JBIDE-12061) Cannot install the ESB tools and ESB detector with Juno

by Len DiMaggio (JIRA)

Len DiMaggio created JBIDE-12061: ------------------------------------ Summary: Cannot install the ESB tools and ESB detector with Juno Key: JBIDE-12061 URL: https://issues.jboss.org/browse/JBIDE-12061 Project: Tools (JBoss Tools) Issue Type: Bug Components: SOA Tooling Affects Versions: 3.3.0.CR1 Environment: http://www.qa.jboss.com/binaries/RHDS/updates/development/5.0.0.Beta2.soa... http://download.jboss.org/jbosstools/updates/JBossTools-3.3.0.CR1.core/ Eclipse Juno: Version: 4.2.0 Build id: I20120524-2100 Reporter: Len DiMaggio Assignee: Nick Boldt Priority: Critical Fix For: 3.4.x Cannot complete the install because of a conflicting dependency. Software being installed: JBoss Runtime ESB Detector 1.3.0.v20120522-1702-H4-Beta2-SOA (org.jboss.tools.runtime.esb.detector.feature.feature.group 1.3.0.v20120522-1702-H4-Beta2-SOA) Software currently installed: Eclipse SDK 4.2.0.I20120524-2100 (org.eclipse.sdk.ide 4.2.0.I20120524-2100) Only one of the following can be installed at once: Core Runtime 3.8.0.v20120521-2346 (org.eclipse.core.runtime 3.8.0.v20120521-2346) Core Runtime 3.8.0.v20120511-1333 (org.eclipse.core.runtime 3.8.0.v20120511-1333) Core Runtime 3.7.0.v20110110 (org.eclipse.core.runtime 3.7.0.v20110110) Cannot satisfy dependency: From: Eclipse e4 Rich Client Platform 1.1.0.v20120521-2329-8yFTIGF3GGduEYaFQA2M2RMm (org.eclipse.e4.rcp.feature.group 1.1.0.v20120521-2329-8yFTIGF3GGduEYaFQA2M2RMm) To: org.eclipse.core.runtime [3.8.0.v20120521-2346] Cannot satisfy dependency: From: Eclipse Platform 4.2.0.v20120508-1726-9JF7AHV8FyMteja0CggfF3FfqHnxgnrWaBmfoD (org.eclipse.platform.feature.group 4.2.0.v20120508-1726-9JF7AHV8FyMteja0CggfF3FfqHnxgnrWaBmfoD) To: org.eclipse.rcp.feature.group [4.2.0.v20120403-2031-7IAPA7BrHQicRoOdPwOavbGRB3N3] Cannot satisfy dependency: From: Eclipse RCP 4.2.0.v20120403-2031-7IAPA7BrHQicRoOdPwOavbGRB3N3 (org.eclipse.rcp.feature.group 4.2.0.v20120403-2031-7IAPA7BrHQicRoOdPwOavbGRB3N3) To: org.eclipse.e4.rcp.feature.group [1.1.0.v20120521-2329-8yFTIGF3GGduEYaFQA2M2RMm] Cannot satisfy dependency: From: Eclipse Project SDK 4.2.0.v20120522-2109-7T7mDFDPz-3FdpcTdH3vf9z-X_aZ4Bz-tcBJLHHhcWJnb (org.eclipse.sdk.feature.group 4.2.0.v20120522-2109-7T7mDFDPz-3FdpcTdH3vf9z-X_aZ4Bz-tcBJLHHhcWJnb) To: org.eclipse.platform.feature.group [4.2.0.v20120508-1726-9JF7AHV8FyMteja0CggfF3FfqHnxgnrWaBmfoD] Cannot satisfy dependency: From: Eclipse SDK 4.2.0.I20120524-2100 (org.eclipse.sdk.ide 4.2.0.I20120524-2100) To: org.eclipse.sdk.feature.group [4.2.0.v20120522-2109-7T7mDFDPz-3FdpcTdH3vf9z-X_aZ4Bz-tcBJLHHhcWJnb] Cannot satisfy dependency: From: JBoss Runtime ESB Detector 1.3.0.v20120522-1702-H4-Beta2-SOA (org.jboss.tools.runtime.esb.detector 1.3.0.v20120522-1702-H4-Beta2-SOA) To: bundle org.eclipse.core.runtime [3.7.0,3.8.0) Cannot satisfy dependency: From: JBoss Runtime ESB Detector 1.3.0.v20120522-1702-H4-Beta2-SOA (org.jboss.tools.runtime.esb.detector.feature.feature.group 1.3.0.v20120522-1702-H4-Beta2-SOA) To: org.jboss.tools.runtime.esb.detector [1.3.0.v20120522-1702-H4-Beta2-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

11 years, 7 months

1
1
0 / 0

[JBoss JIRA] (JBIDE-12213) OpenShiftTimeoutException when embedding more cartridges

by Stefan Bunciak (JIRA)

11 years, 7 months

3
8
0 / 0

[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, 7 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, 7 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, 7 months

4
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2012