June 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-887) Add "collect" conditional element

by Fernando Meyer (JIRA)

Add "collect" conditional element --------------------------------- Key: JBRULES-887 URL: http://jira.jboss.com/jira/browse/JBRULES-887 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Fernando Meyer Assigned To: Fernando Meyer -- 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 month

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-889) suport for memberOf and not memberOf

by Fernando Meyer (JIRA)

suport for memberOf and not memberOf ------------------------------------- Key: JBRULES-889 URL: http://jira.jboss.com/jira/browse/JBRULES-889 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Fernando Meyer Assigned To: Fernando Meyer -- 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 month

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-884) "not contains" and "not matches" for constraints

by Fernando Meyer (JIRA)

"not contains" and "not matches" for constraints ------------------------------------------------ Key: JBRULES-884 URL: http://jira.jboss.com/jira/browse/JBRULES-884 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Fernando Meyer Assigned To: Fernando Meyer -- 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 month

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-882) Add 'forall' Conditional Element

by Fernando Meyer (JIRA)

Add 'forall' Conditional Element -------------------------------- Key: JBRULES-882 URL: http://jira.jboss.com/jira/browse/JBRULES-882 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Fernando Meyer Assigned To: Fernando Meyer -- 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 month

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-883) <and> <or> nesting inside CEs

by Fernando Meyer (JIRA)

<and> <or> nesting inside CEs ------------------------------ Key: JBRULES-883 URL: http://jira.jboss.com/jira/browse/JBRULES-883 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Fernando Meyer Assigned To: Fernando Meyer -- 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 month

1
1
0 / 0

[JBoss JIRA] Commented: (EJBTHREE-433) PersistenceUnitDeployment doesn't work for RESOURCE_LOCAL configuration

by Marco Tedone (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-433?page=comments#action_12366552 ] Marco Tedone commented on EJBTHREE-433: --------------------------------------- [quote] In general, in Java EE environments, a transaction-type of RESOURCE_LOCAL assumes that a non-JTA datasource will be provided. In a Java EE environment, if this element is not specified, the default is JTA [/quote] This means in general, doesn't say it's mandatory. On the other side if I can specify a RESOURCE_LOCAL transaction type with only properties in a J2SE environment, why shouldn't I be able to define it in a EE environment? > PersistenceUnitDeployment doesn't work for RESOURCE_LOCAL configuration > ----------------------------------------------------------------------- > > Key: EJBTHREE-433 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-433 > Project: EJB 3.0 > Issue Type: Bug > Affects Versions: EJB 3.0 RC6 - PFD > Reporter: Christian Bauer > Assigned To: Carlo de Wolf > Priority: Critical > Fix For: AS 4.2.0 CR1 > > > Trying to deploy a persistence.xml with a resource local persistence unit: > <persistence-unit name="caveatemptorLocalDatabase" transaction-type="RESOURCE_LOCAL"> > <properties> > <property name="hibernate.ejb.cfgfile" value="/hibernate.cfg.xml"/> > <property name="hibernate.archive.autodetection" value="none"/> > </properties> > </persistence-unit> > 02:23:23,241 INFO MCKernelAbstraction:79 - installing bean: persistence.units:jar=classes.jar,unitName=caveatemptorLocalDatabase with dependencies: > 02:23:23,247 ERROR AbstractKernelController:350 - Error installing to Start: name=persistence.units:jar=classes.jar,unitName=caveatemptorLocalDatabase state=Create > java.lang.RuntimeException: You have not defined a jta-data-source for a JTA enabled persistence context named: caveatemptorLocalDatabase > at org.jboss.ejb3.entity.PersistenceUnitDeployment.start(PersistenceUnitDeployment.java:240) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.jboss.joinpoint.plugins.reflect.ReflectMethodJoinPoint.dispatch(ReflectMethodJoinPoint.java:72) > at org.jboss.kernel.plugins.dependency.KernelControllerContextActions.dispatchJoinPoint(KernelControllerContextActions.java:96) > at org.jboss.kernel.plugins.dependency.KernelControllerContextActions$LifecycleAction.installAction(KernelControllerContextActions.java:476) > at org.jboss.kernel.plugins.dependency.KernelControllerContextActions$KernelControllerContextAction.install(KernelControllerContextActions.java:171) > at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) > at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:226) > at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:593) > at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:346) > at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:438) > at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:379) > at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:225) > at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:151) > at org.jboss.kernel.plugins.dependency.AbstractKernelController.install(AbstractKernelController.java:79) > at org.jboss.kernel.plugins.dependency.AbstractKernelController.install(AbstractKernelController.java:73) > at org.jboss.ejb3.MCKernelAbstraction.install(MCKernelAbstraction.java:86) > at org.jboss.ejb3.Ejb3Deployment.startPersistenceUnits(Ejb3Deployment.java:599) > at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:452) > at org.jboss.ejb3.embedded.EJB3StandaloneDeployer.start(EJB3StandaloneDeployer.java:450) > at org.jboss.ejb3.embedded.EJB3StandaloneBootstrap.scanClasspath(EJB3StandaloneBootstrap.java:199) > at org.hibernate.ce.auction.test.runtime.EJB3Container.startup(Unknown Source) -- 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 month

1
0
0 / 0

[JBoss JIRA] Created: (JBCACHE-1111) PojoCache does not work with BuddyReplication and autoDataGravitation=false

by Brian Stansberry (JIRA)

PojoCache does not work with BuddyReplication and autoDataGravitation=false --------------------------------------------------------------------------- Key: JBCACHE-1111 URL: http://jira.jboss.com/jira/browse/JBCACHE-1111 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: PojoCache Affects Versions: 2.0.0.CR2 Reporter: Brian Stansberry Assigned To: Jason T. Greene Priority: Blocker When buddy replication is enabled and autoDataGravitation=false, PojoCache does not work. Setting autoDataGravitation=false is the only realistic mode for a BR-enabled app, so this basically means BR doesn't work with PojoCache. The BR-enabled FIELD granularity session repl tests in AS trunk all fail because of this. The problem is basically that when PojoCache traverses a PojoReference to find the actual pojo in _JBossInternal_, it doesn't add a setForceDataGravitation=true Option before making the invocation. As a result, the node with the actual pojo is not gravitated. If you look at o.j.c.p.impl.InternalHelper.get(Fqn fqn, Object key, boolean gravitate), that's where the required Option would be set. But if you search for calls that pass 'true' as the 'gravitate' param, you find that they all lead to unused methods. In the 1.4 branch, those methods are used. Seems this got broken in HEAD. -- 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 month

2
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-986) Sort out JBoss AS dependencies

