January 2010 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-5652) Rule Set should not be mandatory

by Burr Sutter (JIRA)

Rule Set should not be mandatory -------------------------------- Key: JBIDE-5652 URL: https://jira.jboss.org/jira/browse/JBIDE-5652 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb Affects Versions: 3.1.0.CR1 Reporter: Burr Sutter Attachments: mandatory_rule_set.jpg The following is accurate for SOA-P5, ESB 4.7 <action class="org.jboss.soa.esb.actions.ContentBasedRouter" name="MyCBR"> <property name="cbrAlias" value="Regex"/> <property name="ruleLanguage"/> <property name="destinations"> <route-to expression=".*blue.*" service-category="AsynchronousESB" service-name="Service2"/> <route-to expression=".*red.*" service-category="AsynchronousESB" service-name="Service3"/> </property> </action> and the ruleset attribute is not required. The wizard (see screenshot) makes the ruleset required. -- 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

6
9
0 / 0

[JBoss JIRA] Created: (JBIDE-5653) Route To Dialog in jboss-esb.xml editor service category, service name

by Burr Sutter (JIRA)

Route To Dialog in jboss-esb.xml editor service category, service name ---------------------------------------------------------------------- Key: JBIDE-5653 URL: https://jira.jboss.org/jira/browse/JBIDE-5653 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb Affects Versions: 3.1.0.CR1 Reporter: Burr Sutter There are two issues with the Route To dialog in the jboss-esb.xml editor. 1) as so as my first keystroke falls in the Destination Name field an error message pops up related to Service Name. Well, I have not even had a chance to type in a Service Name. This is a little bit confusing. 2) Service Category should also be mandatory. -- 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

6
17
0 / 0

[JBoss JIRA] Created: (JBIDE-5623) Create Drools Runtime duplicates jars

by Burr Sutter (JIRA)

Create Drools Runtime duplicates jars ------------------------------------- Key: JBIDE-5623 URL: https://jira.jboss.org/jira/browse/JBIDE-5623 Project: Tools (JBoss Tools) Issue Type: Bug Components: drools Environment: jbdevstudio-win32-3.0.0.v200912111227M-H41-RC1 Reporter: Burr Sutter Attachments: Drools_Runtime_Issue.pdf When you add/create a new drools runtime, pointing it at the jbrules.esb inside of the SOA Platform 5(Beta 1), it adds a lot of jar files. See attached PDF. -- 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
9
0 / 0

[JBoss JIRA] Created: (JBIDE-5654) Aggregator config: timeoutInMillies is deprecated. Use timeoutInMillis in future.

by Burr Sutter (JIRA)

Aggregator config: timeoutInMillies is deprecated. Use timeoutInMillis in future. --------------------------------------------------------------------------------- Key: JBIDE-5654 URL: https://jira.jboss.org/jira/browse/JBIDE-5654 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb Affects Versions: 3.1.0.CR1 Reporter: Burr Sutter Attachments: aggregator_timeout.jpg 11:14:21,536 WARN [Aggregator] Aggregator config: timeoutInMillies is deprecated. Use timeoutInMillis in future. See screenshot and here is the jboss-esb.xml generated source: <action class="org.jboss.soa.esb.actions.Aggregator" name="AggregationHappensHere"> <property name="timeoutInMillies" value="5000"/> </action> -- 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
5
0 / 0

[JBoss JIRA] Created: (JBIDE-5719) Request option for creating new jBPM actions from "File | New" menu

by Max Rydahl Andersen (JIRA)

Request option for creating new jBPM actions from "File | New" menu ------------------------------------------------------------------- Key: JBIDE-5719 URL: https://jira.jboss.org/jira/browse/JBIDE-5719 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: esb Affects Versions: 3.1.0.M4 Environment: JBDS 3.0 M4 Reporter: Aaron Pestel Assignee: Viacheslav Kabanovich Fix For: 3.1.0.CR2 Requesting option to create a new jBPM action and ESB action. Without this, I always have to go to the quickstarts and copy a default action because I can't remember what interfaces each of the actions have to extend, what methods they have to implement, and what the constructor has to be. Would be nice to right-click on source dir in jBPM and ESB project (or from File menu) and select: New | Other | ESB | ESB Action of New | Other | JBoss jBPM | jBPM Action I think it would save new users even more time, because they may not know to go look in the quickstarts to find a template action to copy. -- 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
12
0 / 0

[JBoss JIRA] Created: (JBIDE-5637) Missing Echo Router from jboss-esb.xml editor

by Burr Sutter (JIRA)

