November 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAOP-538) Swing client that can easily compile and run jboss aop

by Stale Pedersen (JIRA)

Swing client that can easily compile and run jboss aop ------------------------------------------------------ Key: JBAOP-538 URL: http://jira.jboss.com/jira/browse/JBAOP-538 Project: JBoss AOP Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Stale Pedersen Assigned To: Stale Pedersen Priority: Minor -- 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

15 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAOP-621) Adding object to simple meta data without PayloadKey.AS_IS results in ClassCastException

by Carlo de Wolf (JIRA)

Adding object to simple meta data without PayloadKey.AS_IS results in ClassCastException ---------------------------------------------------------------------------------------- Key: JBAOP-621 URL: https://jira.jboss.org/jira/browse/JBAOP-621 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.CR11 Reporter: Carlo de Wolf For the purpose of the bug changed the code in IsLocalInterceptor: invocation.getMetaData().addMetaData("TEST", "TEST", "TEST"); Invocation copy = (Invocation) new MarshalledObjectForLocalCalls(invocation).get(); java.lang.ClassCastException: org.jboss.serial.objectmetamodel.DataContainer$DataContainerOutput cannot be cast to java.io.OutputStream at org.jboss.aop.util.MarshalledValue.writeExternal(MarshalledValue.java:208) at org.jboss.serial.persister.ExternalizePersister.writeData(ExternalizePersister.java:58) at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.describeObject(ObjectDescriptorFactory.java:276) at org.jboss.serial.objectmetamodel.DataContainer$DataContainerOutput.writeObject(DataContainer.java:390) at org.jboss.aop.metadata.SimpleMetaData.writeExternal(SimpleMetaData.java:322) at org.jboss.serial.persister.ExternalizePersister.writeData(ExternalizePersister.java:58) at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.describeObject(ObjectDescriptorFactory.java:276) at org.jboss.serial.objectmetamodel.DataContainer$DataContainerOutput.writeObject(DataContainer.java:390) at org.jboss.aop.joinpoint.MethodInvocation.writeExternal(MethodInvocation.java:376) at org.jboss.ejb3.stateful.StatefulRemoteInvocation.writeExternal(StatefulRemoteInvocation.java:73) at org.jboss.serial.persister.ExternalizePersister.writeData(ExternalizePersister.java:58) at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.describeObject(ObjectDescriptorFactory.java:276) at org.jboss.serial.objectmetamodel.DataContainer$DataContainerOutput.writeObject(DataContainer.java:390) at org.jboss.serial.io.MarshalledObjectForLocalCalls.<init>(MarshalledObjectForLocalCalls.java:38) at org.jboss.ejb3.remoting.IsLocalInterceptor.invokeLocal(IsLocalInterceptor.java:79) at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:71) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.proxy.handler.stateful.StatefulRemoteProxyInvocationHandler.invoke(StatefulRemoteProxyInvocationHandler.java:139) at $Proxy47.setName(Unknown Source) at org.jboss.ejb3.core.test.regression.ejbthree1253.unit.OverriddenProxyFactoryTestCase.test1(OverriddenProxyFactoryTestCase.java:88) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.junit.internal.runners.TestMethod.invoke(TestMethod.java:59) at org.junit.internal.runners.MethodRoadie.runTestMethod(MethodRoadie.java:98) at org.junit.internal.runners.MethodRoadie$2.run(MethodRoadie.java:79) at org.junit.internal.runners.MethodRoadie.runBeforesThenTestThenAfters(MethodRoadie.java:87) at org.junit.internal.runners.MethodRoadie.runTest(MethodRoadie.java:77) at org.junit.internal.runners.MethodRoadie.run(MethodRoadie.java:42) at org.junit.internal.runners.JUnit4ClassRunner.invokeTestMethod(JUnit4ClassRunner.java:88) at org.junit.internal.runners.JUnit4ClassRunner.runMethods(JUnit4ClassRunner.java:51) at org.junit.internal.runners.JUnit4ClassRunner$1.run(JUnit4ClassRunner.java:44) at org.junit.internal.runners.ClassRoadie.runUnprotected(ClassRoadie.java:27) at org.junit.internal.runners.ClassRoadie.runProtected(ClassRoadie.java:37) at org.junit.internal.runners.JUnit4ClassRunner.run(JUnit4ClassRunner.java:42) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:38) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) There is an illegal class cast in MarshalledValue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

4
6
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2246) Portlet invoker exception during portlet window rendering

by Prabhat Jha (JIRA)