by Tim Fox (JIRA)

Sort out JBoss AS dependencies ------------------------------ Key: JBMESSAGING-986 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-986 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.4.0.CR1 Currently we've imported JBossAS in the lib area of our project to keep the project compiling. This is hardly an acceptable solution. The proper solution involves: 1) Deciding what JBossAS depenencies we need and getting rid of artificially introduced dependencies 2) Work with AS team to identifiy the AS interfaces that need to be isolated and exposed in the repository. -- 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 month

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-4146) Update to JacORB 2.3.0.GA

by Fernando Nasser (JIRA)

Update to JacORB 2.3.0.GA ------------------------- Key: JBAS-4146 URL: http://jira.jboss.com/jira/browse/JBAS-4146 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Fernando Nasser Fix For: JBossAS-5.0.0.Beta3 We are currently using a locally patches JacORB 2.2.4. The 2.30.GA includes our patch and also has some other fixes as well. >From Francisco Reverbel: Yes, that patch is in JacORB 2.3.0, which includes at least another RMI-related fix as well. It would be good to upgrade. (Disclaimer: I have never tested JacORB 2.3.0 with JBossAS. A full run of the iiop testsuite is needed.) Notice that JacORB 2.3.0 has a "new property interop.sun to fix RMI/IIOP related interoperability issues". Perhaps this makes a difference with respect to the iiop testcase that has been recently disabled on JDK1.5... NOTE: This upgrade involves JBoss TS recovery -- 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 month

3
5
0 / 0

[JBoss JIRA] Created: (GPD-104) review the task configuration general form

by Koen Aers (JIRA)

review the task configuration general form ------------------------------------------ Key: GPD-104 URL: http://jira.jboss.com/jira/browse/GPD-104 Project: JBoss jBPM GPD Issue Type: Task Affects Versions: jBPM JPDL Designer 3.1.0.alpha4 Reporter: Koen Aers Assigned To: Koen Aers Fix For: jBPM JPDL Designer 3.1.0.beta1 - reuse the named element and describable configuraiton forms - move the duedate, notify, blocking, signalling and priority items to a details configuration form - move the form generation button to the details configuration form -- 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 month

1
1
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