July 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-1898) Depending on keystroke sequence - it is possible to corrupt SOA-P server's Drools runtime from "Create new Drools Runtime" dialog

by Len DiMaggio (Created) (JIRA)

Depending on keystroke sequence - it is possible to corrupt SOA-P server's Drools runtime from "Create new Drools Runtime" dialog --------------------------------------------------------------------------------------------------------------------------------- Key: JBDS-1898 URL: https://issues.jboss.org/browse/JBDS-1898 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: SOA Platform Affects Versions: 4.1.1.Final Reporter: Len DiMaggio Assignee: Brian Fitzpatrick Fix For: 4.1.1.Final The exact set of key strokes is: 1. Navigate to installed drools runtime page 2. Click "Add" 3. Click "Create new Drools 5 Runtime" 4. Navigate to server's jbrules.esb (jboss-soa-p-5/jboss-as/server/<profile>)/deploy/jbrules.esb) 5. Click "Open" The SOA-P jbrules.esb dir will have community jars (these are the files without version numbers embedded in their names) written to it. See below: ================= pwd /opt/local/52_ER5/jboss-soa-p-5/jboss-as/server/production/deploy/jbrules.esb BEFORE [ldimaggi@ldimaggi jbrules.esb]$ ll total 9304 -rw-r--r--. 1 ldimaggi ldimaggi 465235 Oct 12 06:58 antlr-2.7.7.jar -rw-r--r--. 1 ldimaggi ldimaggi 923617 Oct 12 06:58 antlr-3.3.jar -rw-r--r--. 1 ldimaggi ldimaggi 175591 Oct 12 06:58 antlr-runtime-3.3.jar -rw-r--r--. 1 ldimaggi ldimaggi 1045247 Oct 12 06:45 drools-compiler-5.2.0.BRMS.jar -rw-r--r--. 1 ldimaggi ldimaggi 2115192 Oct 12 06:45 drools-core-5.2.0.BRMS.jar -rw-r--r--. 1 ldimaggi ldimaggi 62487 Oct 12 06:45 drools-decisiontables-5.2.0.BRMS.jar -rw-r--r--. 1 ldimaggi ldimaggi 34820 Oct 12 06:45 drools-jsr94-5.2.0.BRMS.jar -rw-r--r--. 1 ldimaggi ldimaggi 60441 Oct 12 06:45 drools-templates-5.2.0.BRMS.jar -rw-r--r--. 1 ldimaggi ldimaggi 1717966 Oct 12 06:58 ecj-3.5.1.jar -rw-r--r--. 1 ldimaggi ldimaggi 90563 Oct 11 10:36 jbossesb-jbrules.jar -rw-r--r--. 1 ldimaggi ldimaggi 341509 Oct 12 06:45 jbpm-flow-5.2.0.BRMS.jar -rw-r--r--. 1 ldimaggi ldimaggi 145022 Oct 12 06:45 jbpm-flow-builder-5.2.0.BRMS.jar -rw-r--r--. 1 ldimaggi ldimaggi 207 Oct 11 10:28 jbrules-service.xml -rw-r--r--. 1 ldimaggi ldimaggi 18263 Oct 12 06:58 jsr94-1.1.jar -rw-r--r--. 1 ldimaggi ldimaggi 787567 Oct 12 06:58 jxl-2.6.10.jar -rw-r--r--. 1 ldimaggi ldimaggi 185855 Oct 12 06:45 knowledge-api-5.2.0.BRMS.jar -rw-r--r--. 1 ldimaggi ldimaggi 391369 Oct 12 06:58 log4j-1.2.14.jar drwxr-xr-x. 2 ldimaggi ldimaggi 4096 Oct 11 10:28 META-INF -rw-r--r--. 1 ldimaggi ldimaggi 757233 Oct 12 06:45 mvel2-2.1.Beta6.jar -rw-r--r--. 1 ldimaggi ldimaggi 156620 Oct 12 06:58 stringtemplate-3.2.1.jar -rw-r--r--. 1 ldimaggi ldimaggi 2755 Oct 11 10:28 XPathLanguage.dsl AFTER [ldimaggi@ldimaggi jbrules.esb]$ ll total 20108 -rw-r--r--. 1 ldimaggi ldimaggi 465235 Oct 12 06:58 antlr-2.7.7.jar -rw-r--r--. 1 ldimaggi ldimaggi 923617 Oct 12 06:58 antlr-3.3.jar -rw-r--r--. 1 ldimaggi ldimaggi 175591 Oct 12 06:58 antlr-runtime-3.3.jar -rw-rw-r--. 1 ldimaggi ldimaggi 163650 Oct 21 16:02 antlr-runtime.jar -rw-r--r--. 1 ldimaggi ldimaggi 1045247 Oct 12 06:45 drools-compiler-5.2.0.BRMS.jar -rw-rw-r--. 1 ldimaggi ldimaggi 996982 Oct 21 16:02 drools-compiler.jar -rw-r--r--. 1 ldimaggi ldimaggi 2115192 Oct 12 06:45 drools-core-5.2.0.BRMS.jar -rw-rw-r--. 1 ldimaggi ldimaggi 1990689 Oct 21 16:02 drools-core.jar -rw-r--r--. 1 ldimaggi ldimaggi 62487 Oct 12 06:45 drools-decisiontables-5.2.0.BRMS.jar -rw-rw-r--. 1 ldimaggi ldimaggi 56955 Oct 21 16:02 drools-decisiontables.jar -rw-rw-r--. 1 ldimaggi ldimaggi 269216 Oct 21 16:02 droolsjbpm-ide-common.jar -rw-r--r--. 1 ldimaggi ldimaggi 34820 Oct 12 06:45 drools-jsr94-5.2.0.BRMS.jar -rw-rw-r--. 1 ldimaggi ldimaggi 30196 Oct 21 16:02 drools-jsr94.jar -rw-r--r--. 1 ldimaggi ldimaggi 60441 Oct 12 06:45 drools-templates-5.2.0.BRMS.jar -rw-rw-r--. 1 ldimaggi ldimaggi 54101 Oct 21 16:02 drools-templates.jar -rw-r--r--. 1 ldimaggi ldimaggi 1717966 Oct 12 06:58 ecj-3.5.1.jar -rw-r--r--. 1 ldimaggi ldimaggi 90563 Oct 11 10:36 jbossesb-jbrules.jar -rw-rw-r--. 1 ldimaggi ldimaggi 169449 Oct 21 16:02 jbpm-bpmn2.jar -rw-r--r--. 1 ldimaggi ldimaggi 341509 Oct 12 06:45 jbpm-flow-5.2.0.BRMS.jar -rw-r--r--. 1 ldimaggi ldimaggi 145022 Oct 12 06:45 jbpm-flow-builder-5.2.0.BRMS.jar -rw-rw-r--. 1 ldimaggi ldimaggi 135300 Oct 21 16:02 jbpm-flow-builder.jar -rw-rw-r--. 1 ldimaggi ldimaggi 319258 Oct 21 16:02 jbpm-flow.jar -rw-r--r--. 1 ldimaggi ldimaggi 207 Oct 11 10:28 jbrules-service.xml -rw-r--r--. 1 ldimaggi ldimaggi 18263 Oct 12 06:58 jsr94-1.1.jar -rw-rw-r--. 1 ldimaggi ldimaggi 13749 Oct 21 16:02 jsr94.jar -rw-rw-r--. 1 ldimaggi ldimaggi 237047 Oct 21 16:02 junit.jar -rw-r--r--. 1 ldimaggi ldimaggi 787567 Oct 12 06:58 jxl-2.6.10.jar -rw-rw-r--. 1 ldimaggi ldimaggi 743361 Oct 21 16:02 jxl.jar -rw-r--r--. 1 ldimaggi ldimaggi 185855 Oct 12 06:45 knowledge-api-5.2.0.BRMS.jar -rw-rw-r--. 1 ldimaggi ldimaggi 161470 Oct 21 16:02 knowledge-api.jar -rw-r--r--. 1 ldimaggi ldimaggi 391369 Oct 12 06:58 log4j-1.2.14.jar drwxr-xr-x. 2 ldimaggi ldimaggi 4096 Oct 11 10:28 META-INF -rw-r--r--. 1 ldimaggi ldimaggi 757233 Oct 12 06:45 mvel2-2.1.Beta6.jar -rw-rw-r--. 1 ldimaggi ldimaggi 716133 Oct 21 16:02 mvel2.jar -rw-rw-r--. 1 ldimaggi ldimaggi 4513443 Oct 21 16:02 org.eclipse.jdt.core_3.6.2.v_A76_R36x.jar -rw-r--r--. 1 ldimaggi ldimaggi 156620 Oct 12 06:58 stringtemplate-3.2.1.jar -rw-r--r--. 1 ldimaggi ldimaggi 2755 Oct 11 10:28 XPathLanguage.dsl -rw-rw-r--. 1 ldimaggi ldimaggi 24956 Oct 21 16:02 xpp3_min.jar -rw-rw-r--. 1 ldimaggi ldimaggi 431406 Oct 21 16:02 xstream.jar -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

