February 2010 - jbosstools-issues

[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, 4 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, 4 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, 4 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, 4 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, 4 months

3
20
0 / 0

[JBoss JIRA] Commented: (JBIDE-5895) Tools: signature String method() - Not found couse exists.

by Alexey Kazakov (JIRA)

[ https://jira.jboss.org/jira/browse/JBIDE-5895?page=com.atlassian.jira.plu... ] Alexey Kazakov commented on JBIDE-5895: --------------------------------------- Please provide more info. Are you using JBoss Tools? Which version? Where do you see this marker? Could you attache any screenshot? > Tools: signature String method() - Not found couse exists. > ---------------------------------------------------------- > > Key: JBIDE-5895 > URL: https://jira.jboss.org/jira/browse/JBIDE-5895 > Project: Tools (JBoss Tools) > Issue Type: Bug > Environment: WinXP Eclipse WTP Build id: 20090920-1017 > Reporter: Peter Rader > Priority: Critical > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > After checkout jsf-pages marks methods as "missing". > i.e.: <h:commandButton action="#{enexus.einloggen}" value="Einloggen" /> > told me that "Method must have signature "String method()" but has signature "String method()"" > Ever i pres Ctrl+LmB to enexus, editor jumps to implementation "public String einloggen()". > -> So this error-message is wrong. > Is critical why i cant build projects contains errors. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Moved: (JBIDE-5895) Tools: signature String method() - Not found couse exists.

by Nick Belaevski (JIRA)

[ https://jira.jboss.org/jira/browse/JBIDE-5895?page=com.atlassian.jira.plu... ] Nick Belaevski moved RF-8431 to JBIDE-5895: ------------------------------------------- Project: Tools (JBoss Tools) (was: RichFaces) Key: JBIDE-5895 (was: RF-8431) Security: (was: Public) > Tools: signature String method() - Not found couse exists. > ---------------------------------------------------------- > > Key: JBIDE-5895 > URL: https://jira.jboss.org/jira/browse/JBIDE-5895 > Project: Tools (JBoss Tools) > Issue Type: Bug > Environment: WinXP Eclipse WTP Build id: 20090920-1017 > Reporter: Peter Rader > Priority: Critical > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > After checkout jsf-pages marks methods as "missing". > i.e.: <h:commandButton action="#{enexus.einloggen}" value="Einloggen" /> > told me that "Method must have signature "String method()" but has signature "String method()"" > Ever i pres Ctrl+LmB to enexus, editor jumps to implementation "public String einloggen()". > -> So this error-message is wrong. > Is critical why i cant build projects contains errors. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBDS-1110) reconfigure .htaccess rules for devstudio.jboss.com

by Nick Boldt (JIRA)

[ https://jira.jboss.org/jira/browse/JBDS-1110?page=com.atlassian.jira.plug... ] Nick Boldt updated JBDS-1110: ----------------------------- Issue Type: Task (was: Thirdparty Change) Component/s: updatesite Fix Version/s: 3.0.1.GA Affects Version/s: 3.0.0.GA Description: Problem ----------- Currently we host update site files and some Early Access (EA) JBoss Dev Studio (JBDS) installers (.jar) on http(s)://devstudio.jboss.com. Everyone using the site shares the same access, which is somewhat painful for several reasons: a) No one can "discover" what's on the site because the root folder is restricted. b) EA users and existing registered JBDS users may not be the same folks; in fact, we may want to provide *FREE* EA access to encourage people to try-before-buy the forthcoming JBDS release, independent of possibly being an existing subscriber. c) Each annual release of JBDS gets a year of updates, but only for the product for which they subscribed; thus each year's update site should be differently restricted rather than using the shared across-the-board login. Ideally, username/password restriction would be fed by information in the CSP so that users would only need a single login, which would expire the minute their subscription expired, rather than using shared passwords via .htaccess; however, that requires significantly (?) more effort than the solution proposed below. Solution ----------- a) remove .htaccess username/password restriction for these folders: http://devstudio.jboss.com/ http://devstudio.jboss.com/updates/ http://devstudio.jboss.com/earlyaccess/ b) add .htaccess username/password restriction for these folders: http://devstudio.jboss.com/updates/2.1/ (use existing username/password) http://devstudio.jboss.com/updates/3.0/ (create new username/password) http://devstudio.jboss.com/earlyaccess/builds/ (use existing username/password + create second new username/password) I will send the current login details & proposed new ones along in an email to helpdesk@ so that they're not copied publicly here. Note that JBDS 3.0 is scheduled to be released March 10, and we need to get these changes in place before then. was: Problem ----------- Currently we host update site files and some Early Access (EA) JBoss Dev Studio (JBDS) installers (.jar) on http(s)://devstudio.jboss.com. Everyone using the site shares the same access, which is somewhat painful for two reasons: a) No one can "discover" what's on the site because the root folder is restricted. b) EA users and existing registered JBDS users may not be the same folks; in fact, we may want to provide *FREE* EA access to encourage people to try-before-buy the forthcoming JBDS release, independent of possibly being an existing subscriber. c) Each annual release of JBDS gets a year of updates, but only for the product for which they subscribed; thus each year's update site should be differently restricted rather than using the shared across-the-board login. d) Ideally, username/password restriction would be fed by information in the CSP so that users would only need a single login, which would expire the minute their subscription expired, rather than using shared passwords via .htaccess; however, that requires significantly (?) more effort than the solution proposed below. Solution ----------- a) remove .htaccess username/password restriction for these folders: http://devstudio.jboss.com/ http://devstudio.jboss.com/updates/ http://devstudio.jboss.com/earlyaccess/ b) add .htaccess username/password restriction for these folders: http://devstudio.jboss.com/updates/2.1/ (use existing username/password) http://devstudio.jboss.com/updates/3.0/ (create new username/password) http://devstudio.jboss.com/earlyaccess/builds/ (use existing username/password + create second new username/password) I will send the current login details & proposed new ones along in an email to helpdesk@ so that they're not copied publicly here. Note that JBDS 3.0 is scheduled to be released March 10, and we need to get these changes in place before then. > reconfigure .htaccess rules for devstudio.jboss.com > --------------------------------------------------- > > Key: JBDS-1110 > URL: https://jira.jboss.org/jira/browse/JBDS-1110 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: updatesite > Affects Versions: 3.0.0.GA > Reporter: Nick Boldt > Assignee: prakash aradhya > Priority: Critical > Fix For: 3.0.1.GA > > > Problem > ----------- > Currently we host update site files and some Early Access (EA) JBoss Dev Studio (JBDS) installers (.jar) on http(s)://devstudio.jboss.com. > Everyone using the site shares the same access, which is somewhat painful for several reasons: > a) No one can "discover" what's on the site because the root folder is restricted. > b) EA users and existing registered JBDS users may not be the same folks; in fact, we may want to provide *FREE* EA access to encourage people to try-before-buy the forthcoming JBDS release, independent of possibly being an existing subscriber. > c) Each annual release of JBDS gets a year of updates, but only for the product for which they subscribed; thus each year's update site should be differently restricted rather than using the shared across-the-board login. > Ideally, username/password restriction would be fed by information in the CSP so that users would only need a single login, which would expire the minute their subscription expired, rather than using shared passwords via .htaccess; however, that requires significantly (?) more effort than the solution proposed below. > Solution > ----------- > a) remove .htaccess username/password restriction for these folders: > http://devstudio.jboss.com/ > http://devstudio.jboss.com/updates/ > http://devstudio.jboss.com/earlyaccess/ > b) add .htaccess username/password restriction for these folders: > http://devstudio.jboss.com/updates/2.1/ (use existing username/password) > http://devstudio.jboss.com/updates/3.0/ (create new username/password) > http://devstudio.jboss.com/earlyaccess/builds/ (use existing username/password + create second new username/password) > I will send the current login details & proposed new ones along in an email to helpdesk@ so that they're not copied publicly here. > Note that JBDS 3.0 is scheduled to be released March 10, and we need to get these changes in place before then. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Moved: (JBDS-1110) reconfigure .htaccess rules for devstudio.jboss.com

by Nick Boldt (JIRA)

[ https://jira.jboss.org/jira/browse/JBDS-1110?page=com.atlassian.jira.plug... ] Nick Boldt moved JBQA-3123 to JBDS-1110: ---------------------------------------- Project: Developer Studio (JBoss Developer Studio) (was: JBoss QA) Key: JBDS-1110 (was: JBQA-3123) Issue Type: Thirdparty Change (was: Bug) Assignee: prakash aradhya (was: Michael Harvey) > reconfigure .htaccess rules for devstudio.jboss.com > --------------------------------------------------- > > Key: JBDS-1110 > URL: https://jira.jboss.org/jira/browse/JBDS-1110 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Thirdparty Change > Reporter: Nick Boldt > Assignee: prakash aradhya > Priority: Critical > > Problem > ----------- > Currently we host update site files and some Early Access (EA) JBoss Dev Studio (JBDS) installers (.jar) on http(s)://devstudio.jboss.com. > Everyone using the site shares the same access, which is somewhat painful for two reasons: > a) No one can "discover" what's on the site because the root folder is restricted. > b) EA users and existing registered JBDS users may not be the same folks; in fact, we may want to provide *FREE* EA access to encourage people to try-before-buy the forthcoming JBDS release, independent of possibly being an existing subscriber. > c) Each annual release of JBDS gets a year of updates, but only for the product for which they subscribed; thus each year's update site should be differently restricted rather than using the shared across-the-board login. > d) Ideally, username/password restriction would be fed by information in the CSP so that users would only need a single login, which would expire the minute their subscription expired, rather than using shared passwords via .htaccess; however, that requires significantly (?) more effort than the solution proposed below. > Solution > ----------- > a) remove .htaccess username/password restriction for these folders: > http://devstudio.jboss.com/ > http://devstudio.jboss.com/updates/ > http://devstudio.jboss.com/earlyaccess/ > b) add .htaccess username/password restriction for these folders: > http://devstudio.jboss.com/updates/2.1/ (use existing username/password) > http://devstudio.jboss.com/updates/3.0/ (create new username/password) > http://devstudio.jboss.com/earlyaccess/builds/ (use existing username/password + create second new username/password) > I will send the current login details & proposed new ones along in an email to helpdesk@ so that they're not copied publicly here. > Note that JBDS 3.0 is scheduled to be released March 10, and we need to get these changes in place before then. -- 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, 4 months

1
0
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, 4 months

2
3
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 February 2010