January 2010 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-5550) ESB Editor - remove cacheScript from ScriptingAction UI

by Brian Fitzpatrick (JIRA)

ESB Editor - remove cacheScript from ScriptingAction UI ------------------------------------------------------- Key: JBIDE-5550 URL: https://jira.jboss.org/jira/browse/JBIDE-5550 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb Affects Versions: 3.1.0.GA Reporter: Brian Fitzpatrick Assignee: Viacheslav Kabanovich Fix For: 3.1.0.GA For the ScriptingAction UI, after checking with the ESB team, it appears that "cacheScript" is not a valid property. It's valid for GroovyActionProcessor, but not for Scripting Action. Can we remove it? >From Kevin Conner: "The only cacheScript I can find is within GroovyActionProcessor. It defaults to true but will force a new script to be created if it is set to false. This doesn't apply to the ScriptingAction." -- 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

16 years, 2 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-5489) For BPMProcessor in ESB Editor, add some

by Brian Fitzpatrick (JIRA)

For BPMProcessor in ESB Editor, add some ----------------------------------------- Key: JBIDE-5489 URL: https://jira.jboss.org/jira/browse/JBIDE-5489 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: esb Affects Versions: 3.1.0.GA Reporter: Brian Fitzpatrick Assignee: Viacheslav Kabanovich Fix For: 3.1.0.GA For the BPM Processor action in the JBoss ESB Editor, there are three values currently available for the Command property: NewProcessInstanceCommand, StartProcessCommand, and CancelProcessInstanceCommand. (Based on the ESB 4.7 Programmer's Reference) Can we add these as choices in a drop-down to the Command property? -- 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

16 years, 2 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-5492) SOAP Proxy Action "wsdlTransform" property should be linked to Smooks Editor in ESB Editor

by Brian Fitzpatrick (JIRA)

SOAP Proxy Action "wsdlTransform" property should be linked to Smooks Editor in ESB Editor ------------------------------------------------------------------------------------------ Key: JBIDE-5492 URL: https://jira.jboss.org/jira/browse/JBIDE-5492 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb Affects Versions: 3.1.0.GA Reporter: Brian Fitzpatrick Assignee: Viacheslav Kabanovich Fix For: 3.1.0.GA In the JBoss ESB Editor where configuring a SOAP Proxy Action, the "wsdlTransform" property should be linked to the Smooks Configuration 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

16 years, 2 months

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-5490) Change "Timeout in Millies" to something easier to translate

by Brian Fitzpatrick (JIRA)

Change "Timeout in Millies" to something easier to translate ------------------------------------------------------------ Key: JBIDE-5490 URL: https://jira.jboss.org/jira/browse/JBIDE-5490 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb Affects Versions: 3.1.0.GA Reporter: Brian Fitzpatrick Assignee: Viacheslav Kabanovich Priority: Minor Fix For: LATER In the JBoss ESB Editor when editing the properties of an Aggregator action, you see "Timeout in Millies" as one of the properties. Though I understand "Millies" is milliseconds, this may not be immediately apparent to people localizing strings. Can we change "Timeout in Millies" to "Timeout in Milliseconds" or "Timeout (Milliseconds)"? -- 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

16 years, 2 months

3
3
0 / 0

[JBoss JIRA] Created: (JBDS-1082) JBoss EWP 5.0.0 not recogized as EAP instance

by Dominik Pospisil (JIRA)

JBoss EWP 5.0.0 not recogized as EAP instance ---------------------------------------------- Key: JBDS-1082 URL: https://jira.jboss.org/jira/browse/JBDS-1082 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: installer, servers Affects Versions: 3.0.0.CR1 Reporter: Dominik Pospisil JBoss EWP 5.0 CR1 is detected by installer as community JBoss AS 5.0 servner, not EAP. Bundled Seam is not registered. -- 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

16 years, 2 months

3
5
0 / 0

[JBoss JIRA] Created: (JBDS-1045) No ESB runtime is configured after JBDS installation

by Dominik Pospisil (JIRA)

