September 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-475) Error in documentation concerning the joining of constarints

by Matias Zaya Mendez (JIRA)

Error in documentation concerning the joining of constarints ------------------------------------------------------------ Key: JBRULES-475 URL: http://jira.jboss.com/jira/browse/JBRULES-475 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 3.0.4 Reporter: Matias Zaya Mendez Assigned To: Mark Proctor Priority: Trivial In the documentation it is specified that in the DSL in order to create join constraints you define them as such: (URL:http://labs.jboss.com/file-access/default/members/jbossrules/freezone...) [when]There is a Cheese with=Cheese() [when]-age is less than {age}=age<{age} [when]-type is '{type}'=type=='{type}' [when]-country equal to '{country}'=country=='{country}' Actually, there must be a space between the "dash" and the constraint, such as: [when]There is a Cheese with=Cheese() [when]- age is less than {age}=age<{age} [when]- type is '{type}'=type=='{type}' [when]- country equal to '{country}'=country=='{country}' -- 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, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1032) Document NavigationPortlet new features

by Roy Russo (JIRA)

Document NavigationPortlet new features --------------------------------------- Key: JBPORTAL-1032 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1032 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal Documentation Affects Versions: 2.6.Alpha1 Reporter: Roy Russo Assigned To: Roy Russo Fix For: 2.6.Alpha1 1. excplitict tab ordering 2. localization support -- 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, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-299) NotificationBusDemo problem with 2.4CR2

by Christian Pekeler (JIRA)

NotificationBusDemo problem with 2.4CR2 --------------------------------------- Key: JGRP-299 URL: http://jira.jboss.com/jira/browse/JGRP-299 Project: JGroups Issue Type: Bug Affects Versions: 2.4 Environment: MacOSX, Java 1.5 Reporter: Christian Pekeler Assigned To: Bela Ban [/Users/christian/Projects/JGroups-2.4CR2.src]> java -cp dist/jgroups-all.jar:lib/commons-logging.jar:lib/concurrent.jar:lib/xalan.jar org.jgroups.demos.NotificationBusDemo Starting NotificationBus with name BusDemo Sep 5, 2006 4:56:53 PM org.jgroups.JChannel init INFO: JGroups version: 2.4CR2 Sep 5, 2006 4:56:53 PM org.jgroups.protocols.UDP createSockets INFO: sockets will use interface 192.168.5.142 Sep 5, 2006 4:56:53 PM org.jgroups.protocols.UDP createSockets WARNING: traffic class of 8 could not be set, will be ignored java.net.SocketException: Invalid argument at java.net.PlainDatagramSocketImpl.socketSetOption(Native Method) at java.net.PlainDatagramSocketImpl.setOption(PlainDatagramSocketImpl.java:299) at java.net.DatagramSocket.setTrafficClass(DatagramSocket.java:1052) at org.jgroups.protocols.UDP.createSockets(UDP.java:456) at org.jgroups.protocols.UDP.start(UDP.java:383) at org.jgroups.stack.Protocol.handleSpecialDownEvent(Protocol.java:589) at org.jgroups.stack.DownHandler.run(Protocol.java:118) Sep 5, 2006 4:56:53 PM org.jgroups.protocols.UDP createSockets WARNING: traffic class of 8 could not be set, will be ignored java.net.SocketException: Invalid argument at java.net.PlainDatagramSocketImpl.socketSetOption(Native Method) at java.net.PlainDatagramSocketImpl.setOption(PlainDatagramSocketImpl.java:299) at java.net.DatagramSocket.setTrafficClass(DatagramSocket.java:1052) at org.jgroups.protocols.UDP.createSockets(UDP.java:527) at org.jgroups.protocols.UDP.start(UDP.java:383) at org.jgroups.stack.Protocol.handleSpecialDownEvent(Protocol.java:589) at org.jgroups.stack.DownHandler.run(Protocol.java:118) Sep 5, 2006 4:56:53 PM org.jgroups.protocols.UDP createSockets -- 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, 6 months

2
8
0 / 0

[JBoss JIRA] Created: (JBRULES-481) LeftInputAdater.updateNewNode does incorrect propagation

by Mark Proctor (JIRA)

LeftInputAdater.updateNewNode does incorrect propagation -------------------------------------------------------- Key: JBRULES-481 URL: http://jira.jboss.com/jira/browse/JBRULES-481 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Reteoo Affects Versions: 3.0.4 Reporter: Mark Proctor Assigned To: Edson Tirelli Fix For: 3.0.5, 3.1-m1 // Get the newly attached TupleSink final TupleSink sink = (TupleSink) getTupleSinks().get( getTupleSinks().size() - 1 ); // Iterate the memory and assert all tuples into the newly attached TupleSink final Map memory = (Map) workingMemory.getNodeMemory( this ); for ( final Iterator it = memory.values().iterator(); it.hasNext(); ) { final LinkedList list = (LinkedList) it.next(); for ( LinkedListNode node = list.getFirst(); node != null; node = node.getNext() ) { sink.assertTuple( (ReteTuple) ((LinkedListObjectWrapper) node).getObject(), context, workingMemory ); } } We get the last Sink but then we send through ALL tuples in the list to that single sink. yet we know that each tuple is for a specific sink. we instead should grab the handle and create a new tuple which we add to the list. -- 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, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-708) Bundled jboss-ejb3-all.jar is invalid in embeddable container