Portlet invoker exception during portlet window rendering ---------------------------------------------------------- Key: JBPORTAL-2246 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2246 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Portlet Affects Versions: 2.7.0 Final Reporter: Prabhat Jha Assignee: Thomas Heute Priority: Critical Fix For: 2.7.1 Final Please see related comment at https://jira.jboss.org/jira/browse/JBEPP-12. JBoss] 13:09:48,658 ERROR [InternalPortletContentProvider] Portlet invoker exception during portlet window rendering [JBoss] java.lang.IllegalStateException: No next invoker [JBoss] at org.jboss.portal.portlet.PortletInvokerInterceptor.safeGetNext(PortletInvokerInterceptor.java:123) [JBoss] at org.jboss.portal.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:82) [JBoss] at org.jboss.portal.portlet.management.PortletContainerManagementInterceptorImpl.invoke(PortletContainerManagementInterceptorImpl.java:59) [JBoss] at org.jboss.portal.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:82) [JBoss] at org.jboss.portal.portlet.aspects.portlet.PortalSessionSynchronizationInterceptor.invoke(PortalSessionSynchronizationInterceptor.java:93) [JBoss] at org.jboss.portal.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:82) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
6
0 / 0

[JBoss JIRA] Created: (JBRULES-1663) DRL/DSLR file inclusion

by Paul Ryan (JIRA)

DRL/DSLR file inclusion ----------------------- Key: JBRULES-1663 URL: http://jira.jboss.com/jira/browse/JBRULES-1663 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Documentation, Drl Parser/Builder, drools-brms Reporter: Paul Ryan Assigned To: Mark Proctor The ability to include one rule file in another would be helpful from the stand point of overrides. I know this can be done using the package builder however giving the rule file writer the ability to include a parent rule file by directory would be of great benefit on some projects. This would allow an easy mechanism for override and extension paradigms for rules without moving into full inheritance (very much not needed). It appears that this was possible when rules were still xml by just using entities but that this feature has been overlooked when moving to text based drl files. -- 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

15 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-5968) NullPointerException in WebServiceDeployerEJB

by Carlo de Wolf (JIRA)

NullPointerException in WebServiceDeployerEJB --------------------------------------------- Key: JBAS-5968 URL: https://jira.jboss.org/jira/browse/JBAS-5968 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: JBossAS-5.0.0.CR2 Reporter: Carlo de Wolf Assignee: Alessio Soldano Priority: Critical Fix For: JBossAS-5.0.0.GA 2008-09-16 13:24:10,638 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] (RMI TCP Connection(36)-127.0.0.1) Error installing to Real: name=vfszip:/home/carlo/work/ejb3/testsuite/target/test-lib/bank.jar state=PreReal mode=Manual requiredState=Real org.jboss.deployers.spi.DeploymentException: java.lang.NullPointerException: name cannot be null at org.jboss.wsf.container.jboss50.deployer.WebServiceDeployerEJB.internalDeploy(WebServiceDeployerEJB.java:103) at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50) at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169) at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1285) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1003) at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:944) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:627) at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:541) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:812) at org.jboss.deployment.MainDeployer.redeploy(MainDeployer.java:587) ... Caused by: java.lang.NullPointerException: name cannot be null at javax.management.ObjectName.construct(ObjectName.java:342) at javax.management.ObjectName.<init>(ObjectName.java:1314) at org.jboss.wsf.container.jboss50.deployer.WebServiceDeployerEJB.internalDeploy(WebServiceDeployerEJB.java:99) ... 66 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (JBASPECT-17) Create test(s) for jboss-aspects-remoting

by Carlo de Wolf (JIRA)

Create test(s) for jboss-aspects-remoting ----------------------------------------- Key: JBASPECT-17 URL: http://jira.jboss.com/jira/browse/JBASPECT-17 Project: JBoss Aspects Issue Type: Task Reporter: Carlo de Wolf Assigned To: Carlo de Wolf Fix For: 1.0.0.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

15 years, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-5965) introduce jboss_init_osx.sh

by Marc Lustig (JIRA)

introduce jboss_init_osx.sh ---------------------------- Key: JBAS-5965 URL: https://jira.jboss.org/jira/browse/JBAS-5965 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.CR1 Environment: Mac OSX Reporter: Marc Lustig Priority: Minor Fix For: JBossAS-5.0.0.GA Using run.sh of AS 4.2.3, bash reports an error message. To fix this, introduce jboss_init_osx.sh I am ready to provide the script. Btw, beside that I have not identified any issues on OSX. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

6
17
0 / 0

[JBoss JIRA] Created: (JBAS-6089) Can not disable autodiscovery if System.setProperty() is used

by Wolf-Dieter Fink (JIRA)

