February 2011 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-7799) Could not parse process L/ddd/src/main/rules/ruleflow.rf

by Libor Zoubek (JIRA)

Could not parse process L/ddd/src/main/rules/ruleflow.rf -------------------------------------------------------- Key: JBIDE-7799 URL: https://jira.jboss.org/browse/JBIDE-7799 Project: Tools (JBoss Tools) Issue Type: Bug Components: drools Affects Versions: 3.2.0.Beta2 Environment: soa-p 4.3 Reporter: Libor Zoubek Assignee: Kris Verlaenen -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

5
21
0 / 0

[JBoss JIRA] Created: (JBIDE-8482) Hook up the Forge tools into the main JBT build.

by Koen Aers (JIRA)

Hook up the Forge tools into the main JBT build. ------------------------------------------------ Key: JBIDE-8482 URL: https://issues.jboss.org/browse/JBIDE-8482 Project: Tools (JBoss Tools) Issue Type: Task Components: Build/Releng Reporter: Koen Aers Assignee: Nick Boldt I have created pom.xml files as I thought it was appropriate. I'll leave the rest in the hands of buildmaster extraordinaire. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-8128) [JBossTools Runtimes] Allow user to select what runtime types to be added

by Libor Zoubek (JIRA)

[JBossTools Runtimes] Allow user to select what runtime types to be added -------------------------------------------------------------------------- Key: JBIDE-8128 URL: https://issues.jboss.org/browse/JBIDE-8128 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS, integration Affects Versions: 3.2.0.CR1 Reporter: Libor Zoubek Assignee: Rob Stryker If user searches for a runtime(s) he adds folder wich contains typically EAP or SOA. But EAP or SOA contains several runtimes, which are added if user decides to add the runtime as whole. Runtimes that will be added are printed in description section. User shlould have the right to decide what runtimes will be added. I suggest to display found runtime as tree with checkboxes. For example SOA runtime should look like: - /opt/soa-5.0 |- Server runtime 5.0 |- Drools 5.1 |- Seam 2.2 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
9
0 / 0

[JBoss JIRA] Created: (JBIDE-4082) Can't change starting state node from graphical editor

by Hedley Proctor (JIRA)

Can't change starting state node from graphical editor ------------------------------------------------------ Key: JBIDE-4082 URL: https://jira.jboss.org/jira/browse/JBIDE-4082 Project: Tools (JBoss Tools) Issue Type: Bug Components: jbpm Affects Versions: 3.1.0 Environment: Windows xp Eclipse 3.3.2, build M20080221-1800 JBoss jBPM Eclipse plugin v3.1.3 SP2 Reporter: Hedley Proctor Fix For: 3.1.0 It doesn't seem possible to change the a starting state node to a normal state node, or vice versa. e.g. if you have a starting state with transitions to a number of states, but you want to insert a new starting state before it and convert the present node to a normal "State" node, it looks like you have to - delete your current starting state node - create a new state node with the same name, transitions, actions etc - add your new starting state node Since state and starting states are very similar, perhaps we could have an option to convert a starting state node to a normal state? e.g. in the properties tab at the bottom perhaps? Then you could just click this button or change the option to convert the node type, without any deleting and recreating. -- 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

14 years, 10 months

5
7
0 / 0

[JBoss JIRA] Created: (JBDS-1571) NPE and empty installer page on Mac OS X 1.5 when java 1.6 used during installation

by Jiri Peterka (JIRA)

NPE and empty installer page on Mac OS X 1.5 when java 1.6 used during installation ----------------------------------------------------------------------------------- Key: JBDS-1571 URL: https://issues.jboss.org/browse/JBDS-1571 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: installer Environment: JBDS 4.0.0.GA H180 MacOSX1.5 cocoa x64, Reporter: Jiri Peterka Simple clicking installatino works fine, there are just 2 scenarios for this error: Scenario1: Open shell and use <path-to-1.6>/bin/java -jar jbdevstudio-product-eap-macosx-cocoa-x86_64-4.0.0.v201102161941R-H180-GA.ja Try to install Scenario2: Open shell and use default (1.5) java and in installer change specific java to 1.6 You should see (and last-1 page in installer is empty): main: [echo] Run p2 metadata generator [echo] jpeterka [p2] Generating metadata for /home/brq/jpeterka/ide/jbds-4.0.0.ga-h180/studio. [p2] Generation completed with success [0 seconds]. [delete] Deleting: /var/folders/zz/zzzivhrRnAmviuee+++sVE++C6I/-Tmp-/artifacts.jar [delete] Deleting: /var/folders/zz/zzzivhrRnAmviuee+++sVE++C6I/-Tmp-/content.jar java.lang.NullPointerException at java.io.FileInputStream.<init>(FileInputStream.java:103) at com.jboss.jbds.installer.CreateLinkPanel.addJREPath(CreateLinkPanel.java:176) at com.jboss.jbds.installer.CreateLinkPanel.panelActivate(CreateLinkPanel.java:62) at com.izforge.izpack.installer.InstallerFrame.switchPanel(Unknown Source) at com.izforge.izpack.installer.InstallerFrame.navigateNext(Unknown Source) at com.izforge.izpack.installer.InstallerFrame.navigateNext(Unknown Source) at com.izforge.izpack.installer.InstallerFrame$NavigationHandler.actionPerformed(Unknown Source) at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:2028) at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2351) at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387) at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242) at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:236) at java.awt.Component.processMouseEvent(Component.java:6348) at javax.swing.JComponent.processMouseEvent(JComponent.java:3267) at java.awt.Component.processEvent(Component.java:6113) at java.awt.Container.processEvent(Container.java:2085) at java.awt.Component.dispatchEventImpl(Component.java:4714) at java.awt.Container.dispatchEventImpl(Container.java:2143) at java.awt.Component.dispatchEvent(Component.java:4544) at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4618) at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4282) at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4212) at java.awt.Container.dispatchEventImpl(Container.java:2129) at java.awt.Window.dispatchEventImpl(Window.java:2475) at java.awt.Component.dispatchEvent(Component.java:4544) at java.awt.EventQueue.dispatchEvent(EventQueue.java:635) at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:296) at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:211) at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:201) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:196) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:188) at java.awt.EventDispatchThread.run(EventDispatchThread.java:122) calltarget: -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
5
0 / 0