No ESB runtime is configured after JBDS installation ---------------------------------------------------- Key: JBDS-1045 URL: https://jira.jboss.org/jira/browse/JBDS-1045 Project: JBoss Developer Studio Issue Type: Bug Components: installer Affects Versions: 3.0.0.CR1 Reporter: Dominik Pospisil When a user registers one or more SOA platform instances during instalation, no associated ESB runtime is configured. -- 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

16 years, 2 months

4
7
0 / 0

[JBoss JIRA] Created: (JBIDE-5380) jBPM deployment wizard - both test connection and deployment failing

by Dominik Pospisil (JIRA)

jBPM deployment wizard - both test connection and deployment failing --------------------------------------------------------------------- Key: JBIDE-5380 URL: https://jira.jboss.org/jira/browse/JBIDE-5380 Project: Tools (JBoss Tools) Issue Type: Bug Components: jbpm Affects Versions: 3.1.0.M4 Environment: JBoss Tools - 3.1.0.v200910281724M-H247-M4 - Linux x86_64 SOA-P 5.0.0.ER4 Reporter: Dominik Pospisil Both test connection and deployment to bundled SOA-P 5.0.0.ER4 jBPM runtime fails. Failure message: An exception happened with testing server connection. Reason: An unexpected exception caused the test connection opertaion to fail Checked that jbpm console is up and running. Also tried unsecure jbpm console, no difference. No other error messages/logs found. -- 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

16 years, 2 months

5
13
0 / 0

[JBoss JIRA] Created: (JBIDE-5624) New Drools4 project generated incorrectly

by Dominik Pospisil (JIRA)

New Drools4 project generated incorrectly ----------------------------------------- Key: JBIDE-5624 URL: https://jira.jboss.org/jira/browse/JBIDE-5624 Project: Tools (JBoss Tools) Issue Type: Bug Components: drools Affects Versions: 3.1.0.CR1 Environment: JBDS 3.1 CR1 SOA-P 4.3 Reporter: Dominik Pospisil Priority: Critical After creating new Drools project for drools4 runtime, the project is generated incorrectly. File ProcessTest.java contains RuleFlowTest class File DroolsTest..java contains ProcessTest class Steps to reproduce: 1) Create new Drools4 project with a Drools4 runtime 2) Turn all features on, finish -- 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

16 years, 2 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-5554) ESB Editor - Notifier action needs ability to add targets to a notifier list

by Brian Fitzpatrick (JIRA)

ESB Editor - Notifier action needs ability to add targets to a notifier list ---------------------------------------------------------------------------- Key: JBIDE-5554 URL: https://jira.jboss.org/jira/browse/JBIDE-5554 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb Affects Versions: 3.1.0.GA Reporter: Brian Fitzpatrick Assignee: Viacheslav Kabanovich For the Notifier action, we need the ability to add targets to a notifier list. For example, a NotificationList for an error notifier (see page 119 of Progammer's Reference for ESB 4.7): <NotificationList type="err"> <target class="NotifyConsole" /> <target class="NotifyFiles" > <file name="@results.dir(a)/badresult.log" /> </target> </NotificationList> I'm not sure how we'd implement this for 3.1 since it's pretty detailed - there are multiple types of targets for the NotifyList: * NotifyConsole * NotifyFiles * NotifySQLTable * NotifyFTP * NotifyQueues * NotifyTopics * NotifyEmail I'm open to suggestions here. :) -- 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

16 years, 2 months

4
11
0 / 0

[JBoss JIRA] Created: (JBIDE-5549) ESB Editor - Smooks Action - need clarification on excludeNonSerializables and messageProfile

by Brian Fitzpatrick (JIRA)

ESB Editor - Smooks Action - need clarification on excludeNonSerializables and messageProfile --------------------------------------------------------------------------------------------- Key: JBIDE-5549 URL: https://jira.jboss.org/jira/browse/JBIDE-5549 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb Affects Versions: 3.1.0.GA Reporter: Brian Fitzpatrick Assignee: Tom Fennelly Hey Tom... Either the "excludeNonSerializables" and "messageProfile" properties are missing from the doc, or they are extras in the UI. If missing from the docs, what do they do? When I asked Kevin, he said I should ask you. :) Should we include them in the ESB editor as optional properties? -- 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

16 years, 2 months

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