January 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPORTAL-2281) Perf issue when many user dashboard

by Thomas Heute (JIRA)

Perf issue when many user dashboard ----------------------------------- Key: JBPORTAL-2281 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2281 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Heute On 'configure dashboard' when many users have a dashboard performance can drop considerably -- 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

16 years, 6 months

2
7
0 / 0

[JBoss JIRA] Created: (JBREFLECT-91) Support multiple callbacks in ClassPoolRepository

by Kabir Khan (JIRA)

Support multiple callbacks in ClassPoolRepository ------------------------------------------------- Key: JBREFLECT-91 URL: https://jira.jboss.org/jira/browse/JBREFLECT-91 Project: JBoss Reflection Issue Type: Feature Request Components: Class Pool Affects Versions: JBossReflection.2.2.0-Alpha1 Reporter: Kabir Khan Assignee: Kabir Khan Fix For: JBossReflection.2.2.0-Beta Small API change -- 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

16 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBID-217) STSSecurityHandler: Improve exception/fault handling.

by Daniel Bevenius (JIRA)

STSSecurityHandler: Improve exception/fault handling. ----------------------------------------------------- Key: JBID-217 URL: https://jira.jboss.org/jira/browse/JBID-217 Project: JBoss Identity Issue Type: Task Components: Identity-Federation Reporter: Daniel Bevenius Assignee: Daniel Bevenius Priority: Minor Improve the exception handling in this class. Currently only a WebServiceException is thrown from the handleMessage method. Use the appropriate fault codes that are defined in WS-Security for handling execptions in this handler: UnsupportedSecurityToken InvalidSecurity InvalidSecurityToken FailedAuthentication FailedCheck SecurityTokenUnavailable -- 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

16 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-7604) HDScanner start() ignores config property scanEnabled

by Brian Stansberry (JIRA)

HDScanner start() ignores config property scanEnabled ----------------------------------------------------- Key: JBAS-7604 URL: https://jira.jboss.org/jira/browse/JBAS-7604 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: ProfileService Affects Versions: JBossAS-6.0.0.M1, JBossAS-5.1.0.GA Reporter: Brian Stansberry Assignee: Scott M Stark The setter for the scanEnabled property does not cache the value, it only uses it to cancel an already-started scheduled task. If the setter is called during bean configuration, there is no scheduled task, the setter essentially becomes a no-op, and when start() is called the task is scheduled. Effect is the only way to disable HDScanner via configuration is to remove the deployment; you can't leave it deployed but configure whether it is enabled (e.g. with a system property). -- 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

16 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-2401) Maven 2 Integration and Annotations integration

by Boretti Mathieu (JIRA)

Maven 2 Integration and Annotations integration ----------------------------------------------- Key: JBRULES-2401 URL: https://jira.jboss.org/jira/browse/JBRULES-2401 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: All Affects Versions: 5.0.1.FINAL Environment: N/A Reporter: Boretti Mathieu Assignee: Mark Proctor Hello, I wrote some libraries and maven 2 plugin related to Drools integration and I think it may be interesting to integrate these stuff in the drools 5 core. Currently, it is a separate open-source project (http://www.javaforge.com/wiki/73765). Here is the features that can be interested to be added to the drools core: 1. Maven 2 plugin to compile rules and/or validate rules 2. Several annotations to : a) defines interfaces that use rules. b) defines that some field of a classes must be "auto-computed" by rules (instrumentation at compile time) c) defines that some method uses pre-condition based on rules. (Note that my implementation is currently based on the "old API" from Drools 4. I think these features can be interesting for Drools users. Thanks, Mathieu Boretti -- 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

16 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBREM-1177) Assure version compatibility with earlier versions of Remoting

by Ron Sigal (JIRA)

Assure version compatibility with earlier versions of Remoting -------------------------------------------------------------- Key: JBREM-1177 URL: https://jira.jboss.org/jira/browse/JBREM-1177 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.5.2.SP1 (Flounder) -- 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

16 years, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (JBREFLECT-90) Improve concurrency of the delegating classpools and domains

by Kabir Khan (JIRA)

Improve concurrency of the delegating classpools and domains ------------------------------------------------------------ Key: JBREFLECT-90 URL: https://jira.jboss.org/jira/browse/JBREFLECT-90 Project: JBoss Reflection Issue Type: Feature Request Components: Class Pool Reporter: Kabir Khan Assignee: Kabir Khan Fix For: JBossReflection.2.2.0-Beta -- 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

16 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2400) RuntimeException deploying drools-guvnor.war on GlassFish v3

by Matthew Sowders (JIRA)

