March 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-5082) Add a transaction status interface for the connection manager and implement it in TxConnectionManager

by Adrian Brock (JIRA)

Add a transaction status interface for the connection manager and implement it in TxConnectionManager ------------------------------------------------------------------------------------------------------ Key: JBAS-5082 URL: http://jira.jboss.com/jira/browse/JBAS-5082 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JCA service Affects Versions: JBossAS-4.2.2.GA Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossAS-5.0.0.Beta3, JBossAS-4.2.3.GA The ConnectionManager needs a transaction status interface such that resource adapters can check the active status of the transaction assoication. This should be similar to the TransactionTimeoutConfiguration where only the TxConnectionManager implements it. If the transaction is not active then an exception should be thrown. The resource adapters (jdbc and jms) need to add a check for transation active to their checkState methods). -- 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

16 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (JBRULES-1495) Properties keywords should not be case sensitive

by Michael Neale (JIRA)

Properties keywords should not be case sensitive ------------------------------------------------ Key: JBRULES-1495 URL: http://jira.jboss.com/jira/browse/JBRULES-1495 Project: JBoss Drools Issue Type: Task Security Level: Public (Everyone can see) Components: Decision tables Affects Versions: 4.0.4 Reporter: Michael Neale Assigned To: Michael Neale Fix For: 5.0.0-M1 Small one - no need to patch 4.0.x. Is now non case sensitive. This was a good once, it confused Mark P at 4.30 in the morning no end, made him question his sanity. Thats a job well done ;) -- 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

16 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-479) Wizard for autopopulating a decision table

by Michael Neale (JIRA)

Wizard for autopopulating a decision table ------------------------------------------ Key: JBRULES-479 URL: http://jira.jboss.com/jira/browse/JBRULES-479 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Decision tables Reporter: Michael Neale Assigned To: Mark Proctor Priority: Minor This could be done quite easily by a contributor. Have a wizard (in the IDE) which takes information regarding the facts to be used, fields, actions (and the number of each) and generates a decision table based on that info capture (ie populates it). -- 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

16 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBVFS-17) NestedJarFromStream serialization contract is incorrect

by Scott M Stark (JIRA)

NestedJarFromStream serialization contract is incorrect ------------------------------------------------------- Key: JBVFS-17 URL: http://jira.jboss.com/jira/browse/JBVFS-17 Project: JBoss VFS Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Scott M Stark Assigned To: Scott M Stark The serialization of the NestedJarFromStream is incorrect. Its using default serialization of these fields: private transient ZipInputStream zis; private URL jarURL; private URL entryURL; private long lastModified; private long size; private AtomicBoolean inited = new AtomicBoolean(false); The problem is that the inited flag should not be serialized as this implies its parents fields: private transient List<VirtualFileHandler> entries; private transient Map<String, VirtualFileHandler> entryMap; have been initialized. They will not be after deserialization of NestedJarFromStream as it lazily does initialization. -- 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

16 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (SECURITY-124) SecurityContextAssociation should use InheritableThreadLocal

by Anil Saldhana (JIRA)

SecurityContextAssociation should use InheritableThreadLocal ------------------------------------------------------------ Key: SECURITY-124 URL: http://jira.jboss.com/jira/browse/SECURITY-124 Project: JBoss Security and Identity Management Issue Type: Bug Security Level: Public (Everyone can see) Components: Security SPI Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.2-BETA5 Currently using ThreadLocal. Use InheritableThreadLocal. -- 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

16 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (SECURITY-123) Create Federated Identity Representation Interfaces

by Anil Saldhana (JIRA)

Create Federated Identity Representation Interfaces --------------------------------------------------- Key: SECURITY-123 URL: http://jira.jboss.com/jira/browse/SECURITY-123 Project: JBoss Security and Identity Management Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Security SPI Affects Versions: 2.0.2-BETA4 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.2-BETA5 -- 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

16 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1897) Event payload marshalling

