June 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JGRP-542) MPING: add bind_interfaces to define list of interfaces to listen for discovery requests

by Bela Ban (JIRA)

MPING: add bind_interfaces to define list of interfaces to listen for discovery requests ---------------------------------------------------------------------------------------- Key: JGRP-542 URL: http://jira.jboss.com/jira/browse/JGRP-542 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.4.1 SP4, 2.5 Same as in TP -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years

1
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-974) Unable to process control connection

by Tim Fox (JIRA)

Unable to process control connection ------------------------------------ Key: JBMESSAGING-974 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-974 Project: JBoss Messaging Issue Type: Bug Reporter: Tim Fox Assigned To: Ron Sigal Fix For: 1.3.0.GA When running messaging remote tests (ant remote-tests from tests dir). At various points, JBoss Remoting is logging the following: [junit] @control: Socket[addr=/127.0.0.1,port=2960,localport=58358] 17:09:54,929 ERROR [BisocketServerInvoker] Unable to process control connection: Socket closed [junit] java.net.SocketException: Socket closed [junit] at java.net.SocketInputStream.socketRead0(Native Method) [junit] at java.net.SocketInputStream.read(SocketInputStream.java:129) [junit] at java.net.SocketInputStream.read(SocketInputStream.java:182) [junit] at java.io.FilterInputStream.read(FilterInputStream.java:66) [junit] at org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlConnectionThread.run(BisocketServerInvoker.java:652) This doesn't seem to cause the tests to fail, and is annoying. I guess remoting is trying to clear up its state and failing (??) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years

1
2
0 / 0

[JBoss JIRA] Created: (JBRULES-951) Strange NullPointerException in rule compilation with Iterator in RHS

by Alexandre Gattiker (JIRA)

Strange NullPointerException in rule compilation with Iterator in RHS --------------------------------------------------------------------- Key: JBRULES-951 URL: http://jira.jboss.com/jira/browse/JBRULES-951 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.0.MR3 Environment: IBM RAD 7 Reporter: Alexandre Gattiker Assigned To: Mark Proctor Create a new Rules Project In Sample.drl add "import java.util.*;" at the top, and within the consequence block of one of the two rules: ArrayList list = new ArrayList(); for (Iterator iter = list.iterator(); iter.hasNext();) { } Eclipse reports a problem: Severity and Description Path Resource Location Creation Time Id Error: java.lang.NullPointerException droolstest6/src/rules Sample.drl Unknown 1182938042901 228615 When executing DroolsTest I get: java.lang.NullPointerException at org.drools.rule.builder.dialect.java.JavaConsequenceBuilder.build(JavaConsequenceBuilder.java:54) at org.drools.rule.builder.RuleBuilder.build(RuleBuilder.java:67) at org.drools.compiler.PackageBuilder.addRule(PackageBuilder.java:390) at org.drools.compiler.PackageBuilder.addPackage(PackageBuilder.java:264) at org.drools.compiler.PackageBuilder.addPackageFromDrl(PackageBuilder.java:147) at com.sample.DroolsTest.readRule(DroolsTest.java:54) at com.sample.DroolsTest.main(DroolsTest.java:21) With 4.0.0.MR2 the bug does not happen. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years

2
3
0 / 0

[JBoss JIRA] Created: (BPEL-225) API documentation for packages and core classes

by Alejandro Guizar (JIRA)

API documentation for packages and core classes ----------------------------------------------- Key: BPEL-225 URL: http://jira.jboss.com/jira/browse/BPEL-225 Project: JBoss jBPM BPEL Issue Type: Task Security Level: Public (Everyone can see) Components: Documents Reporter: Alejandro Guizar Assigned To: Alejandro Guizar Fix For: jBPM BPEL 1.1 beta 3 Altough the source code is well documented, API documentation is almost unexistent. Writing javadocs for all packages and at least the core classes is a must. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years

2
2
0 / 0

[JBoss JIRA] Created: (BPEL-228) move endpoint references to a separate package

by Alejandro Guizar (JIRA)

move endpoint references to a separate package ---------------------------------------------- Key: BPEL-228 URL: http://jira.jboss.com/jira/browse/BPEL-228 Project: JBoss jBPM BPEL Issue Type: Task Security Level: Public (Everyone can see) Components: Engine Reporter: Alejandro Guizar Assigned To: Alejandro Guizar Fix For: jBPM BPEL 1.1 beta 3 In BPEL 2, endpoint references have been turned into an extensible mechanism, just like sublanguages. Moving endpoint references to a separate package is meant as an aid for the end developer to understand the structure and the components of the mechanism. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years

