July 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBSEAM-322) DateWrapper is not registered for remoting. Javascript-Java conversion of date types fails.

by Jens (JIRA)

DateWrapper is not registered for remoting. Javascript-Java conversion of date types fails. ------------------------------------------------------------------------------------------- Key: JBSEAM-322 URL: http://jira.jboss.com/jira/browse/JBSEAM-322 Project: JBoss Seam Issue Type: Bug Components: Remoting Affects Versions: 1.0.1 Environment: All Reporter: Jens in WrapperFactory.java the DateWrapper wrapper class is not registered. Javascript remote calls cannot be converted to Java Date type. This line needs to be added: registerWrapper("date", DateWrapper.class); -- 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, 10 months

3
2
0 / 0

[JBoss JIRA] Created: (JBAS-3443) JBossCacheService should not hold a direct ref to TreeCache service bean

by Brian Stansberry (JIRA)

JBossCacheService should not hold a direct ref to TreeCache service bean ------------------------------------------------------------------------ Key: JBAS-3443 URL: http://jira.jboss.com/jira/browse/JBAS-3443 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Web (Tomcat) service Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-4.0.5.CR1 Don't call TreeCacheMBean.getInstance() -- just use the mbean proxy. One thing this means is for certain operations the TCCL needs to be set to the webapp classloader. -- 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, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-263) malformed '<a' tag causes Javadoc to fail

by Michael Newcomb (JIRA)

malformed '<a' tag causes Javadoc to fail ----------------------------------------- Key: JGRP-263 URL: http://jira.jboss.com/jira/browse/JGRP-263 Project: JGroups Issue Type: Bug Affects Versions: 2.3 SP1 Environment: JDK 1.5 Reporter: Michael Newcomb Assigned To: Bela Ban You can't build javadoc because of some bad '<a' tags. (http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5082928). It seems that it affects mostly where collections have been 'generified' in the javadocs: /** Map<Address, Rsp> */ in RspList.java. So, in IntelliJ, search for "<a" in src and replace all of them with < and >. It isn't too many files: GroupRequest.java RequestCorrelator.java FC.java FRAG2.java SEQUENCER.java STATS.java TP.java RspList.java Util.java Digest.java NAKACK.java Thanks, Michael -- 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, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JBREM-551) org.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(java_serialization) failure

by Ron Sigal (JIRA)

org.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(java_serialization) failure ------------------------------------------------------------------------------------------------ Key: JBREM-551 URL: http://jira.jboss.com/jira/browse/JBREM-551 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.0.0.CR1 (Boon) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.0.0.CR1 (Boon) There seem to be two sources of exceptions here: 1. When a Connector shuts down and a MultiplexingManager is still running on remote end (not sure how this happened), the remote OutputMultiplexor will get "Broken pipe" exceptions. 2. When a Connector shuts down, the master MultiplexServerInvoker can shut down a virtual MultiplexServerInvoker, interruptting an acceptThread, which cause the VirtualServerSocket to think it has reached end of file. Not sure how these problems caused the test to fail, however. -- 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, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-3444) org.jboss.test.naming.test.ENCUnitTestCase ends with errors

by Jaroslaw Kijanowski (JIRA)

org.jboss.test.naming.test.ENCUnitTestCase ends with errors ----------------------------------------------------------- Key: JBAS-3444 URL: http://jira.jboss.com/jira/browse/JBAS-3444 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Suite Affects Versions: JBossAS-5.0.0.Beta Environment: win xp Reporter: Jaroslaw Kijanowski org.jboss.test.naming.test.ENCUnitTestCase ends with two errors, because nessesary queues and topics aren't present for the "all" instance. ENCUnitTestCase calls accessENC() method in org.jboss.test.naming.ejb.TestEncBean.java. The last two methods of the if-block (testResourceEnvEntries and testMessageDestinationRefs) cause NameNotFoundException: testQueue not bound. They try to use the queues "res/aQueue" and "mdr/ConsumesProducesJNDIName". These queues are "mapped" in the jboss-head/testsuite/src/resources/naming/jar/META-INF/jboss.xml to "queue/testQueue" and "queue/A", but these two queues don't exist. The last method (testMessageDestinationRefs) try to use also the topic "mdr/ProducesLink", which is "mapped" in jboss-head/testsuite/src/resources/naming/jar/META-INF/ejb-jar.xml to "TestTopic" which is "mapped" in jboss-head/testsuite/src/resources/naming/jar/META-INF/jboss.xml to "topic/testTopic" cause an errror, because the tpic isnt't present too. To fix these errors: copy server/default/deploy/jms/jbossmq-destinations-service.xml to server/all/deploy/jms/jbossmq-destinations-service.xml and uncomment the two queues "testQueue" and "A" and the first topic "testTopic". -- 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, 10 months