Missing Echo Router from jboss-esb.xml editor --------------------------------------------- Key: JBIDE-5637 URL: https://jira.jboss.org/jira/browse/JBIDE-5637 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb Affects Versions: 3.1.0.CR1 Reporter: Burr Sutter in Docs: http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_SOA... 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/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

7
11
0 / 0

[JBoss JIRA] Created: (JBIDE-5700) Simplify project examples update process

by Brian Fitzpatrick (JIRA)

Simplify project examples update process ----------------------------------------- Key: JBIDE-5700 URL: https://jira.jboss.org/jira/browse/JBIDE-5700 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: project-examples Affects Versions: 3.1.0.CR2 Reporter: Brian Fitzpatrick Assignee: Snjezana Peco Currently for the project examples, the user must either create a runtime instance in the tooling that maps to the expected runtime name from the project example or go in and update the references in the Quick Fix dialog by hand in the project properties. Is there any way to make this process simpler? For example, could we match on the type of server instead of the name? How feasible is this type of change? -- 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
20
0 / 0

[JBoss JIRA] Created: (JBIDE-5575) Seam project doesn't expect that the configuration with new <project_name> name could exists.

by Dmitry Geraskov (JIRA)

Seam project doesn't expect that the configuration with new <project_name> name could exists. --------------------------------------------------------------------------------------------- Key: JBIDE-5575 URL: https://jira.jboss.org/jira/browse/JBIDE-5575 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate, Seam Affects Versions: 3.1.0.CR1 Reporter: Dmitry Geraskov Assignee: Dmitry Geraskov Fix For: 3.1.0.CR2 1. Create console configuration test. 2. create seam web project with name test. ERROR: newly created console configuration doesn't appear in hibernate configurations view 3. rename newly created launch file. ERROR: old console configuration is removed from view and new is added. -- 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

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-5543) Nightly builds for trunk/cr2 not running

by Max Rydahl Andersen (JIRA)

Nightly builds for trunk/cr2 not running ---------------------------------------- Key: JBIDE-5543 URL: https://jira.jboss.org/jira/browse/JBIDE-5543 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng Reporter: Max Rydahl Andersen Assignee: Nick Boldt Priority: Blocker Fix For: 3.1.0.CR2 http://download.jboss.org/jbosstools/builds/nightly/trunk/latestBuild.html says the last build was the 18th. And no builds seem to be listed at http://hudson.qa.jboss.com/hudson/view/DevStudio/ either. -- 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
8
0 / 0

[JBoss JIRA] Created: (JBDS-968) Can't update JBDS M4 with JBT CR1 from update site.

by Yura Zhishko (JIRA)

Can't update JBDS M4 with JBT CR1 from update site. --------------------------------------------------- Key: JBDS-968 URL: https://jira.jboss.org/jira/browse/JBDS-968 Project: JBoss Developer Studio Issue Type: Bug Components: Build Affects Versions: 3.0.0.M4, 3.0.0.CR1 Environment: jbdevstudio-eap-win32-3.0.0.v200911161447M-H94-M4 Reporter: Yura Zhishko Assignee: Denis Golovin Priority: Critical 1) Install studio version from environment description. 2) Help -> Install New Software 3) Add http://download.jboss.org/jbosstools/updates/nightly/trunk/ to update list 4) Select all except Integration (screenshot-1) 5) Press Next I've got unsatisfied dependency: Cannot complete the install because one or more required items could not be found. Software being installed: JBoss Maven SDK 1.0.0.v200912010124N-H1-RC1 (org.jboss.tools.maven.sdk.feature.feature.group 1.0.0.v200912010124N-H1-RC1) Missing requirement: JBoss Maven Core 1.0.0.v200912010124N-H1-RC1 (org.jboss.tools.maven.core 1.0.0.v200912010124N-H1-RC1) requires 'bundle org.maven.ide.components.maven_model_edit 0.0.0' but it could not be found Cannot satisfy dependency: From: JBoss Maven Integration 1.0.0.v200912010124N-H1-RC1 (org.jboss.tools.maven.feature.feature.group 1.0.0.v200912010124N-H1-RC1) To: org.jboss.tools.maven.core [1.0.0.v200912010124N-H1-RC1] Cannot satisfy dependency: From: JBoss Maven SDK 1.0.0.v200912010124N-H1-RC1 (org.jboss.tools.maven.sdk.feature.feature.group 1.0.0.v200912010124N-H1-RC1) To: org.jboss.tools.maven.feature.feature.group [1.0.0.v200912010124N-H1-RC1] 6) I've excluded JBoss Maven SDK from build. During JBT updating next errors occur (see Error screenshot) -- 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

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