15
28
0 / 0

[JBoss JIRA] (JBDS-1880) webservice_producer_client ESB example readme file should reference client app parameters

by Len DiMaggio (Created) (JIRA)

webservice_producer_client ESB example readme file should reference client app parameters ----------------------------------------------------------------------------------------- Key: JBDS-1880 URL: https://issues.jboss.org/browse/JBDS-1880 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: SOA Platform Affects Versions: 4.1.1.M2 Reporter: Len DiMaggio Priority: Minor Fix For: 4.1.1.Final The readme file for the webservice_producer_client ESB 5.0 example should have this text added to it: There are three options for arguments for the Java Application run configuration "jms" - Invokes a JBossWS Endpoint over JMS (via JBoss ESB). "http 8765" - Invokes a JBossWS Endpoint over HTTP (via JBoss ESB). "socket 8888" - Invokes a JBossWS Endpoint over a raw socket connection (via JBoss ESB). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

7
7
0 / 0

[JBoss JIRA] (JBDS-2151) Inconsistent names for referenced JBDS views

by Len DiMaggio (JIRA)

Len DiMaggio created JBDS-2151: ---------------------------------- Summary: Inconsistent names for referenced JBDS views Key: JBDS-2151 URL: https://issues.jboss.org/browse/JBDS-2151 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: SOA Tooling / Platform Affects Versions: 5.0.0.Beta1-SOA Environment: Version: 5.0.0.Beta3 Build id: v20120514-2058-H159-Beta3 Build date: 20120514-2058 Reporter: Len DiMaggio Assignee: Brian Fitzpatrick Priority: Minor Fix For: 5.0.0.Beta3-SOA The "JBoss ESB Configuration Visualizer" displays a message instructing the user to: Select an ESB Configuration file in the navigator or use the 'Open JBoss ESB Configuration' view menu to show a configuration graphically. ------------------- The view name as shown in Window->Show View is: "JBoss ESB Configuration Visualizer" and not "Open JBoss ESB Configuration" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

