May 2010 - jbosstools-issues - Jboss List Archives

[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

[JBoss JIRA] Created: (JBIDE-5900) BPEL validator noisy in logs

by Max Rydahl Andersen (JIRA)

BPEL validator noisy in logs ---------------------------- Key: JBIDE-5900 URL: https://jira.jboss.org/jira/browse/JBIDE-5900 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpm Affects Versions: 3.1.0.CR2 Reporter: Max Rydahl Andersen Assignee: Brian Fitzpatrick Priority: Blocker Fix For: 3.1.0.CR2, 3.1.0.GA I'm seeing "Validator Startup 862ms" from org.eclipse.bpel.validator in the Error log (event though I have zero BPEL enabled projects). We should not be logging timing stuff to the error log in GA release. -- 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
6
0 / 0

[JBoss JIRA] Created: (JBIDE-5621) Clean up blank prefs page for BPEL

by Brian Fitzpatrick (JIRA)

Clean up blank prefs page for BPEL ---------------------------------- Key: JBIDE-5621 URL: https://jira.jboss.org/jira/browse/JBIDE-5621 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: bpm Affects Versions: 3.1.0.CR1 Reporter: Brian Fitzpatrick Assignee: Feng Qian Fix For: 3.1.0.GA This is a sub-task for https://jira.jboss.org/jira/browse/JBIDE-5610 There's a root BPEL preference page that has nothing on it. We should avoid blank preference pages if at all possible. Even if all we do is add a label to the page like "Expand the tree to edit preferences for the BPEL Editor." -- 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

2
7
0 / 0

[JBoss JIRA] Created: (JBIDE-6046) ESB Editor for JMS Router missing fields or has wrong field name

by Brian Fitzpatrick (JIRA)

ESB Editor for JMS Router missing fields or has wrong field name ---------------------------------------------------------------- Key: JBIDE-6046 URL: https://jira.jboss.org/jira/browse/JBIDE-6046 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb Affects Versions: 3.1.0.GA Reporter: Brian Fitzpatrick Fix For: 3.2.next, 3.1.1 This came from JBDS-1156 The JMS Router Action does not have a field on the screen for JNDI Name: Need to add via source view: <property name="jndiName" value="queue/quickstart_jms_router_routeTo"/> The credential name is misspelled, so need to add: <property name="security-credential" value="guest"/> -- 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

4
11
0 / 0

[JBoss JIRA] Created: (JBIDE-5916) Wrong Compiler Compliance Level set when creating new ESB Project

by Vlado Pakan (JIRA)

Wrong Compiler Compliance Level set when creating new ESB Project ------------------------------------------------------------------ Key: JBIDE-5916 URL: https://jira.jboss.org/jira/browse/JBIDE-5916 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb Environment: JBDS 3.0.0v201002190339M-H173-CR2 Java Sun JDK 1.6.0_16-b01 JBoss [SOA] 5.0.0.GA_SOA (build: SVNTag=5.0.0.GA_SOA date=201002151345) Reporter: Vlado Pakan Fix For: 3.1.0.CR2 When new ESB Project is created (File > New > Others > ESB Project) this project has set Compiler Compliance Level to 1.5 (Project > Properties > Java Compiler) even when only Java JDK 1.6 Runtime is specified within workspace. Then when user adds new ESB Action to this project (File > New > Others > ESB Action) it generates new class with this content (JBoss ESB Runtime jas to be added to project classpath): import org.jboss.soa.esb.actions.AbstractActionPipelineProcessor; import org.jboss.soa.esb.helpers.ConfigTree; import org.jboss.soa.esb.actions.ActionProcessingException; import org.jboss.soa.esb.message.Message; public class EsbAction extends AbstractActionPipelineProcessor { protected ConfigTree _config; public EsbAction(ConfigTree config) { _config = config; } @Override public Message process(Message message) throws ActionProcessingException { //ADD CUSTOM ACTION CODE HERE return message; } } And compiler is complaining about @Override annotation on method process(Message) displaying this error: The method process(Message) of type EsbAction must override a superclass method Either when Compiler Compliance level is set to 1.6 or Project Facets Java version is set to 6.0 (Project Properties > Project Facets > Java) error disappear. I think it should work in the way that when user creates new EBS Action it should be created without errors so Compiler Compliance Level or Project Facets Java should be set properly. -- 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

6
41
0 / 0

[JBoss JIRA] Created: (JBDS-943) Does not run on Mac after installing with the attached error

by Jim Tyrrell (JIRA)

Does not run on Mac after installing with the attached error ------------------------------------------------------------ Key: JBDS-943 URL: https://jira.jboss.org/jira/browse/JBDS-943 Project: JBoss Developer Studio Issue Type: Bug Affects Versions: 3.0.0.M4 Environment: Mac Snow Leopard Macintosh-75:Applications jimtyrrell$ java -version java version "1.6.0_15" Java(TM) SE Runtime Environment (build 1.6.0_15-b03-219) Java HotSpot(TM) 64-Bit Server VM (build 14.1-b02-90, mixed mode) Reporter: Jim Tyrrell Attachments: Screen shot 2009-11-10 at 7.57.16 PM.png Clicking on JBoss Developer Studio.app results in the attached error. -- 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

5
15
0 / 0

[JBoss JIRA] Created: (JBDS-875) BRMS pluging, deleting file not working

by Jehudi Castro (JIRA)

BRMS pluging, deleting file not working --------------------------------------- Key: JBDS-875 URL: https://jira.jboss.org/jira/browse/JBDS-875 Project: JBoss Developer Studio Issue Type: Bug Reporter: Jehudi Castro see GUVNOR-459 -- 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

4
14
0 / 0

[JBoss JIRA] Created: (JBIDE-6286) Inconsistent deploy folder in server setting

by Jiri Peterka (JIRA)

Inconsistent deploy folder in server setting -------------------------------------------- Key: JBIDE-6286 URL: https://jira.jboss.org/jira/browse/JBIDE-6286 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.1.0.GA Environment: JBT 3.1.0 GA, JDK 1.6 Reporter: Jiri Peterka Fix For: 3.2.next When there is selected custom deploy folder on Runtime Server properties -> Deployment tab, in server properties there is still metedata (see screenshots) Steps: 1. Add Jboss Runtime and create server 2. Click on Server in Servers view 3. On Deployment tab switch to "Use Custom deploy folder" 4. Save setting 5. Click on Servers view 6. Click on Server -> Properties (context menu) 7. See there is metadata dir set as location ASSERT: Should be custom ASSERT2: It should be possible to use "Switch Location" to switch location to custom folder -- 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
6
0 / 0

[JBoss JIRA] Created: (JBIDE-5878) Archives .packages configuration cannot be used without modifications to build archive with ant inside eclipse

by Denis Golovin (JIRA)

Archives .packages configuration cannot be used without modifications to build archive with ant inside eclipse -------------------------------------------------------------------------------------------------------------- Key: JBIDE-5878 URL: https://jira.jboss.org/jira/browse/JBIDE-5878 Project: Tools (JBoss Tools) Issue Type: Bug Components: Archives Affects Versions: 3.1.0.CR2 Reporter: Denis Golovin Assignee: Rob Stryker By default packages/package@todir attribute is set to /${project-name} and that works only when archive is built by using context menu on Archives View. If you create build.xml and run it by eclipse ant launcher it fails with error like Error adding child node jarName.jar [GenerateArchives] org.jboss.ide.eclipse.archives.core.model.ArchivesModelException: Error adding child node myJar.jar [GenerateArchives] at org.jboss.ide.eclipse.archives.core.model.internal.ArchiveNodeImpl.addChild(ArchiveNodeImpl.java:273) [GenerateArchives] at org.jboss.ide.eclipse.archives.core.util.ModelUtil.fillArchiveModel(ModelUtil.java:216) [GenerateArchives] at org.jboss.ide.eclipse.archives.core.model.ArchivesModel.registerProject(ArchivesModel.java:194) [GenerateArchives] at org.jboss.ide.eclipse.archives.core.model.ArchivesModel.registerProject(ArchivesModel.java:170) [GenerateArchives] at org.jboss.ide.eclipse.archives.core.ant.GenerateArchivesTask.execute(GenerateArchivesTask.java:63) [GenerateArchives] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288) [GenerateArchives] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [GenerateArchives] at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) [GenerateArchives] at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) [GenerateArchives] at java.lang.reflect.Method.invoke(Unknown Source) [GenerateArchives] at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105) [GenerateArchives] at org.apache.tools.ant.Task.perform(Task.java:348) [GenerateArchives] at org.apache.tools.ant.Target.execute(Target.java:357) [GenerateArchives] at org.apache.tools.ant.Target.performTasks(Target.java:385) [GenerateArchives] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329) [GenerateArchives] at org.apache.tools.ant.Project.executeTarget(Project.java:1298) [GenerateArchives] at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41) [GenerateArchives] at org.eclipse.ant.internal.ui.antsupport.EclipseDefaultExecutor.executeTargets(EclipseDefaultExecutor.java:32) [GenerateArchives] at org.apache.tools.ant.Project.executeTargets(Project.java:1181) [GenerateArchives] at org.eclipse.ant.internal.ui.antsupport.InternalAntRunner.run(InternalAntRunner.java:423) [GenerateArchives] at org.eclipse.ant.internal.ui.antsupport.InternalAntRunner.main(InternalAntRunner.java:137) -- 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
6
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 May 2010