January 2007 - jboss-jira - Jboss List Archives

by 95kj22k＠shengshala.com

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-830) Support for Bean Scripting Framework (BSF)

by Edward Staub (JIRA)

Support for Bean Scripting Framework (BSF) ------------------------------------------ Key: JBPM-830 URL: http://jira.jboss.com/jira/browse/JBPM-830 Project: JBoss jBPM Issue Type: Feature Request Components: Core Engine Reporter: Edward Staub Assigned To: Tom Baeyens I'm planning to implement support for BSF and will contribute it back if it's wanted. (BSF supports pluggable scripting engines and pluggable domain classes.) I'm posting this here, rather than on the forum, to make sure we don't end up with duplicate efforts. If this was the wrong thing to do, apologies in advance. My current plans are to just provide a way to configure a global scripting engine via jbpm.cfg.xml. In the future, it would be desirable to make this settable in the Process Definition. I'll make sure this works with BeanShell and Groovy - other folks will have to vet Rhino, etc. Current estimate is "before end of February". Any thoughts? Requests? Is this useful to others? I haven't seen much about it on the forums. -- 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, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-792) Modify testing framework to use with priority JGroups stack configurations we ship with the release

by Ovidiu Feodorov (JIRA)

Modify testing framework to use with priority JGroups stack configurations we ship with the release --------------------------------------------------------------------------------------------------- Key: JBMESSAGING-792 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-792 Project: JBoss Messaging Issue Type: Task Components: Tests and Performance Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.Beta2 -- 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, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-4038) HiLoKeyGeneratorFactory IllegalArgumentException

by Manuel Duran Aguete (JIRA)

HiLoKeyGeneratorFactory IllegalArgumentException ------------------------------------------------ Key: JBAS-4038 URL: http://jira.jboss.com/jira/browse/JBAS-4038 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.0.5.GA Environment: java version "1.5.0_10" Debian Sarge 2.6.18-2-686 #1 SMP Wed Nov 8 19:52:12 UTC 2006 i686 GNU/Linux jboss-4.0.5.GA JEMS INSTALLER 1.2.0.GA with ejb3-clustered fresh install Reporter: Manuel Duran Aguete When we try to use the HiLoKeyGenerator the following exception occurs: java.lang.IllegalArgumentException: no such field at java.io.ObjectInputStream$GetFieldImpl.getFieldOffset(ObjectInputStream.java:2092) at java.io.ObjectInputStream$GetFieldImpl.get(ObjectInputStream.java:2028) at org.jboss.ejb.plugins.keygenerator.hilo.HiLoKeyGeneratorFactory.readObject(HiLoKeyGeneratorFactory.java:431) 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 java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:946) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1809) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348) at java.rmi.MarshalledObject.get(MarshalledObject.java:135) at org.jnp.interfaces.MarshalledValuePair.get(MarshalledValuePair.java:72) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:652) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587) at javax.naming.InitialContext.lookup(InitialContext.java:351) at net.caixagaliciamoviles.plataforma.sms.mensaje.SMSIdGenerator.getSMSId(SMSIdGenerator.java:27) The calling code is : public static String getSMSId() { log.info ("Generando SMSID"); try { InitialContext ctx = new InitialContext(); KeyGeneratorFactory kgf = (KeyGeneratorFactory) ctx.lookup("HiLoKeyGeneratorFactory"); KeyGenerator kg = kgf.getKeyGenerator (); Long id = (Long) kg.generateKey (); String txtId = String.valueOf (id); log.info ("El SMSID generado es [" + txtId + "]"); return txtId; } catch (Exception e){ log.warn ("Error generando SMSID",e); } log.info ("El ID es BLANCO"); return ""; } The exception is thrown at " KeyGeneratorFactory kgf = (KeyGeneratorFactory) ctx.lookup("HiLoKeyGeneratorFactory"); If we change to use de UUID generator no exception is thrown in lookup. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-372) Basic splitter

by Mark Little (JIRA)

Basic splitter -------------- Key: JBESB-372 URL: http://jira.jboss.com/jira/browse/JBESB-372 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Content Based Routing Affects Versions: 4.0 CR2 Reporter: Mark Little Assigned To: Kurt Stam Priority: Optional Fix For: 4.0 Driven by config and Java. -- 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, 3 months

2
1
0 / 0

[JBoss JIRA] Updated: (JBAS-3321) Support for "method-attributes" including "transaction-timeout" for MDBs