2
2
0 / 0

[JBoss JIRA] (JBDS-2047) gpd.xml is written in platform encoding

by Toshiya Kobayashi (JIRA)

Toshiya Kobayashi created JBDS-2047: --------------------------------------- Summary: gpd.xml is written in platform encoding Key: JBDS-2047 URL: https://issues.jboss.org/browse/JBDS-2047 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: jBPM Affects Versions: 4.1.1.GA Reporter: Toshiya Kobayashi Platform JIRA for GPD-184 and GPD-98 Here are the reproduce steps but basically the same as those GPD Jiras. 1. Window->Preference, General->Workspace, change the 'Text file encoding' to "Other: UTF-8". (Default is MS932 in Japanese Windows) 2. Create a jBPM3 project. (with a sample process) 3. Set 'スタート' the name of a start-state with GPD editor. 4. Look at .simple.gpd.xml (you may need to edit Package Explorer Filter for .* resources to find the file in JBDS) The file is written in Shift_JIS(MS932) even though it declares encoding="UTF-8". It will cause a problem when you use jbpm-console to see the process image. - In jbpm-console : An exception of type "org.jbpm.util.XmlException" was thrown. The message is: failed to parse xml - In server.log : [Fatal Error] :4:15: Invalid byte 1 of 1-byte UTF-8 sequence. GPD editor doesn't lookup the workspace settings when it generates gpd.xml. Hard-coded "UTF-8" may be fine (the proposed patch in GPD-184) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

3
5
0 / 0

[JBoss JIRA] (JBIDE-12264) JBoss SOA Tools REQUIRES but does not INCLUDE BPEL features

by Nick Boldt (JIRA)

12 years

4
11
0 / 0

[JBoss JIRA] (JBDS-1922) JBoss BPEL Editor showing error message for valid Assign activity

by Michael Pellegrini (Created) (JIRA)

JBoss BPEL Editor showing error message for valid Assign activity ----------------------------------------------------------------- Key: JBDS-1922 URL: https://issues.jboss.org/browse/JBDS-1922 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: visualeditor Affects Versions: 1.1.0.GA Reporter: Michael Pellegrini The assign activity is reporting an error, which only shows up in the Project Explorer view (not in the actual editor). The assign is a sample assign between two variables. The error is: The XPath segment "child::app:Application" cannot be resolved. Test.bpel /Test/bpelContent line 45 BPEL Validation Marker Although it shows as an error, it actually deploys and runs fine. Have a sample project, but not sure how to attach to this jira. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

10
13
0 / 0

[JBoss JIRA] (JBIDE-10174) SOA: Extend JBoss Perspective

by Alexey Kazakov (Created) (JIRA)

SOA: Extend JBoss Perspective ----------------------------- Key: JBIDE-10174 URL: https://issues.jboss.org/browse/JBIDE-10174 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: esb, Webservices Reporter: Alexey Kazakov Assignee: Brian Fitzpatrick Fix For: 3.3.0.Beta1 Brian, I'm crating this sub-task to include SAO stuff to JBoss Perspecitve if any. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