2
2
0 / 0

[JBoss JIRA] Created: (BPEL-227) update user guide to match new distribution package structure

by Alejandro Guizar (JIRA)

update user guide to match new distribution package structure ------------------------------------------------------------- Key: BPEL-227 URL: http://jira.jboss.com/jira/browse/BPEL-227 Project: JBoss jBPM BPEL Issue Type: Task Security Level: Public (Everyone can see) Components: Documents Reporter: Alejandro Guizar Assigned To: Alejandro Guizar Fix For: jBPM BPEL 1.1 beta 3 The new project structure created a separation between the development and the distribution structure. The user guide must be updated to match the contents of the distribution package. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years

2
2
0 / 0

[JBoss JIRA] Created: (BPEL-226) upgrade to jBPM jPDL 3.2.Beta1

by Alejandro Guizar (JIRA)

upgrade to jBPM jPDL 3.2.Beta1 ------------------------------ Key: BPEL-226 URL: http://jira.jboss.com/jira/browse/BPEL-226 Project: JBoss jBPM BPEL Issue Type: Task Security Level: Public (Everyone can see) Components: Engine Reporter: Alejandro Guizar Assigned To: Alejandro Guizar Fix For: jBPM BPEL 1.1 beta 3 Upgrade the jBPM jPDL dependency and make sure unit tests and examples do not break. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years

2
2
0 / 0

[JBoss JIRA] Created: (BPEL-222) soap message creation fails under jbossws 1.0.3 and above

by Alejandro Guizar (JIRA)

soap message creation fails under jbossws 1.0.3 and above --------------------------------------------------------- Key: BPEL-222 URL: http://jira.jboss.com/jira/browse/BPEL-222 Project: JBoss jBPM BPEL Issue Type: Task Security Level: Public (Everyone can see) Reporter: Alejandro Guizar Assigned To: Alejandro Guizar Because of a change in the saaj implementation first introduced in jbossws 1.0.3, jbpm bpel can no longer use the same code to create a fault message under both the old and the new services stack. The proposed solution is to introduce a class hierarchy for creating fault messages modeled after the Strategy pattern. This hierarchy encapsulates the different ways a fault message is created. Two strategies exist at this time: a) The default strategy adds a soap:fault element of type SOAPFault. This is what a developer normally would do. This should work on most stacks, including jbossws. It does *not* work under the old Axis-based stack used JBoss AS 4.0.3 and earlier. b) The backwards compatibility strategy adds a soap:fault element of type SOAPElement. Altough jboss ws4ee allows to add a SOAPFault, the marshaling code is broken and no detail entry gets written. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years

2
4
0 / 0

[JBoss JIRA] Created: (BPEL-220) Introduce distribution module

by Alejandro Guizar (JIRA)

Introduce distribution module ----------------------------- Key: BPEL-220 URL: http://jira.jboss.com/jira/browse/BPEL-220 Project: JBoss jBPM BPEL Issue Type: Task Security Level: Public (Everyone can see) Components: Engine Reporter: Alejandro Guizar Assigned To: Alejandro Guizar Fix For: jBPM BPEL 1.1 The introduction of an external repository in jBPM 3.2 brought changes in the way the distribution is built. We need to introduce a BPEL distribution module, similar to the jPDL distribution module located in jpdl/dist. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years

2
4
0 / 0

[JBoss JIRA] Created: (BPEL-219) explanation of bpel-application.xml missing in atm chapter

by Alejandro Guizar (JIRA)

explanation of bpel-application.xml missing in atm chapter ---------------------------------------------------------- Key: BPEL-219 URL: http://jira.jboss.com/jira/browse/BPEL-219 Project: JBoss jBPM BPEL Issue Type: Bug Security Level: Public (Everyone can see) Components: Documents Affects Versions: jBPM BPEL 1.1 beta 2 Reporter: Alejandro Guizar Assigned To: Alejandro Guizar Fix For: jBPM BPEL 1.1 When updating the user guide for version 1.1.Beta2, the explanation of the bpel-application.xml descriptor was left out. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years

2
5
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2007