4
7
0 / 0

[JBoss JIRA] Created: (JBRULES-384) Unable to remove a rule after package was merged (addPackage on RuleBase)

by Michael Neale (JIRA)

Unable to remove a rule after package was merged (addPackage on RuleBase) ------------------------------------------------------------------------- Key: JBRULES-384 URL: http://jira.jboss.com/jira/browse/JBRULES-384 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Rule Assemply/SPI Affects Versions: 3.0.3 Reporter: Michael Neale Assigned To: Michael Neale Fix For: 3.0.4, 3.1-m1 Problem is RuleBase was not keeping track of new Rule instances that were added to the RuleBase in binary form. Easy fixed. Need to put in 3.0.x and trunk branches. -- 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, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-385) Compiler is reporting too many errors when a semantic error occurs

by Michael Neale (JIRA)

Compiler is reporting too many errors when a semantic error occurs ------------------------------------------------------------------ Key: JBRULES-385 URL: http://jira.jboss.com/jira/browse/JBRULES-385 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Drl Parser/Builder Affects Versions: 3.0.3 Reporter: Michael Neale Assigned To: Michael Neale Problem is when an error appears, all the error handlers report an error. Added a flag to indicate that a given block is actually in error or not. To fix in both 3.0.x and trunk branches. -- 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, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBTM-107) Update WS-TXM documents

by Mark Little (JIRA)

Update WS-TXM documents ----------------------- Key: JBTM-107 URL: http://jira.jboss.com/jira/browse/JBTM-107 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Documentation Reporter: Mark Little Assigned To: Mark Little Fix For: 4.2.1 -- 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, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBCACHE-694) Collection added to itself causes stack explosion in toString()

by Bela Ban (JIRA)

