October 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPORTAL-1769) Portlet disappears in IE 7.0 after it is maximized

by krish p (JIRA)

Portlet disappears in IE 7.0 after it is maximized -------------------------------------------------- Key: JBPORTAL-1769 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1769 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Portlet Affects Versions: 2.6.1 Final Environment: Windows XP, Internet Explorer 7.0 Reporter: krish p Assigned To: Julien Viet I am not able to reproduce the exact issue in this build, http://portal.demo.jboss.com/portal/default but I can definitely see related issues. Essentially, this is the problem: * Add a portlet on the page. * Maximize it, restore it, minimize it, and keep doing this a few times, and at some point, the portlet disappears for the user and cannot ever be restored (unless the portlet is chosen to be added again, and even in that case, it fails occasionally). After doing a fair bit of testing, I've narrowed down the test case to the following: * This does NOT reproduce in Firefox and happens only in IE * Even in IE, it happens ONLY when clicking on the maximize/minimize/restore events DOES NOT work the first time. I am able to see the exact the same issue in the http://portal.demo.jboss.com/portal/default build in IE. The portlet events do not work unless repetitively tried, and in our case, the portlet disappears exactly at that point. In other words, when the portlet event does not get kicked off the first time when the portlet is in the maximized mode, the portlet ends up disappearing when we repeatedly click on that event (be it minimize or restore). It is a little painful to reproduce this but the problem does exist in IE. -- 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

18 years, 2 months

4
21
0 / 0

[JBoss JIRA] Created: (JBAS-4662) XADatasource property names are not using the javabean convention

by Adrian Brock (JIRA)

XADatasource property names are not using the javabean convention ----------------------------------------------------------------- Key: JBAS-4662 URL: http://jira.jboss.com/jira/browse/JBAS-4662 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JCA service Reporter: Adrian Brock Fix For: JBossAS-4.2.2.GA, JBossAS-5.0.0.GA XADataSource properties are not following the javabean convention. i.e. <xa-datasource-property name="lower">value</xa-datasource-property> should work with XADataSourceImpl.setLower() Currently you have to capitalize the name "Lower" to make it work. See org.jboss.resource.connectionmanager.RARDeployment::setManagedConnectionFactoryAttribute(...) for the correct code to do this safely. -- 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

18 years, 2 months

2
6
0 / 0

[JBoss JIRA] Created: (EJBTHREE-698) Exception serialization issue when remotely accessing stateless session bean

by David Green (JIRA)

Exception serialization issue when remotely accessing stateless session bean ---------------------------------------------------------------------------- Key: EJBTHREE-698 URL: http://jira.jboss.com/jira/browse/EJBTHREE-698 Project: EJB 3.0 Issue Type: Bug Reporter: David Green Accessing a remote EJB (Session bean) results in exception. Stack trace follows: 13:54:39,546 ERROR [SocketClientInvoker] Got marshalling exception, exiting java.lang.ClassNotFoundException: [Ljava.lang.StackTraceElement; at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:276) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at org.jboss.remoting.loading.RemotingClassLoader.loadClass(RemotingClassLoader.java:50) at org.jboss.remoting.loading.ObjectInputStreamWithClassLoader.resolveClass(ObjectInputStreamWithClassLoader.java:139) at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1575) at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1496) at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1624) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1323) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1945) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1869) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1945) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1869) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351) at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.receiveObject(JavaSerializationManager.java:128) at org.jboss.remoting.marshal.serializable.SerializableUnMarshaller.read(SerializableUnMarshaller.java:66) at org.jboss.remoting.transport.socket.SocketClientInvoker.transport(SocketClientInvoker.java:279) at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:143) at org.jboss.remoting.Client.invoke(Client.java:525) at org.jboss.remoting.Client.invoke(Client.java:488) at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:55) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:55) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:65) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:102) at $Proxy0.postNotification(Unknown Source) at com.hgea.hch.service.HchClientDelegate.postNotification(HchClientDelegate.java:99) at com.hgea.hch.client.RemoteHchClientTest.testRemotePostNotification(RemoteHchClientTest.java:38) 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:597) at junit.framework.TestCase.runTest(TestCase.java:154) at junit.framework.TestCase.runBare(TestCase.java:127) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:118) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:297) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:672) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:567) -- 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

18 years, 2 months

7
7
0 / 0

[JBoss JIRA] Created: (JBREM-773) Create bisocket sample code

by Ron Sigal (JIRA)

Create bisocket sample code --------------------------- Key: JBREM-773 URL: http://jira.jboss.com/jira/browse/JBREM-773 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.4.0.Beta1 (Pinto) Reporter: Ron Sigal Assigned To: Ron Sigal Priority: Minor Fix For: 2.4.0.Beta1 (Pinto) Give a simple client and server example. Install a security policy on the client that forbids the creation of ServerSockets. -- 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

18 years, 2 months

1
3
0 / 0

[JBoss JIRA] Created: (JBRULES-1216) log4j.xml contained in drools-repository.jar

by mike mcmahon (JIRA)