RuntimeException deploying drools-guvnor.war on GlassFish v3 ------------------------------------------------------------ Key: JBRULES-2400 URL: https://jira.jboss.org/jira/browse/JBRULES-2400 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-guvnor Affects Versions: 5.0.1.FINAL Environment: Windows XP SP3, GlassFish v3 Reporter: Matthew Sowders Assignee: Mark Proctor Deploying drools-guvnor.war on GlassFish v3 produces the following exception: Logger:javax.enterprise.system.core.org.glassfish.internal.data Message ID:Exception while invoking class org.glassfish.ejb.startup.EjbDeployer load method java.lang.RuntimeException Complete Message:Unable to load EJB module. DeploymentContext does not contain any EJB Check archive to ensure correct packaging for C:\glassfishv3\glassfish\domains\domain1\applications\drools-guvnor at org.glassfish.ejb.startup.EjbDeployer.load(EjbDeployer.java:133) at org.glassfish.ejb.startup.EjbDeployer.load(EjbDeployer.java:63) at org.glassfish.internal.data.ModuleInfo.load(ModuleInfo.java:175) at org.glassfish.internal.data.ApplicationInfo.load(ApplicationInfo.java:216) at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:338) at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:183) at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:272) at com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:305) at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:320) at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1176) at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$900(CommandRunnerImpl.java:83) at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1235) at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1224) at org.glassfish.admingui.common.util.LocalDeploymentFacility$LocalDFCommandRunner.run(LocalDeploymentFacility.java:138) at org.glassfish.deployment.client.AbstractDeploymentFacility.deploy(AbstractDeploymentFacility.java:350) at org.glassfish.admingui.common.util.DeployUtil.invokeDeploymentFacility(DeployUtil.java:89) at org.glassfish.admingui.common.util.DeployUtil.deploy(DeployUtil.java:66) at org.glassfish.admingui.common.handlers.DeploymentHandler.deploy(DeploymentHandler.java:186) 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 com.sun.jsftemplating.layout.descriptors.handler.Handler.invoke(Handler.java:442) at com.sun.jsftemplating.layout.descriptors.LayoutElementBase.dispatchHandlers(LayoutElementBase.java:420) at com.sun.jsftemplating.layout.descriptors.LayoutElementBase.dispatchHandlers(LayoutElementBase.java:394) at com.sun.jsftemplating.layout.event.CommandActionListener.invokeCommandHandlers(CommandActionListener.java:150) at com.sun.jsftemplating.layout.event.CommandActionListener.processAction(CommandActionListener.java:98) at javax.faces.event.ActionEvent.processListener(ActionEvent.java:88) at javax.faces.component.UIComponentBase.broadcast(UIComponentBase.java:772) at javax.faces.component.UICommand.broadcast(UICommand.java:300) at com.sun.webui.jsf.component.WebuiCommand.broadcast(WebuiCommand.java:160) at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:775) at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:1267) at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:82) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:312) at org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1523) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:343) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:215) at com.sun.webui.jsf.util.UploadFilter.doFilter(UploadFilter.java:229) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:256) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:215) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:277) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:188) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:641) at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:97) at com.sun.enterprise.web.PESessionLockingStandardPipeline.invoke(PESessionLockingStandardPipeline.java:85) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:185) at org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:332) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:233) at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:239) at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:791) at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:693) at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:954) at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:170) at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:135) at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:102) at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:88) at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:76) at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:53) at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:57) at com.sun.grizzly.ContextTask.run(ContextTask.java:69) at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:330) at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:309) at java.lang.Thread.run(Thread.java:619) -- 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

16 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-7608) Add hibernate-validator-legacy

by Stan Silvert (JIRA)

Add hibernate-validator-legacy ------------------------------ Key: JBAS-7608 URL: https://jira.jboss.org/jira/browse/JBAS-7608 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Hibernate service Affects Versions: JBossAS-6.0.0.M1 Reporter: Stan Silvert Assignee: Stan Silvert Fix For: JBossAS-6.0.0.M2 -- 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

16 years, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (JBDEPLOY-232) War's metadata location is used too broadly

by Ales Justin (JIRA)

War's metadata location is used too broadly ------------------------------------------- Key: JBDEPLOY-232 URL: https://jira.jboss.org/jira/browse/JBDEPLOY-232 Project: JBoss Deployers Issue Type: Task Affects Versions: JBDEPLOY-2.0.8.SP1 Reporter: Ales Justin Assignee: Ales Justin Fix For: JBDEPLOY-2.0.9.GA, JBDEPLOY-2.1.0.Alpha1 When adding .war libs metadata locations as deployment's metadata locations, we can stumble upon unexpected behavior; see forum for more details. We need to limit the usage of alternative metadata locations. e.g. diff between default and alternative -- JEE EJB might also pick up from alternative -- 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

16 years, 6 months

1
1
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 January 2010