Can not disable autodiscovery if System.setProperty() is used ------------------------------------------------------------- Key: JBAS-6089 URL: https://jira.jboss.org/jira/browse/JBAS-6089 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Naming Affects Versions: JBossAS-4.2.3.GA, JBossAS-5.0.0.CR1, JBossAS-4.2.2.GA Reporter: Wolf-Dieter Fink Assignee: Scott M Stark If a InitialContext is created via new InitialContext() and the properties are set via System.setProperty(...) the autodiscovery can not be disabled. Here the JUnitTest method: public void checkSystemPropertiesConnection() throws NamingException { System.setProperty("java.naming.factory.initial", "org.jboss.naming.NamingContextFactory"); System.setProperty("java.naming.factory.url.pkgs", "org.jboss.naming:org.jnp.interfaces"); // System.setProperty("java.naming.provider.url", "jnp://localhost:1099"); System.setProperty("jnp.disableDiscovery", "true"); InitialContext ctx = new InitialContext(); LOGGER.debug("JNDI properties: "+ctx.getEnvironment()); } ------------------------------ The Log output 16:01:28,497 DEBUG [de.wfink.ejb21.ConnectionTest] JNDI properties: {jnp.parsedName=, java.naming.provider.url=padwfink1:1099, java.naming.factory.initial=org.jboss.naming.NamingContextFactory, jnp.disableDiscovery=false, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces:org.jboss.naming:org.jnp.interfaces} 16:01:29,481 DEBUG [org.jnp.interfaces.NamingContext] Failed to connect to padwfink1:1099 ---------------------------- If a lookup is started with this InitialContext autodiscovery is started. If all is set in a HashTable and InitialContext(hashTable) is call it works -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

5
10
0 / 0

[JBoss JIRA] Created: (JBBUILD-483) jta.jar from the repo does not have a manifest.mf file

by Jay Balunas (JIRA)

jta.jar from the repo does not have a manifest.mf file ------------------------------------------------------ Key: JBBUILD-483 URL: https://jira.jboss.org/jira/browse/JBBUILD-483 Project: JBoss Build System Issue Type: Bug Components: JBossBuild, Maven Reporter: Jay Balunas Assignee: Pete Muir Priority: Critical jta.jar from the repository does not have a manifest.mf file -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

4
8
0 / 0

[JBoss JIRA] Created: (JBAS-5581) Setting jgroups.bind_address or bind.address in run.conf will be ignored if -b used

by Galder Zamarreno (JIRA)

Setting jgroups.bind_address or bind.address in run.conf will be ignored if -b used ----------------------------------------------------------------------------------- Key: JBAS-5581 URL: http://jira.jboss.com/jira/browse/JBAS-5581 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.Beta4, JBossAS-4.2.2.GA Reporter: Galder Zamarreno Assigned To: Galder Zamarreno * Why it it useless specifying -Dbind.address=192.168.0.1 inside run.conf? Why does it work only specifying it on command line? For example: If you set -Dbind.address=127.0.0.1 in run.conf and starting AS with: ./bin/run.sh -b 10.33.144.245 The value assigned to -Dbind.address will be ignored. When you pass -Dbind.address in the command line, JBoss sets both this system property and -Djgroups.bind_address to that value, which means that if you pass -b after that, it won't override the given -Dbind.address. Bottom line, if -Dbind.address set in command line before -b, it's the winner. Example: ./bin/run.sh -Dbind.address=127.0.0.1 -b 1.2.3.4 -> JGroups will bind to 127.0.0.1 If you pass -b in the command line before -Dbind.address, -b will first set -Dbind.address and -Djgroups.bind_address, but then, when -Dbind.address is process, it will override the values of them two with what was passed in -Dbind.address ./bin/run.sh -b 1.2.3.4 -Dbind.address=127.0.0.1 -> JGroups will bind to 127.0.0.1 Now, This does not happen when the -Dbind.address is set in run.conf instead of command line. There's a bug here. When AS processes -b, it checks whether -Dbind.address has been set, which it has, so leaves it as it is. Now, when it checks -Djgroups.bind_address, it sees that it hasn't been set, but *does not do a double check in case -Dbind.address has been set*, so it ends up setting -Djgroups.bind_address to the value of -b, that way ignoring the value you passed to -Dbind.address. Example: run.conf with -Dbind.address=127.0.0.1 ./bin/run.sh -b 1.2.3.4 -> JGroups will bind to 1.2.3.4 What's the fix? Add the double check in -b processing so that if -Dbind.address was set by the user, AS does not take the value of -b and assign to -Djgroups.bind_addr -- 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

15 years, 9 months

2
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2008