6
9
0 / 0

[JBoss JIRA] Created: (JBIDE-8871) SA00086 check not implemented in BPEL validator

by Robert (Bob) Brodt (JIRA)

SA00086 check not implemented in BPEL validator ----------------------------------------------- Key: JBIDE-8871 URL: https://issues.jboss.org/browse/JBIDE-8871 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.2.0.Final Reporter: Robert (Bob) Brodt Assignee: Robert (Bob) Brodt Priority: Minor Fix For: 3.3.0.Final The FromPartValidator has a method named rule_ImplicitOnEventVariable_10 but this doesn't appear to do anything and it is the only rule that references SA00086. Look into this. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

3
4
0 / 0

[JBoss JIRA] (JBIDE-11608) Deploying BPEL project to a server is not working

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBIDE-11608: ----------------------------------------- Summary: Deploying BPEL project to a server is not working Key: JBIDE-11608 URL: https://issues.jboss.org/browse/JBIDE-11608 Project: Tools (JBoss Tools) Issue Type: Bug Components: BPEL Affects Versions: 3.3.0.Beta3-SOA Environment: Eclipse 3.7.2 + JBoss AS 5.1.0 + RiftSaw 2.3.0 Reporter: Andrej Podhradsky Assignee: Robert (Bob) Brodt Deploying BPEL project to a server, which is created using JBoss AS 5.1 adapter, is not working - it seems that nothing happens. But if I try to deploy the same project to a server created using JBoss Application Platform 5.x, it works fine. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

4
8
0 / 0

[JBoss JIRA] (JBIDE-10761) jboss bot tests job fails after switching to Drools 5.3.1

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-10761: ---------------------------------- Summary: jboss bot tests job fails after switching to Drools 5.3.1 Key: JBIDE-10761 URL: https://issues.jboss.org/browse/JBIDE-10761 Project: Tools (JBoss Tools) Issue Type: Bug Components: drools, SOA Tooling, testing Affects Versions: 3.3.0.Beta1 Reporter: Nick Boldt Assignee: Kris Verlaenen Fix For: 3.3.0.Beta1 >From https://hudson.qa.jboss.com/hudson/view/DevStudio_Trunk/job/jbosstools-3.... {code} !SESSION 2012-01-31 09:21:39.379 ----------------------------------------------- eclipse.buildId=unknown java.version=1.6.0_30 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US Framework arguments: -application org.eclipse.tycho.surefire.osgibooter.uitest -testproperties /mnt/hudson_workspace/workspace/jbosstools-3.3_trunk.bottests.aggregate/sources/aggregate/bottests-site/tests/org.jboss.tools.drools.ui.bot.test/target/surefire.properties -testApplication org.eclipse.ui.ide.workbench -product org.eclipse.platform.ide -nouithread Command-line arguments: -data /mnt/hudson_workspace/workspace/jbosstools-3.3_trunk.bottests.aggregate/sources/aggregate/bottests-site/tests/org.jboss.tools.drools.ui.bot.test/target/work/data -dev file:/mnt/hudson_workspace/workspace/jbosstools-3.3_trunk.bottests.aggregate/sources/aggregate/bottests-site/tests/org.jboss.tools.drools.ui.bot.test/target/dev.properties -application org.eclipse.tycho.surefire.osgibooter.uitest -testproperties /mnt/hudson_workspace/workspace/jbosstools-3.3_trunk.bottests.aggregate/sources/aggregate/bottests-site/tests/org.jboss.tools.drools.ui.bot.test/target/surefire.properties -testApplication org.eclipse.ui.ide.workbench -product org.eclipse.platform.ide -nouithread ... !ENTRY org.eclipse.osgi 4 0 2012-01-31 09:21:44.984 !MESSAGE Application error !STACK 1 org.eclipse.swt.SWTError: No more handles [gtk_init_check() failed] at org.eclipse.swt.SWT.error(SWT.java:4308) {code} which results in: {code} [INFO] Reactor Summary: [INFO] [INFO] org.jboss.tools.site.bottests.root ................ SUCCESS [0.888s] [INFO] org.jboss.tools.bot.tests.plugins ................. SUCCESS [0.030s] [INFO] org.jboss.tools.bot.tests.tests ................... SUCCESS [0.044s] [INFO] org.jboss.tools.drools.ui.bot.test ................ FAILURE [1:34.367s] [INFO] org.jboss.tools.bot.tests.features ................ SUCCESS [0.012s] [INFO] org.jboss.tools.bot.test.feature .................. SKIPPED [INFO] JBoss Tools - Bot Tests Site ...................... SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE {code} Not sure to whom to assign this - who owns the org.jboss.tools.drools.ui.bot.test code? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

5
13
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2012