[JBoss JIRA] Created: (JBDS-1522) Add title captions to right-corner icon pages

by Libor Zoubek (JIRA)

Add title captions to right-corner icon pages --------------------------------------------- Key: JBDS-1522 URL: https://issues.jboss.org/browse/JBDS-1522 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: ui/branding Affects Versions: 4.0.0.CR1 Reporter: Libor Zoubek Priority: Minor Originally suggested by mmalina: Once you click on Getting started or any other of the items from the welcome screen, on the next page there are buttons in the top-right corner. These buttons don't have any text caption, so you have to guess what these buttons do. It would be nice to have a title="" for each of them if that's possible. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

4
8
0 / 0

[JBoss JIRA] Created: (JBIDE-8374) First expansion of Hibernate CC node is often unsuccessful

by Jiri Peterka (JIRA)

First expansion of Hibernate CC node is often unsuccessful ---------------------------------------------------------- Key: JBIDE-8374 URL: https://issues.jboss.org/browse/JBIDE-8374 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.2.0.CR2 (tentative) Environment: JBDS 4.0.0.CR3 H162, Linux 64 Reporter: Jiri Peterka It's quite often experience that first expansion of Hibernate CC tree is often unsuccessful (nothing is expanded or empty tree) Steps to replicate this can be various and it's not 100% reproducible because it happens only from time to tome. For me it's often happenings with new workspace and first hibernate console and with newly started JBT/JBDS. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-8275) Composite components should be recognized in jar-files inside META-INF/resources/

by Viacheslav Kabanovich (JIRA)

Composite components should be recognized in jar-files inside META-INF/resources/ --------------------------------------------------------------------------------- Key: JBIDE-8275 URL: https://issues.jboss.org/browse/JBIDE-8275 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JSF Affects Versions: 3.2.0.CR1 Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 3.3.0.M1 Within project, composite components are located in folder %Web-root%/resources. - That is supported by JBoss Tools. But besides, composite components may be located in used by the project external jars in folder META-INF/resources. - That should be implemented. See http://community.jboss.org/message/583919#583919 JavaServerTM Faces Specification 2.6.1.2 Packaging Resources into the Classpath For the default implementation, resources packaged in the classpath must reside under the JAR entry name: META-INF/resources/<resourceIdentifier> -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

4
15
0 / 0

[JBoss JIRA] Created: (JBIDE-8399) Improve US States SOAP Service Project Example

by Snjezana Peco (JIRA)

Improve US States SOAP Service Project Example ---------------------------------------------- Key: JBIDE-8399 URL: https://issues.jboss.org/browse/JBIDE-8399 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: project-examples, teiid Affects Versions: 3.2.0.CR1 Reporter: Snjezana Peco Assignee: Snjezana Peco I propose adding the "wtpruntime" fix/requirement for SOA-P. Since JBoss Tools has the same runtime type for EAP, SOA-P, EPP, we would probably need to add a separate property for Teiid examples (suppose they require a Teiid runtime). We already have a similar property for esb, portlet ... (see http://download.jboss.org/jbosstools/examples/project-examples-jbds30.xml). It would also be possible to add a cheatsheet that would describe and run the actions described in US_States/readme.txt. BTW The StateService project should use Java Execution environment instead of a specific version of JRE (1.6.0_14). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

6
23
0 / 0

[JBoss JIRA] Created: (JBDS-1573) Deploying a BPEL project to a SOA-P 5.1 server in JBDS 4.0 appears succesful - but the service is actually not deployed

by Len DiMaggio (JIRA)

Deploying a BPEL project to a SOA-P 5.1 server in JBDS 4.0 appears succesful - but the service is actually not deployed ----------------------------------------------------------------------------------------------------------------------- Key: JBDS-1573 URL: https://issues.jboss.org/browse/JBDS-1573 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: Error Reporting, integration Environment: JBDS 4.0 CR4 SOA-P 5.1 CR1 Reporter: Len DiMaggio Priority: Critical To recreate the problem: 1) Install this into JBDS 4.0 JBoss BPEL Editor, 1.0.0.v20110204-2131-H55-Alpha1 org.jboss.tools.bpel.feature.feature.group 2) Import the BPEL project from the attached .zip file (a copy of the SOA-P 5.1 'bpel_helloworld' quickstart 3) Create a new SOA-P 5.1 server in JBDS - using SOA-P 5.1 CR1 - and start it 4) Add the BPEL project to the server 5) See screenshot 1 - the BPEL project's jar appears to be there 6) Attemmpt to access the project - at this URL: http://localhost:8080/Quickstart_bpel_hello_worldWS?wsdl 7) And a 404 - not found error is returned Note that nothing is written to the workspace .log file or the server.log file -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

5
17
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 2011