September 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-2706) Replace extjs grid in decision tables and rule templates with a new grid that suppors cell merging

by Geoffrey De Smet (JIRA)

Replace extjs grid in decision tables and rule templates with a new grid that suppors cell merging -------------------------------------------------------------------------------------------------- Key: JBRULES-2706 URL: https://jira.jboss.org/browse/JBRULES-2706 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-guvnor Affects Versions: 5.1.1.FINAL Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet Priority: Critical Fix For: 5.2.0.M1 <conan> so what I'd like to do is get our dtable moved across to a new grid <conan> but also for it to be updated so that it supports cell merging <conan> the cell merging is essential for proper web based dtables <conan> cbrock was working on errai grid that supports cell merging <conan> manstis has been looking into it <conan> he submitted some patches to errai but says it's a lot of work <conan> to make it into a full component <conan> he thinks that flex grid now has cell merging, but I doubt that..... <conan> but he might be right in that it would be quicker to move the errai cell merging code into a fork of the gwt flex grid <conan> that try and move everything into errai grid that makes a grid workable <conan> a second issue is that that the rule template <conan> really should use the same grid as dtable grid <conan> including the same mechanisms for driving possible values et -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
11
0 / 0

[JBoss JIRA] Created: (JBAS-8468) Upgrade to jboss-metadata-common 2.0.0-alpha-17

by Richard Opalka (JIRA)

Upgrade to jboss-metadata-common 2.0.0-alpha-17 ----------------------------------------------- Key: JBAS-8468 URL: https://jira.jboss.org/browse/JBAS-8468 Project: JBoss Application Server Issue Type: Component Upgrade Security Level: Public (Everyone can see) Reporter: Richard Opalka Assignee: Richard Opalka Fix For: 6.0.0.CR1 This brings in the following fixes to AS trunk: * JBMETA-293 * JBMETA-297 * JBMETA-298 * JBMETA-299 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-8309) Initial OSGi integration

by Thomas Diesler (JIRA)

Initial OSGi integration ------------------------ Key: JBAS-8309 URL: https://jira.jboss.org/browse/JBAS-8309 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: OSGi integration Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.0.0.M1 Integrate the MSC based Framework -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
11
0 / 0

[JBoss JIRA] Created: (JBBUILD-652) Add option to load additional license map from a file

by Paul Gier (JIRA)

Add option to load additional license map from a file ----------------------------------------------------- Key: JBBUILD-652 URL: https://jira.jboss.org/browse/JBBUILD-652 Project: JBoss Build System Issue Type: Feature Request Components: maven-license-plugin Reporter: Paul Gier Assignee: Paul Gier Fix For: maven-license-plugin-2.0.0 Many dependency POMs do not contain license information. In these cases it would be useful to manually create a license mapping file which stores a list of dependencies and each license associated with that dependency. These dependencies could then be skipped when checking remote dependencies. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/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: (JGRP-1236) Port UFC and MFC protocols from HEAD to 2.10 branch

by Vladimir Blagojevic (JIRA)

Port UFC and MFC protocols from HEAD to 2.10 branch ---------------------------------------------------- Key: JGRP-1236 URL: https://jira.jboss.org/browse/JGRP-1236 Project: JGroups Issue Type: Task Affects Versions: 2.10 Reporter: Vladimir Blagojevic Assignee: Vladimir Blagojevic Fix For: 2.10.1 New flow control protocols MFC and UFC available on HEAD branch (2.11) should be ported to 2.10 branch and included in 2.10.1 maintenance release. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2164) Create LinkRefs in java:global namespace for EJB3.1 beans

by jaikiran pai (JIRA)

Create LinkRefs in java:global namespace for EJB3.1 beans ---------------------------------------------------------- Key: EJBTHREE-2164 URL: https://jira.jboss.org/browse/EJBTHREE-2164 Project: EJB 3.0 Issue Type: Task Reporter: jaikiran pai Assignee: jaikiran pai We currently don't bind to java:global JNDI namespace. Create a deployer which creates LinkRefs in java:global namespace to our internal jndi names. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2180) EJB3.1 spec jndi binder should only apply for EJB3.1 beans

by jaikiran pai (JIRA)

EJB3.1 spec jndi binder should only apply for EJB3.1 beans ---------------------------------------------------------- Key: EJBTHREE-2180 URL: https://jira.jboss.org/browse/EJBTHREE-2180 Project: EJB 3.0 Issue Type: Bug Reporter: jaikiran pai Assignee: jaikiran pai Currently, we even include EJB3.0 beans during EJBBinder creation. Only EJB3.1 beans should be eligible. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/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: (JBAS-6335) EjbModule is already installed

