October 2010 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-7220) Recent AS versions should support esb 4.9 module type

by Rob Stryker (JIRA)

Recent AS versions should support esb 4.9 module type ----------------------------------------------------- Key: JBIDE-7220 URL: https://jira.jboss.org/browse/JBIDE-7220 Project: Tools (JBoss Tools) Issue Type: Task Components: JBossAS Affects Versions: 3.2.0.Beta1 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.2.0.Beta2 -- 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

15 years, 4 months

4
8
0 / 0

[JBoss JIRA] Created: (JBDS-1364) ModeShape Connection profile default URL is wrong for EDS.

by John Doyle (JIRA)

ModeShape Connection profile default URL is wrong for EDS. ---------------------------------------------------------- Key: JBDS-1364 URL: https://jira.jboss.org/browse/JBDS-1364 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: SOA Platform Affects Versions: 4.0.0.M2 Reporter: John Doyle Assignee: John Doyle The default URL in the ModeShape connection profile is currently: jdbc:jcr:http://localhost:8080/modeshape-rest/repository/default For EDS it should be: jdbc:jcr:http://localhost:8080/modeshape-rest/repository/eds -- 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

15 years, 4 months

5
11
0 / 0

[JBoss JIRA] Created: (JBDS-1381) Should EAP 5.0 be listed as EAP 5.x or do we need more versions ?

by Max Andersen (JIRA)

Should EAP 5.0 be listed as EAP 5.x or do we need more versions ? ----------------------------------------------------------------- Key: JBDS-1381 URL: https://jira.jboss.org/browse/JBDS-1381 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: servers Reporter: Max Andersen Assignee: Rob Stryker Priority: Blocker Fix For: 4.0.0.Beta2 Now that EAP 5.1, EPP 5.1 and SOA-P 5.1 is coming out should we label our driver EAP 5.x instead of EAP 5.0 ? Will it work ? Or should we create a new set of servers ? Is there any differences we need to cater for ? diferent startup options etc. ? -- 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

15 years, 4 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-7296) Remote System Deployment: classToLaunch cannot be null

by Burr Sutter (JIRA)

Remote System Deployment: classToLaunch cannot be null ------------------------------------------------------ Key: JBIDE-7296 URL: https://jira.jboss.org/browse/JBIDE-7296 Project: Tools (JBoss Tools) Issue Type: Bug Components: Archives Environment: Win7 Java 1.6 32-bit JVM and JBDS 4.0 M2 Reporter: Burr Sutter Assignee: Rob Stryker Selecting Start on the Server results in: An internal error occurred during: "Starting JBoss 6.0 M5 Remote Server". classToLaunch cannot be null See screenshots -- 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

15 years, 4 months

4
10
0 / 0

[JBoss JIRA] Created: (JBIDE-5645) Missing requirements description for Project Examples

by Jiri Peterka (JIRA)

Missing requirements description for Project Examples ----------------------------------------------------- Key: JBIDE-5645 URL: https://jira.jboss.org/jira/browse/JBIDE-5645 Project: Tools (JBoss Tools) Issue Type: Bug Components: project-examples Affects Versions: 3.1.0.CR1 Environment: JBDS 3.0.0 CR1, build 50, Linux 32, Sun JDK 6.0 Reporter: Jiri Peterka Fix For: 3.1.0.CR2 There are many project examples but missing requirement information. At least there should be detailed java and runtime information for each example to provide developers information howto make it running without lots of time spent with each example. For Example there is lot of complication when you want to run examples on SOA 5 and Sun JDK6. Maybe some examples reorganization according to runtime would be helpful as well. -- 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

15 years, 4 months

7
69
0 / 0

[JBoss JIRA] Created: (JBIDE-7341) SOA-P 5.1 ER2 jbpm runtime is invalid for creating jBPM Project

by Jiri Peterka (JIRA)