by Weston Price (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3321?page=all ] Weston Price updated JBAS-3321: ------------------------------- Assignee: Weston Price (was: Scott M Stark) > Support for "method-attributes" including "transaction-timeout" for MDBs > ------------------------------------------------------------------------ > > Key: JBAS-3321 > URL: http://jira.jboss.com/jira/browse/JBAS-3321 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: EJB2 > Affects Versions: JBossAS-4.0.4.GA > Reporter: Galder Zamarreno > Assigned To: Weston Price > > Looking at jboss_4_0.dtd it seems that MDBs in JBoss do not support the use of "method-attributes", > particularly "transaction-timeout", why is this? > I have looked in to this a little and it doesn't seem to be prohibited by the J2EE specs, in fact > Weblogic seems to support the setting of transaction timeouts on MDBs, so why not JBoss? > I guess it is either an error or a deliberate design decision not to support it, if it's the latter I > would be interested to hear what the rational is? > Adrian Brock wrote: > Because the MDB transaction is not started by the EJB container > like the other EJB types. > Raise a feature request. There is no reason why the ServerSessionPool > cannot ask the EJB container for this information. > _________________ > Adrian Brock > Chief Scientist > JBoss, Inc. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBREM-694) Correct regression in handling timeout in MicroSocketClientInvoker

by Ron Sigal (JIRA)

Correct regression in handling timeout in MicroSocketClientInvoker ------------------------------------------------------------------ Key: JBREM-694 URL: http://jira.jboss.com/jira/browse/JBREM-694 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.2.0.Alpha7 Between versions 1.16.2.14 and 1.16.2.15 the creation of a ServerAddress in org.jboss.remoting.transport.socket.MicroSocketClientInvoker.setup() reverted to an incorrect state. -- 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, 3 months

1
1
0 / 0

[JBoss JIRA] Updated: (JBCACHE-331) Opt locking should not replay modifications

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-331?page=all ] Manik Surtani updated JBCACHE-331: ---------------------------------- Affects Version/s: 1.4.1.GA 1.4.0.GA 1.3.0.GA (was: 1.2.4beta) > Opt locking should not replay modifications > ------------------------------------------- > > Key: JBCACHE-331 > URL: http://jira.jboss.com/jira/browse/JBCACHE-331 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 1.3.0.GA, 1.4.0.GA, 1.4.1.GA > Reporter: Manik Surtani > Assigned To: Manik Surtani > Priority: Minor > Fix For: 2.1.0.GA > > > ... try and copy state from workspace nodes to tree nodes, both locally and on remote caches. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBCACHE-953) Class cast exception on DefaultDataVersion while using Hibernate OptimisticTreeCache

by cgs (JIRA)