by Henrik Lindell (JIRA)

EjbModule is already installed ------------------------------ Key: JBAS-6335 URL: https://jira.jboss.org/jira/browse/JBAS-6335 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployers Affects Versions: JBossAS-5.0.0.GA Environment: Windows XP jdk1.6.0_11 Reporter: Henrik Lindell Assignee: Ales Justin Priority: Blocker When deploying 2 EARs containing each an ejb 2.x jar with the same name ("my-ejbs.jar") deployment fails with this stack trace when the second is handled by the EjbDeployer. The BasicMBeanRegistry tries to register them both with the name "jboss.j2ee:module="my-ejbs.jar",service=EjbModule" 14:33:27,796 WARN [AbstractDeploymentContext] Unable to register deployment mbean jboss.j2ee:module="my-ejbs.jar",service=EjbModule javax.management.InstanceAlreadyExistsException: jboss.deployment:id="jboss.j2ee:module="my-ejbs.jar",service=EjbModule",type=Component already registered. at org.jboss.mx.server.registry.BasicMBeanRegistry.add(BasicMBeanRegistry.java:767) at org.jboss.mx.server.registry.BasicMBeanRegistry.registerMBean(BasicMBeanRegistry.java:236) at sun.reflect.GeneratedMethodAccessor89.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:138) at org.jboss.mx.server.Invocation.invoke(Invocation.java:90) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:140) at org.jboss.mx.server.Invocation.invoke(Invocation.java:90) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) at org.jboss.mx.server.MBeanServerImpl$3.run(MBeanServerImpl.java:1431) at java.security.AccessController.doPrivileged(Native Method) at org.jboss.mx.server.MBeanServerImpl.registerMBean(MBeanServerImpl.java:1426) at org.jboss.mx.server.MBeanServerImpl.registerMBean(MBeanServerImpl.java:376) at org.jboss.deployers.structure.spi.helpers.AbstractDeploymentContext.registerMBeans(AbstractDeploymentContext.java:989) at org.jboss.deployers.structure.spi.helpers.AbstractDeploymentContext.addComponent(AbstractDeploymentContext.java:719) at org.jboss.deployers.structure.spi.helpers.AbstractDeploymentUnit.addComponent(AbstractDeploymentUnit.java:249) at org.jboss.system.deployers.ServiceDeploymentDeployer.addServiceComponent(ServiceDeploymentDeployer.java:62) at org.jboss.system.deployers.ServiceDeploymentDeployer$ServiceMetaDataVisitor.deploy(ServiceDeploymentDeployer.java:150) at org.jboss.system.deployers.ServiceDeploymentDeployer$ServiceMetaDataVisitor.deploy(ServiceDeploymentDeployer.java:141) at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployerWithInput.deploy(AbstractRealDeployerWithInput.java:125) at org.jboss.deployers.spi.deployer.helpers.AbstractComponentDeployer.deployComponents(AbstractComponentDeployer.java:102) at org.jboss.deployers.spi.deployer.helpers.AbstractComponentDeployer.internalDeploy(AbstractComponentDeployer.java:82) at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50) at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171) at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1210) at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098) 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:781) at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:545) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:304) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:205) at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:405) at org.jboss.Main.boot(Main.java:209) at org.jboss.Main$1.run(Main.java:547) at java.lang.Thread.run(Thread.java:619) 14:33:27,828 INFO [TomcatDeployment] deploy, ctxPath=/abc-6-0-4, vfsUrl=my-ear-6-0-4.ear/webApp.war 14:33:28,046 WARN [TomcatDeployment] Failed to setup clustering, clustering disabled. NoClassDefFoundError: org/jboss/cache/pojo/jmx/PojoCacheJmxWrapperMBean 14:33:28,125 INFO [EjbModule] Deploying AbcSLS 14:33:28,203 INFO [ProxyFactory] Bound EJB Home 'AbcSLS' to jndi 'xyz/abc-6-0-4/internal/ejb/session/Abc' 14:33:28,218 INFO [ProxyFactory] Unbind EJB Home 'AbcSLS' from jndi 'xyz/abc-6-0-4/internal/ejb/session/Abc' 14:33:28,218 INFO [EjbModule] Undeployed AbcSLS 14:33:28,218 INFO [TomcatDeployment] undeploy, ctxPath=/abc-6-0-4, vfsUrl=my-ear-6-0-4.ear/webApp.war 14:33:31,015 ERROR [AbstractKernelController] Error installing to Real: name=vfsfile:/C:/develop/server/jboss-5.0.0.GA.JDK6/server/standard/deploy/my-ear-6-0-4.ear/ state=PreReal mode=Manual requiredState=Real org.jboss.deployers.spi.DeploymentException: Error deploying: jboss.j2ee:service=EjbModule,module="my-ejbs.jar" at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:123) at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:45) at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62) at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50) at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171) at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1178) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1210) at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098) 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:781) at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:545) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:304) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:205) at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:405) at org.jboss.Main.boot(Main.java:209) at org.jboss.Main$1.run(Main.java:547) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.IllegalStateException: jboss.j2ee:module="my-ejbs.jar",service=EjbModule is already installed. at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:716) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:540) at org.jboss.system.ServiceController.doInstall(ServiceController.java:670) at org.jboss.system.ServiceController.install(ServiceController.java:273) at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:95) ... 24 more 14:33:31,093 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): *** CONTEXTS IN ERROR: Name -> Error vfsfile:/C:/develop/server/jboss-5.0.0.GA.JDK6/server/standard/deploy/my-ear-6-0-4.ear/ -> java.lang.IllegalStateException: jboss.j2ee:module="my-ejbs.jar",service=EjbModule is already installed. 14:33:31,109 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080 14:33:31,140 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009 14:33:31,140 INFO [ServerImpl] JBoss (Microcontainer) [5.0.0.GA (build: SVNTag=JBoss_5_0_0_GA date=200812042120)] Started in 1m:40s:531ms -- 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
10
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2163) service-ref not creating env binding