Collection added to itself causes stack explosion in toString() --------------------------------------------------------------- Key: JBCACHE-694 URL: http://jira.jboss.com/jira/browse/JBCACHE-694 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: PojoCache Affects Versions: 1.4.0, 1.3.0.SP2, 1.3.0.SP1, 1.3.0, 1.2.4SP2, 1.2.4SP1, 1.2.4, 1.2.4beta, 1.2.3, 1.2.2, 1.2.1, 1.2 Reporter: Bela Ban Assigned To: Manik Surtani This works in plain Java. How to reproduce: - runShellDemo.sh/bat sourceRelative("aopWithTx.bsh"); tree.putObject("list", new ArrayList()); list=tree.getObject("list"); list.add(list); list.toString(); BOOOM Some of the exception trace: java.lang.StackOverflowError at org.jboss.cache.Fqn.get(Fqn.java:257) at org.jboss.cache.TreeCache.findNode(TreeCache.java:5606) at org.jboss.cache.TreeCache.findNode(TreeCache.java:5577) at org.jboss.cache.TreeCache._get(TreeCache.java:3457) at org.jboss.cache.aop.InternalDelegate.get(InternalDelegate.java:126) at org.jboss.cache.aop.InternalDelegate.getAopInstanceWithGravitation(InternalDelegate.java:78) at org.jboss.cache.aop.InternalDelegate.getPojoWithGravitation(InternalDelegate.java:231) at org.jboss.cache.aop.TreeCacheAopDelegate._getObject(TreeCacheAopDelegate.java:74) at org.jboss.cache.aop.PojoCache._getObject(PojoCache.java:722) at org.jboss.cache.aop.PojoCache.getObject(PojoCache.java:416) at org.jboss.cache.aop.collection.CachedListImpl.get(CachedListImpl.java:56) at org.jboss.cache.aop.collection.CachedListAbstract.toString(CachedListAbstract.java:155) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.cache.aop.collection.CollectionInterceptorUtil.invoke(CollectionInterceptorUtil.java:124) at org.jboss.cache.aop.collection.CachedListInterceptor.invoke(CachedListInterceptor.java:132) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98) at AOPClassProxy$0.toString(AOPClassProxy$0.java) at java.lang.String.valueOf(String.java:2615) at java.lang.StringBuffer.append(StringBuffer.java:220) at org.jboss.cache.aop.collection.CachedListAbstract.toString(CachedListAbstract.java:156) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.cache.aop.collection.CollectionInterceptorUtil.invoke(CollectionInterceptorUtil.java:124) at org.jboss.cache.aop.collection.CachedListInterceptor.invoke(CachedListInterceptor.java:132) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98) at AOPClassProxy$0.toString(AOPClassProxy$0.java) at java.lang.String.valueOf(String.java:2615) at java.lang.StringBuffer.append(StringBuffer.java:220) at org.jboss.cache.aop.collection.CachedListAbstract.toString(CachedListAbstract.java:156) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.cache.aop.collection.CollectionInterceptorUtil.invoke(CollectionInterceptorUtil.java:124) at org.jboss.cache.aop.collection.CachedListInterceptor.invoke(CachedListInterceptor.java:132) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98) at AOPClassProxy$0.toString(AOPClassProxy$0.java) at java.lang.String.valueOf(String.java:2615) at java.lang.StringBuffer.append(StringBuffer.java:220) at org.jboss.cache.aop.collection.CachedListAbstract.toString(CachedListAbstract.java:156) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.cache.aop.collection.CollectionInterceptorUtil.invoke(CollectionInterceptorUtil.java:124) at org.jboss.cache.aop.collection.CachedListInterceptor.invoke(CachedListInterceptor.java:132) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98) at AOPClassProxy$0.toString(AOPClassProxy$0.java) at java.lang.String.valueOf(String.java:2615) at java.lang.StringBuffer.append(StringBuffer.java:220) at org.jboss.cache.aop.collection.CachedListAbstract.toString(CachedListAbstract.java:156) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.cache.aop.collection.CollectionInterceptorUtil.invoke(CollectionInterceptorUtil.java:124) at org.jboss.cache.aop.collection.CachedListInterceptor.invoke(CachedListInterceptor.java:132) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98) at AOPClassProxy$0.toString(AOPClassProxy$0.java) at java.lang.String.valueOf(String.java:2615) at java.lang.StringBuffer.append(StringBuffer.java:220) at org.jboss.cache.aop.collection.CachedListAbstract.toString(CachedListAbstract.java:156) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.cache.aop.collection.CollectionInterceptorUtil.invoke(CollectionInterceptorUtil.java:124) at org.jboss.cache.aop.collection.CachedListInterceptor.invoke(CachedListInterceptor.java:132) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98) at AOPClassProxy$0.toString(AOPClassProxy$0.java) at java.lang.String.valueOf(String.java:2615) at java.lang.StringBuffer.append(StringBuffer.java:220) at org.jboss.cache.aop.collection.CachedListAbstract.toString(CachedListAbstract.java:156) at sun.reflect.GeneratedMethodAccessor9.invoke(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, 10 months

3
5
0 / 0

[JBoss JIRA] Created: (BPEL-199) BPEL reader does not contain logic to parse 1.1 fault handlers.

by Jiehuan Li (JIRA)

BPEL reader does not contain logic to parse 1.1 fault handlers. --------------------------------------------------------------- Key: BPEL-199 URL: http://jira.jboss.com/jira/browse/BPEL-199 Project: JBoss jBPM BPEL Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM BPEL 1.1 beta 1 Environment: JBoss 4.0.4 GA patch 1 on windows. Reporter: Jiehuan Li Assigned To: Alejandro Guizar >From Alex: I just reviewed the BPEL reader and it does not contain logic to parse 1.1 fault handlers, even tough the execution logic deals with them property. Please open a JIRA issue. -- 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, 10 months

2
3
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 July 2006