log4j.xml contained in drools-repository.jar --------------------------------------------- Key: JBRULES-1216 URL: http://jira.jboss.com/jira/browse/JBRULES-1216 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.1, 4.0.0.GA Reporter: mike mcmahon Assigned To: Mark Proctor the file drools-repository/src/main/resources/log4j.xml goes into the jar artifact. this causes problems for end-users who also use log4j since the classloader may choose either log4j.xml -- 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

18 years, 2 months

4
6
0 / 0

[JBoss JIRA] Created: (JBRULES-867) Can't load classes from expanded class dir on windows

by Dan Lipofsky (JIRA)

Can't load classes from expanded class dir on windows ----------------------------------------------------- Key: JBRULES-867 URL: http://jira.jboss.com/jira/browse/JBRULES-867 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Drl Parser/Builder Affects Versions: 3.0.6 Environment: Windows XP SP2 (problem not reproducable on Linux), JDK 1.5.0_11-b03, Ant 1.7.0, Eclipse 3.2.2 Reporter: Dan Lipofsky Assigned To: Mark Proctor Priority: Minor When running some JUnit tests of our rules from an Ant task or from Eclipse, we got the following rule compile errors: org.drools.rule.InvalidRulePackage: Rule Compilation error The import com.bricsnet.core.util.constants cannot be resolved UserGroup cannot be resolved The same rules compile perfectly on the server. On the server the class is question is only available from a JAR file. In Eclipse it in an expanded class dir. In the Ant task both the expanded class dir and the JAR file were in the classpath, but the expanded class dir was first. Putting the JAR first on the classpath solved the problem for the ant task (but this is not possible for eclipse since the JAR is not available). Therefore we believe the problem is specifically related to loading from an expanded class dir. The problem seems to occur on Windows but not Linux. Finally the problem only seems to occur for some classes. All 3 of the classes in the sample rule file below are in the same boat, but for some reason only UserGroup is a problem (it might be the Example 1 (fails): package com.foobar.rules; import com.foobar.core.util.constants.UserGroup; import com.foobar.core.util.security.principal.UserPrincipal; import com.foobar.core.util.security.auth.RuleAuthorization; rule "test_rule" when r: RuleAuthorization() u: UserPrincipal() eval(u.hasGroup(123)) then r.setLevel(RuleAuthorization.READ); end Example 2 (works): package com.foobar.rules; import com.foobar.core.util.security.principal.UserPrincipal; import com.foobar.core.util.security.auth.RuleAuthorization; rule "test_rule" when r: RuleAuthorization() u: UserPrincipal() eval(u.hasGroup(123)) then r.setLevel(RuleAuthorization.READ); end -- 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

18 years, 2 months

5
6
0 / 0

[JBoss JIRA] Created: (JBAOP-395) Release/Packaging holder task

by Kabir Khan (JIRA)

Release/Packaging holder task ------------------------------ Key: JBAOP-395 URL: http://jira.jboss.com/jira/browse/JBAOP-395 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: 2.0.0.alpha5 -- 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

18 years, 2 months

1
6
0 / 0

[JBoss JIRA] Created: (JBRULES-1143) ClassTypeResolver throws an Error

by Michael Neale (JIRA)

ClassTypeResolver throws an Error --------------------------------- Key: JBRULES-1143 URL: http://jira.jboss.com/jira/browse/JBRULES-1143 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Rule Assemply/SPI Affects Versions: 4.0.0.GA Reporter: Michael Neale Assigned To: Mark Proctor Priority: Minor Fix For: FUTURE would be nicer if it was a better exception (or reported it a bit better) - perhaps. Its pretty buried. -- 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

18 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1111) Final methods of POJO's aer never evaluated

by Arjun Dhar (JIRA)

Final methods of POJO's aer never evaluated ------------------------------------------- Key: JBRULES-1111 URL: http://jira.jboss.com/jira/browse/JBRULES-1111 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.0.GA Reporter: Arjun Dhar Assigned To: Mark Proctor Priority: Minor If a POJO defines certain getters as final and they are used in a condition in the Rules, then they do not evaluate properly -- 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

18 years, 2 months

3
8
0 / 0

[JBoss JIRA] Created: (JBRULES-1289) BRMS gives unusable error messages when validating DSL based rules

by Phil Verghese (JIRA)

BRMS gives unusable error messages when validating DSL based rules ------------------------------------------------------------------ Key: JBRULES-1289 URL: http://jira.jboss.com/jira/browse/JBRULES-1289 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-brms Affects Versions: 4.0.2 Reporter: Phil Verghese Assigned To: Mark Proctor The error messages that are shown when you click "Validate" when editing a business rule that uses a DSL in the BRMS are not user-friendly at all. If I make a small typo and misspell the name of an attribute (a very likely thing for a BRMS user to do), and click the Validate button, the error I get back is a big stack trace starting with "java.lang.RuntimeException: SNO: Conversion failed at org.codehaus.janino.UnitCompiler.numericPromotion(UnitCompiler.java) at ..." Nowhere in that stack trace is anything that gives a hint that the error is just a typo of an attribute name. Contrast this with the rather helpful error message I get if I make the same typo when editing a DRL rule: "Unable to create Field Extractor for 'overtimHours'". (The error is that I misspelled overtimeHours). The BRMS needs to give the same type of helpful error message on validation errors when editing a DSL rule. -- 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

18 years, 2 months

3
6
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 October 2007