July 2010 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-6559) NIGHTLY (6/29/2010): JBoss AS Plugin Has strange artifacts showing up in it

by Lincoln Baxter III (JIRA)

NIGHTLY (6/29/2010): JBoss AS Plugin Has strange artifacts showing up in it --------------------------------------------------------------------------- Key: JBIDE-6559 URL: https://jira.jboss.org/browse/JBIDE-6559 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Reporter: Lincoln Baxter III Assignee: Rob Stryker Attachments: screenshot2.png Using eclipse 3.6 clean install and nightly jboss AS 6 install - attaching screenshot -- 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, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-6332) "Path for project must have only one segment" when working with Project Archive

by Shu-Wei Tan (JIRA)

"Path for project must have only one segment" when working with Project Archive ------------------------------------------------------------------------------- Key: JBIDE-6332 URL: https://jira.jboss.org/browse/JBIDE-6332 Project: Tools (JBoss Tools) Issue Type: Bug Components: Archives Affects Versions: 3.1.0.GA Environment: XP SP3, JBoss 5.1.0 GA, Eclipse Galileo, Seam 2.2.0, JBoss Tools 3.1.0 Reporter: Shu-Wei Tan Assignee: Rob Stryker I have my workspace here: e:\test and I have a Seam project here: e:\test\sub\Proj e:\test\sub\Proj-ear e:\test\sub\Proj-ejb e:\test\sub\Proj-test When I create a Project Archive using the default values, everything I try to work with the archive I get this error: "Path for project must have only one segment" If my project lives directly in the test folder then it works without errors -- 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, 9 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-6526) Make deployable vs Make Undeployable = strange text

by Rob Stryker (JIRA)

Make deployable vs Make Undeployable = strange text --------------------------------------------------- Key: JBIDE-6526 URL: https://jira.jboss.org/browse/JBIDE-6526 Project: Tools (JBoss Tools) Issue Type: Task Components: JBossAS Affects Versions: 3.1.1 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.2.0.M2 I suggest: Mark as Deployable Unmark as Deployable -- 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, 9 months

2
5
0 / 0

[JBoss JIRA] Created: (JBIDE-6585) Server View still showing toStrings() on xml / ports / etc

by Rob Stryker (JIRA)

Server View still showing toStrings() on xml / ports / etc ---------------------------------------------------------- Key: JBIDE-6585 URL: https://jira.jboss.org/browse/JBIDE-6585 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel, JBossAS Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.2.0.M2 Some BPEL label provider is returning a toString() on an object it should have no idea about -- 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, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBIDE-5865) Bahaviour of "Make Deployable" and "Make Undeployable" is not consistent

by Dominik Pospisil (JIRA)

Bahaviour of "Make Deployable" and "Make Undeployable" is not consistent ------------------------------------------------------------------------ Key: JBIDE-5865 URL: https://jira.jboss.org/jira/browse/JBIDE-5865 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.CR2 Reporter: Dominik Pospisil When "Make Deployable" is applied to a resource, and a server is running, it gets immediatelly deployed. When "Make Undeployable" is applied to a resource on running server, it is correctly removed from a list of resources available for deployment, but it is not undeployed. Make Deployable/Undeployable should: 1) not deploy/undeploy resource immediately (preferably) 2) or both deploy/undeploy immediately. -- 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, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-6312) JBoss Server doesn't reflect setting on Server Deployment tab

by Jiri Peterka (JIRA)

JBoss Server doesn't reflect setting on Server Deployment tab ------------------------------------------------------------- Key: JBIDE-6312 URL: https://jira.jboss.org/browse/JBIDE-6312 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.1.0.GA Environment: JBT 3.1.0 GA Reporter: Jiri Peterka Fix For: 3.2.next Steps: 1. Have EAP 5.0 Server defined in Servers view 2. In Local Deployment (Double click on server -> Deployment tab) set workspace metadata as deploy server 3. Start server, deploy, undeploy 4. Stop server 5 Set custom folder as default deploy folder, start server, deploy Change isn't reflected. Application isn't deployed according custom folder selection. My experience is this setting works very unreliably if ever. -- 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, 9 months

3
11
0 / 0

[JBoss JIRA] Created: (JBIDE-6525) EAP 5.0 server defaults server deploy location to normal server deploy folder, but eap 5.0 contains AS 5.1

by Rob Stryker (JIRA)

EAP 5.0 server defaults server deploy location to normal server deploy folder, but eap 5.0 contains AS 5.1 ---------------------------------------------------------------------------------------------------------- Key: JBIDE-6525 URL: https://jira.jboss.org/browse/JBIDE-6525 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.2.0.M2 Reporter: Rob Stryker Assignee: Rob Stryker EAP 5.0 contains AS 5.1 and should default to workspace metadata as publish location. -- 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, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBIDE-6357) NPE error when create a correlation

by Feng Qian (JIRA)

NPE error when create a correlation ----------------------------------- Key: JBIDE-6357 URL: https://jira.jboss.org/browse/JBIDE-6357 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpm Affects Versions: 3.1.0.GA Reporter: Feng Qian Assignee: Feng Qian Fix For: 3.1.2 when click the '+' button to add a correlation, you will get the NPE error java.lang.NullPointerException at org.eclipse.bpel.model.util.ReconciliationHelper.updateCorrelationSetNameReferences(ReconciliationHelper.java:401) -- 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, 9 months

2
8
0 / 0

[JBoss JIRA] Created: (JBIDE-6230) Process is not removed from ODE deployment editor model if BPEL process file is deleted from project

by Robert (Bob) Brodt (JIRA)

Process is not removed from ODE deployment editor model if BPEL process file is deleted from project ---------------------------------------------------------------------------------------------------- Key: JBIDE-6230 URL: https://jira.jboss.org/jira/browse/JBIDE-6230 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpm Reporter: Robert (Bob) Brodt Assignee: Robert (Bob) Brodt Fix For: 3.2.next Like the title says: if a bpel file is deleted from the workspace, the process entry is never removed from the ODE deployment model. This is part of a bigger problem having to do with refactoring: see https://jira.jboss.org/jira/browse/JBIDE-6018 and https://jira.jboss.org/jira/browse/JBIDE-5027 but at the very least, the deployment model should be kept in sync if bpel files are created or deleted. Also, if the name of the bpel process is changed, the deployment editor assumes it is a new process and adds it to the model. This is not tragic, but the user must then re-select the inbound and outbound ports. -- 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, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-6154) NewFileWizard for BPEL should add service and binding to WSDL artifacts

by Robert (Bob) Brodt (JIRA)

NewFileWizard for BPEL should add service and binding to WSDL artifacts ----------------------------------------------------------------------- Key: JBIDE-6154 URL: https://jira.jboss.org/jira/browse/JBIDE-6154 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: bpm Affects Versions: 3.1.0.GA Reporter: Robert (Bob) Brodt Assignee: Feng Qian Fix For: 3.2.next The New BPEL Process File wizard should add the <service> and <binding> elements to the generated WSDL. A new wizard page needs to be built which allows the user to enter: 1. the service name (default is same as BPEL Process Name) 2. port name (default is same as service name + "Port") 3. service address (default is http://localhost:8080/<service_name>) 4. binding protocol (SOAP or HTTP) The goal is to have the New File Wizard build a complete BPEL process and WSDL which can immediately be deployed to and run with the riftsaw (ODE) runtime. -- 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, 9 months

3
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 July 2010