by Julien Viet (JIRA)

Event payload marshalling ------------------------- Key: JBPORTAL-1897 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1897 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal Portlet Affects Versions: Portlet-2.0, Portlet-2.1 Reporter: Julien Viet Assigned To: Julien Viet Fix For: Portlet-2.0 -- 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

16 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-251) ClassAnnotationTestCase is failing with AOP configuration

by Ales Justin (JIRA)

ClassAnnotationTestCase is failing with AOP configuration --------------------------------------------------------- Key: JBMICROCONT-251 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-251 Project: JBoss MicroContainer Issue Type: Bug Components: MetaData Affects Versions: JBossMC-2.0.0.Beta10 Reporter: Ales Justin Assigned To: Ales Justin Fix For: JBossMC-2.0.0.CR1 ClassAnnotationTestCase expects non-null MetaData to be present in order to test it for annotations. With the aop-mc-int present, the AOPConstructorJoinpoint is used, which masks the MetaData, hence making in unaccessible in the TestClassAnnotation's constructor. But the tests expects the peeked MetaData to be non-null, resulting in failure. -- 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

16 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-5272) EAR containing a MDB(listening to a topic) fails to deploy because of the order of deployment

by jaikiran pai (JIRA)

EAR containing a MDB(listening to a topic) fails to deploy because of the order of deployment --------------------------------------------------------------------------------------------- Key: JBAS-5272 URL: http://jira.jboss.com/jira/browse/JBAS-5272 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.Beta4 Environment: JBoss-5.0 Beta 4, Sun Java 1.5, Windows 2003 Server Reporter: jaikiran pai A simple EAR containing an MDB which listens on a topic fails to deploy. The MDB is as follows: package org.myapp.ejb.impl; import javax.ejb.ActivationConfigProperty; import javax.ejb.MessageDriven; import javax.jms.Message; import javax.jms.MessageListener; import org.apache.log4j.Logger; @MessageDriven(activationConfig = { @ActivationConfigProperty(propertyName="destinationType", propertyValue="javax.jms.Topic"), @ActivationConfigProperty(propertyName="destination", propertyValue="topic/testTopic") }) public class MyMDB implements MessageListener { private static Logger logger = Logger.getLogger(MyMDB.class); /** * Default constructor * */ public MyMDB() { } /** * */ public void onMessage(Message arg0) { System.out.println("onMessage of MyMDB called"); logger.info("onMessage of MyMDB called"); } } The sample EAR that i used for testing was named EJB3Persistence.ear and was placed in the deploy folder of JBoss. The topic was configured in destinations-service.xml which is inside deploy\messaging folder. Started JBoss. While deploying the application, JBoss threw this exception: 2008-03-04 11:29:51,416 INFO [org.jboss.ejb3.EJBContainer] STARTED EJB: org.myapp.ejb.impl.MyMDB ejbName: MyMDB 2008-03-04 11:29:51,416 DEBUG [org.jboss.ejb3.mdb.MessagingContainer] Initializing 2008-03-04 11:29:51,463 DEBUG [org.jboss.ejb.txtimer.EJBTimerServiceImpl] createTimerService: org.jboss.ejb.txtimer.TimerServiceImpl@1099c38 2008-03-04 11:29:51,510 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to Start: name=jboss.j2ee:ear=EJB3Persistence.ear,jar=myapp_ejb3.jar,name=MyMDB,service=EJB3 state=Create org.jboss.deployment.DeploymentException: Unable to create activation spec ra=jboss.jca:service=RARDeployment,name='jms-ra.rar' messaging-type=javax.jms.MessageListener properties={destination=org.jboss.metadata.ejb.spec.ActivationConfigPropertyMetaData@aac6440e{destination}, destinationType=org.jboss.metadata.ejb.spec.ActivationConfigPropertyMetaData@96f19068{destinationType}} at org.jboss.deployment.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:52) at org.jboss.ejb3.mdb.inflow.JBossMessageEndpointFactory.createActivationSpec(JBossMessageEndpointFactory.java:299) at org.jboss.ejb3.mdb.inflow.JBossMessageEndpointFactory.start(JBossMessageEndpointFactory.java:192) at org.jboss.ejb3.mdb.MessagingContainer.startProxies(MessagingContainer.java:187) at org.jboss.ejb3.mdb.MessagingContainer.start(MessagingContainer.java:151) at org.jboss.ejb3.mdb.MDB.start(MDB.java:123) 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.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:56) at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:110) at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66) at org.jboss.kernel.plugins.dependency.KernelControllerContextAction$JoinpointDispatchWrapper.execute(KernelControllerContextAction.java:214) at org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(ExecutionWrapper.java:45) at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchExecutionWrapper(KernelControllerContextAction.java:108) at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:69) at org.jboss.kernel.plugins.dependency.LifecycleAction.installActionInternal(LifecycleAction.java:221) at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.installAction(KernelControllerContextAction.java:135) at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.installAction(KernelControllerContextAction.java:46) at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62) at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71) at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411) at org.jboss.system.ServiceController.doChange(ServiceController.java:659) at org.jboss.system.ServiceController.start(ServiceController.java:431) at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:150) at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:108) at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46) at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:65) 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.doInstallParentFirst(DeployersImpl.java:853) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:874) at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:794) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411) at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:498) at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:506) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:246) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:131) at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:408) at org.jboss.Main.boot(Main.java:208) at org.jboss.Main$1.run(Main.java:534) at java.lang.Thread.run(Thread.java:595) Caused by: javax.management.InstanceNotFoundException: jboss.jca:service=RARDeployment,name='jms-ra.rar' is not registered. at org.jboss.mx.server.registry.BasicMBeanRegistry.get(BasicMBeanRegistry.java:529) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:662) at org.jboss.ejb3.JmxClientKernelAbstraction.invoke(JmxClientKernelAbstraction.java:44) at org.jboss.ejb3.mdb.inflow.JBossMessageEndpointFactory.createActivationSpec(JBossMessageEndpointFactory.java:294) ... 54 more This appears to be because the topic defined in the deploy\messaging folder is created at a later stage during deployment: 2008-03-04 11:30:08,479 DEBUG [org.jboss.jms.server.destination.TopicService] Starting jboss.messaging.destination:service=Topic,name=testTopic 2008-03-04 11:30:08,494 DEBUG [org.jboss.jms.server.DestinationJNDIMapper] topic testTopic registered 2008-03-04 11:30:08,494 DEBUG [org.jboss.jms.server.DestinationJNDIMapper] topic bound in JNDI as /topic/testTopic As a workaround, i renamed the EAR file to ZEJB3Persistence.ear (note that the filename now starts with Z), so that this file is picked up for deployment *after* deploying the topic in the messaging folder. I then restarted JBoss with came up fine without any errors and deployed the EAR and MDB. Please see the forum reference for more details. -- 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

16 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-5132) Jboss 4.2.2 JSF RI did not work for clicking links w/ target=_blank

by Dave Chen (JIRA)

Jboss 4.2.2 JSF RI did not work for clicking links w/ target=_blank ------------------------------------------------------------------- Key: JBAS-5132 URL: http://jira.jboss.com/jira/browse/JBAS-5132 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JSF Affects Versions: JBossAS-4.2.2.GA Environment: Linux Federa Core 6, MySQL Reporter: Dave Chen Assigned To: Stan Silvert Priority: Critical Everything works fine for myfaces on Jboss 4.0.5GA. After I moved to JBoss 4.2.2 with faces RI. I got issues when clicking a command link with target=_blank. First time clicking the link is ok, but clicking the link again did not work, did not go to the Invoke Application phase to execute action. http://www.nabble.com/Jboss-4.2.2-RI-did-not-work-for-clicking-links-w--t... -- 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

16 years, 2 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2008