Class cast exception on DefaultDataVersion while using Hibernate OptimisticTreeCache ------------------------------------------------------------------------------------ Key: JBCACHE-953 URL: http://jira.jboss.com/jira/browse/JBCACHE-953 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.4.1.GA Reporter: cgs Assigned To: Manik Surtani [01:35:34.171] org.jboss.cache.interceptors.OrderedSynchronizationHandler.afterCompletion failed calling afterCompletion() on TxInterceptor.RemoteSynchronizationHandler(gtx=GlobalTransaction:<10.236.26.142:43026>:138, tx=Transaction[]) [01:35:34.171] java.lang.ClassCastException: org.hibernate.cache.OptimisticTreeCache$DataVersionAdapter cannot be cast to org.jboss.cache.optimistic.DefaultDataVersion [01:35:34.171] at org.jboss.cache.interceptors.OptimisticValidatorInterceptor.commit(OptimisticValidatorInterceptor.java:224) [01:35:34.171] at org.jboss.cache.interceptors.OptimisticValidatorInterceptor.invoke(OptimisticValidatorInterceptor.java:78) [01:35:34.171] at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68) [01:35:34.171] at org.jboss.cache.interceptors.OptimisticLockingInterceptor.invoke(OptimisticLockingInterceptor.java:107) [01:35:34.171] at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68) [01:35:34.171] at org.jboss.cache.interceptors.OptimisticReplicationInterceptor.invoke(OptimisticReplicationInterceptor.java:115) [01:35:34.171] at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68) [01:35:34.171] at org.jboss.cache.interceptors.TxInterceptor.handleCommitRollback(TxInterceptor.java:715) [01:35:34.171] at org.jboss.cache.interceptors.TxInterceptor.runCommitPhase(TxInterceptor.java:757) [01:35:34.171] at org.jboss.cache.interceptors.TxInterceptor$RemoteSynchronizationHandler.afterCompletion(TxInterceptor.java:1063) [01:35:34.171] at org.jboss.cache.interceptors.OrderedSynchronizationHandler.afterCompletion(OrderedSynchronizationHandler.java:83) [01:35:34.171] at com.caucho.transaction.TransactionImpl.callAfterCompletion(TransactionImpl.java:895) [01:35:34.171] at com.caucho.transaction.TransactionImpl.commit(TransactionImpl.java:715) [01:35:34.171] at com.caucho.transaction.TransactionManagerImpl.commit(TransactionManagerImpl.java:263) [01:35:34.171] at org.jboss.cache.interceptors.TxInterceptor.handleRemoteCommitRollback(TxInterceptor.java:642) [01:35:34.171] at org.jboss.cache.interceptors.TxInterceptor.invoke(TxInterceptor.java:146) [01:35:34.171] at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68) [01:35:34.171] at org.jboss.cache.interceptors.CacheMgmtInterceptor.invoke(CacheMgmtInterceptor.java:183) [01:35:34.171] at org.jboss.cache.TreeCache.invokeMethod(TreeCache.java:5710) [01:35:34.171] at org.jboss.cache.TreeCache._replicate(TreeCache.java:5056) [01:35:34.171] at sun.reflect.GeneratedMethodAccessor215.invoke(Unknown Source) [01:35:34.171] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [01:35:34.171] at java.lang.reflect.Method.invoke(Method.java:597) [01:35:34.171] at org.jgroups.blocks.MethodCall.invoke(MethodCall.java:330) [01:35:34.171] at org.jgroups.blocks.RpcDispatcher.handle(RpcDispatcher.java:281) [01:35:34.171] at org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:650) [01:35:34.171] at org.jgroups.blocks.RequestCorrelator.receiveMessage(RequestCorrelator.java:535) [01:35:34.171] at org.jgroups.blocks.RequestCorrelator.receive(RequestCorrelator.java:358) [01:35:34.171] at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.up(MessageDispatcher.java:775) [01:35:34.171] at org.jgroups.JChannel.up(JChannel.java:1091) [01:35:34.171] at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:377) [01:35:34.171] at org.jgroups.stack.ProtocolStack.receiveUpEvent(ProtocolStack.java:393) [01:35:34.171] at org.jgroups.stack.Protocol.passUp(Protocol.java:538) [01:35:34.171] at org.jgroups.protocols.pbcast.STATE_TRANSFER.up(STATE_TRANSFER.java:158) [01:35:34.171] at org.jgroups.stack.UpHandler.run(Protocol.java:60) [01:35:34.171] -- 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, 3 months

2
6
0 / 0

[JBoss JIRA] Commented: (JBRULES-214) goddamn keyword collisions damn it damn damn

by Edson Tirelli (JIRA)

[ http://jira.jboss.com/jira/browse/JBRULES-214?page=comments#action_12351940 ] Edson Tirelli commented on JBRULES-214: --------------------------------------- Most of the conflicts are solved in revision #9193. See following sample: ================================== package test.rule.when.end.package.mine; global java.lang.String accumulate; function boolean eval() { return true; } rule type1 when $id : Something( duration == "foo") then The.end(); end; attributes; rule; package; end =========================== Only case I was not able to solve yet is when the first word in a dotted name is a reserved word. For instance, the following will not work, because "rule" is the first word in the dotted name and is a reserved word. import rule.mypackage.MyClass; But the following works fine: import org.rule.mypackage.MyClass; I will investigate more for the final 3.2 release, but for 3.1 milestone 1 I will probably let as it is now. > goddamn keyword collisions damn it damn damn > -------------------------------------------- > > Key: JBRULES-214 > URL: http://jira.jboss.com/jira/browse/JBRULES-214 > Project: JBoss Rules > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Drl Parser/Builder > Affects Versions: 3.0-rc1 > Reporter: Michael Neale > Assigned To: Edson Tirelli > Priority: Critical > Fix For: 3.1-m3 > > > Getting more complaints about collisions with keywords. Things like "end" are obvious, but even "duration" etc... > Parser possibly needs to be a bit cleverer (not sure why duration is barfing.. but anyway). > I guess the only clear way forward is to enforce newline characters. > Most often the problem happens in the LHS. On the RHS its just "end" that is a problem. -- 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, 3 months

1
0
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 January 2007