SOA-P 5.1 ER2 jbpm runtime is invalid for creating jBPM Project --------------------------------------------------------------- Key: JBIDE-7341 URL: https://jira.jboss.org/browse/JBIDE-7341 Project: Tools (JBoss Tools) Issue Type: Bug Components: jbpm Affects Versions: 3.2.0.Beta1 Environment: JBDS 4.0.0.beta1 #47, SOA-P 5.1.ER2, Linux 64 Reporter: Jiri Peterka Priority: Blocker Fix For: 3.2.0.Beta2 1. New workspace 2. Create jbpm3 project 3. Try to define jBPM3 runtime from EAP 5.1.0.ER2 ($SOA_HOME/jbpm-jpdl/) ERROR: This location does not contain a valid jBPM 3 runtime, please retry After finishing, there is lot of errors related to unresolved types. -- 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

15 years, 4 months

2
5
0 / 0

[JBoss JIRA] Created: (JBIDE-7302) Problem with Refactor>Rename field in JSF KickStart project when "Rename getter ...", "Rename setter ..." are checked

by Snjezana Peco (JIRA)

Problem with Refactor>Rename field in JSF KickStart project when "Rename getter ...", "Rename setter ..." are checked ---------------------------------------------------------------------------------------------------------------------- Key: JBIDE-7302 URL: https://jira.jboss.org/browse/JBIDE-7302 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.2.0.M2 Environment: JBT trunk, Windows XP, JDK 1.6.0_21 Reporter: Snjezana Peco Assignee: Alexey Kazakov Steps to reproduce: - create a JSF KickStart project - start the JBoss AS and verify that the application runs correctly - right-click the name property and call Refactor>Rename - rename the property to name1, check "Update References", "Rename getter ...", "Rename setter ..." - click OK You will get a NPE (attached is RefactorRename.log). After fixing the NPE (the fix is trivial; the NPE was introduced a few days ago), you will face the following issues: - the GWT Rename participants fail and are disabled (this is not a JBT problem; attached is GWTRefactorRename.log) - hello.jsp and inputUserName.jsp contain the user.name11 value. The problem can't be reproduced in JBDS 4.0.0.Beta1. The problem can be reproduced using the JBT trunk with and without GWT plugins. -- 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

15 years, 4 months

4
6
0 / 0

[JBoss JIRA] Created: (JBIDE-1304) Docbook XML editor

by Denis Golovin (JIRA)

Docbook XML editor ------------------ Key: JBIDE-1304 URL: http://jira.jboss.com/jira/browse/JBIDE-1304 Project: JBoss Tools Issue Type: Feature Request Affects Versions: 2.0.0.CR1 Reporter: Denis Golovin Assigned To: Denis Golovin Fix For: LATER Use current VPE as editor for docbook.xml files. There will problem with editing files that uses ENTITY definition but for plain files it should works fine. -- 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

15 years, 4 months

4
18
0 / 0

[JBoss JIRA] Created: (JBIDE-7042) Clarify MacOSX 10.5 support

by Dominik Pospisil (JIRA)

Clarify MacOSX 10.5 support --------------------------- Key: JBIDE-7042 URL: https://jira.jboss.org/browse/JBIDE-7042 Project: Tools (JBoss Tools) Issue Type: Task Affects Versions: 3.2.0.M2 Reporter: Dominik Pospisil Assignee: Dominik Pospisil Priority: Blocker Fix For: 3.2.0.Beta As we dropped JDK 1.5 support and we do not support 64-bit JVM on MacOSX it seems we do not have any bits which could be ran on Mac OSX 10.5 (Leopard). Clarify the status. -- 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

15 years, 4 months

5
23
0 / 0

[JBoss JIRA] Created: (JBIDE-7451) Vpe templates for rich output

by Maxim Areshkau (JIRA)

Vpe templates for rich output ----------------------------- Key: JBIDE-7451 URL: https://jira.jboss.org/browse/JBIDE-7451 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Visual Page Editor Templates Affects Versions: 3.2.0.Beta1 Reporter: Maxim Areshkau Assignee: Maxim Areshkau Fix For: 3.2.0.Beta2 Attachments: Screen shot 2010-10-28 at 10.50.37 PM.png Vpe templates for rich output -- 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

15 years, 4 months

4
10
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 October 2010