by William DeCoste (JIRA)

service-ref not creating env binding ------------------------------------ Key: EJBTHREE-2163 URL: https://jira.jboss.org/browse/EJBTHREE-2163 Project: EJB 3.0 Issue Type: Bug Components: ejb3 Affects Versions: 1.1.22 Environment: EAP 5.0.1 Reporter: William DeCoste Assignee: Carlo de Wolf service-ref/service-ref-name in ejb-jar.xml/jboss.xml is not creating an env binding. See SLSB, ejb-jar.xml, jboss.xml, and JNDIView for SLSB java:comp/env: java:comp namespace of the component jboss.j2ee:jar=webservices-test.jar,name=WebServiceRefBean,service=EJB3 : +- EJBContext (class: javax.ejb.EJBContext) +- TransactionSynchronizationRegistry[link -> java:TransactionSynchronizationRegistry] (class: javax.naming.LinkRef) +- UserTransaction (class: org.jboss.ejb3.tx.UserTransactionImpl) +- env (class: org.jnp.interfaces.NamingContext) | +- org.jboss.webservicestest.WebServiceRefBean (class: org.jnp.interfaces.NamingContext) | | +- serviceRef (class: org.jboss.ws.core.jaxws.client.ServiceReferenceable) +- ORB[link -> java:/JBossCorbaORB] (class: javax.naming.LinkRef) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/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: (JBAS-7096) SLSB with dependency on HASingletonDeployer / Barrier results in error message on second node on startup

by Richard Taylor (JIRA)

SLSB with dependency on HASingletonDeployer / Barrier results in error message on second node on startup -------------------------------------------------------------------------------------------------------- Key: JBAS-7096 URL: https://jira.jboss.org/jira/browse/JBAS-7096 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering Affects Versions: JBossAS-5.1.0.GA Environment: RHEL 4 Update 7 (and OSX 10.5.7), Sun JRE 1.6.0_12, JBoss 5.1.0 - "all" configuration Reporter: Richard Taylor Assignee: Brian Stansberry Priority: Minor Basic cluster, two JBoss 5.1.0 nodes, "all" configuration. First node starts fine. Second node starts, however at the end of starting, any SLSBs that depend on the barrier result in an error being logged at startup (on the second node). Example: DEPLOYMENTS MISSING DEPENDENCIES: Deployment "jboss.j2ee:ear=app-ear.ear,jar=app-ejb.jar,name=BoardPollerMDB,service=EJB3" is missing the following dependencies: Dependency "<UNKNOWN jboss.j2ee:ear=app-ear.ear,jar=app-ejb.jar,name=BoardPollerMDB,service=EJB3>" (should be in state "Described", bu t is actually in state "** UNRESOLVED Demands 'jboss.ha:service=HASingletonDeployer,type=Barrier' **") DEPLOYMENTS IN ERROR: Deployment "<UNKNOWN jboss.j2ee:ear=app-ear.ear,jar=app-ejb.jar,name=BoardPollerMDB,service=EJB3>" is in error due to the following reas on(s): ** UNRESOLVED Demands 'jboss.ha:service=HASingletonDeployer,type=Barrier' ** The SLSBs on node 2 do properly start in a failover scenario when node 1 goes down. So functionally things seem OK. However the error message is a little concerning and it leaves us wondering if there is more to the problem. -- 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
7
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 September 2010