by Adrian Pillinger (JIRA)

Bundled jboss-ejb3-all.jar is invalid in embeddable container ------------------------------------------------------------- Key: EJBTHREE-708 URL: http://jira.jboss.com/jira/browse/EJBTHREE-708 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - FD Environment: Linux, Maven, Java 5. Reporter: Adrian Pillinger Priority: Blocker The classes that were bundled together to form the jboss-ejb3-all.jar of the embeddable container are not compatible. I am calling the following code... {code} EJB3StandaloneBootstrap.boot(null); Collection<URL> deployDirs = getDeployDirURLs(); Collection<URL> persistenceArchives = getPersistenceArchiveURLs(); deployer = EJB3StandaloneBootstrap.createDeployer(); .... get deploy dirs .. deployer.getDeployDirs().addAll(deployDirs); deployer.create(); deployer.start(); {code} When the code gets to deployer.create(); it fails with the following stack trace {noformat} java.lang.NoSuchMethodError: org/jboss/ejb3/Ejb3Deployment.<init>(Lorg/jboss/ejb3/DeploymentUnit;Lorg/jboss/ejb3/EAR;)V at org.jboss.ejb3.embedded.EJB3StandaloneDeployment.<init>(EJB3StandaloneDeployment.java:49) at org.jboss.ejb3.embedded.EJB3StandaloneDeployer.create(EJB3StandaloneDeployer.java:438) at com.dolby.pics.test.AbstractEJBTestCase.startupEmbeddedJboss(AbstractEJBTestCase.java:84) at com.dolby.pics.test.TestSetupWrapper.setUp(TestSetupWrapper.java:32) at junit.extensions.TestSetup$1.protect(TestSetup.java:22) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.extensions.TestSetup.run(TestSetup.java:27) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:210) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:135) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:122) at org.apache.maven.surefire.Surefire.run(Surefire.java:129) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:225) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:747) {noformat} The error as you can see is an incompatability between {noformat} org.jboss.ejb3.embedded.EJB3StandaloneDeployment {noformat} and {noformat} org.jboss.ejb3.Ejb3Deployment {noformat} I'm guessing that these are from different jars and have been bundled into the same jar without a compile any tests to check that they are compatible. My code worked absolutely fine with alpha 8 of the embeddable container. -- 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, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (JBREM-605) Inform a server side listener that a callback has been delivered.

by Ron Sigal (JIRA)

Inform a server side listener that a callback has been delivered. ----------------------------------------------------------------- Key: JBREM-605 URL: http://jira.jboss.com/jira/browse/JBREM-605 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.2.0.Beta1 (Bluto) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.2.0.Beta1 (Bluto) JBossMessaging has a need to know that a Callback has been pulled to the client side and has been processed. See JBMESSAGING-207 for some discussion. -- 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, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (JBREM-601) Integrate http with messaging

by Ron Sigal (JIRA)

Integrate http with messaging ----------------------------- Key: JBREM-601 URL: http://jira.jboss.com/jira/browse/JBREM-601 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.2.0.Beta1 (Bluto) Reporter: Ron Sigal Assigned To: Tom Elrod Fix For: 2.2.0.Beta1 (Bluto) A few changes need to be made for the http transport to work with JBossMessaging. -- 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, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-3411) Port EARDeployer and complete JavaEE5 support

by Scott M Stark (JIRA)

Port EARDeployer and complete JavaEE5 support --------------------------------------------- Key: JBAS-3411 URL: http://jira.jboss.com/jira/browse/JBAS-3411 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Deployment services Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: JBossAS-5.0.0.Beta The EARDeployer needs to be ported to the new VDF and the JavaEE 5 changes completed -- 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, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (JBTM-115) XTS trailmap talks about webMethods only deployment

by Mark Little (JIRA)

XTS trailmap talks about webMethods only deployment --------------------------------------------------- Key: JBTM-115 URL: http://jira.jboss.com/jira/browse/JBTM-115 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Demonstrator, WS-T Implementation Affects Versions: 4.2.1 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.2.2 -- 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, 6 months

2
6
0 / 0

[JBoss JIRA] Created: (JBAS-3636) Port HASingletonElectionPolicy to Branch_4_0

by Brian Stansberry (JIRA)

Port HASingletonElectionPolicy to Branch_4_0 -------------------------------------------- Key: JBAS-3636 URL: http://jira.jboss.com/jira/browse/JBAS-3636 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Alex Fu Fix For: JBossAS-4.0.6.CR1 -- 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, 6 months

3
4
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 September 2006