September 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-1819) JGroup channels should use AUTO_RECONNECTION option to automatically reconnect in case the channel is closed

by Yong Hao Gao (JIRA)

JGroup channels should use AUTO_RECONNECTION option to automatically reconnect in case the channel is closed ------------------------------------------------------------------------------------------------------------ Key: JBMESSAGING-1819 URL: https://jira.jboss.org/browse/JBMESSAGING-1819 Project: JBoss Messaging Issue Type: Bug Components: JMS Clustering Affects Versions: 1.4.7.GA, 1.4.0.SP3.CP10 Reporter: Yong Hao Gao Assignee: Yong Hao Gao Fix For: 1.4.0.SP3.CP11, 1.4.8.GA -- 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, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (SECURITY-528) Release PicketBox 3.0.0.CR1

by ANIL SALDHANA (JIRA)

Release PicketBox 3.0.0.CR1 --------------------------- Key: SECURITY-528 URL: https://jira.jboss.org/browse/SECURITY-528 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Release Security Level: Public (Everyone can see) Components: ACL, Identity, JBossSX, PicketBox, Security SPI Reporter: ANIL SALDHANA Assignee: ANIL SALDHANA Fix For: PicketBox_v3_0_CR1 -- 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, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (SECURITY-527) OTP Login Module

by ANIL SALDHANA (JIRA)

OTP Login Module ---------------- Key: SECURITY-527 URL: https://jira.jboss.org/browse/SECURITY-527 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: PicketBox_v3_0_CR1 Reporter: ANIL SALDHANA Assignee: ANIL SALDHANA Validate a submitted otp. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBAS-8304) Use shared library mode in JBoss AS

by Marius Bogoevici (JIRA)

[ https://jira.jboss.org/browse/JBAS-8304?page=com.atlassian.jira.plugin.sy... ] Marius Bogoevici reassigned JBAS-8304: -------------------------------------- Assignee: Marius Bogoevici (was: Pete Muir) > Use shared library mode in JBoss AS > ----------------------------------- > > Key: JBAS-8304 > URL: https://jira.jboss.org/browse/JBAS-8304 > Project: JBoss Application Server > Issue Type: Feature Request > Components: Weld/CDI > Reporter: Pete Muir > Assignee: Marius Bogoevici > Priority: Critical > Fix For: 6.0.0.CR1 > > -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-8399) Register a BeanInstantiator at java:comp/internal/instantiator/BeanInstantiator

by Marius Bogoevici (JIRA)

Register a BeanInstantiator at java:comp/internal/instantiator/BeanInstantiator ------------------------------------------------------------------------------- Key: JBAS-8399 URL: https://jira.jboss.org/browse/JBAS-8399 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: EJB3, Weld/CDI Reporter: Marius Bogoevici Assignee: Marius Bogoevici Fix For: 6.0.0.CR1 -- 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, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-8012) Complete Site and Documentation for AS6 Security

by Stan Silvert (JIRA)

Complete Site and Documentation for AS6 Security ------------------------------------------------ Key: JBAS-8012 URL: https://jira.jboss.org/jira/browse/JBAS-8012 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Stan Silvert -- 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, 10 months

4
4
0 / 0

[JBoss JIRA] Created: (JBAS-8404) Dependency cleanup for Maven 3 beta 4

by Paul Gier (JIRA)

Dependency cleanup for Maven 3 beta 4 ------------------------------------- Key: JBAS-8404 URL: https://jira.jboss.org/browse/JBAS-8404 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Build System Affects Versions: 6.0.0.M4 Reporter: Paul Gier Assignee: Paul Gier Fix For: 6.0.0.CR1 There were some minor chages (bug fixes) to Maven's dependency resolution in Maven 3.0-beta-3. This has caused some failures in the AS build which should be fixed by cleaning up some unused dependencies in the tree. -- 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, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-8398) Injection metadata validation on deploy-time is too aggressive

by Toshiya Kobayashi (JIRA)

Injection metadata validation on deploy-time is too aggressive -------------------------------------------------------------- Key: JBAS-8398 URL: https://jira.jboss.org/browse/JBAS-8398 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployers, Web (Tomcat) service Affects Versions: 6.0.0.M4, JBossAS-5.1.0.GA Reporter: Toshiya Kobayashi Assignee: Ales Justin If your war file includes Pojo whose field is annotated with @Resource, deployer throws Exception below: 2010-09-09 00:51:45,460 ERROR [org.apache.catalina.core.StandardContext] (main) Context [/simple1] startup failed due to previous errors java.lang.RuntimeException: mapped-name is required for com.example.ResourceBean/obj of deployment simple1.war at org.jboss.web.tomcat.service.injection.WebResourceHandler.loadXmlResourceEnvRefs(WebResourceHandler.java:287) at org.jboss.web.tomcat.service.injection.WebResourceHandler.loadXml(WebResourceHandler.java:325) at org.jboss.web.tomcat.service.TomcatInjectionContainer.processMetadata(TomcatInjectionContainer.java:550) at org.jboss.web.tomcat.service.WebCtxLoader.start(WebCtxLoader.java:158) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4272) at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:310) at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:142) at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:461) at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118) at org.jboss.web.deployers.WebModule.start(WebModule.java:97) 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 org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) Scanning is ok, but validation is too aggressive. In JBoss AS 4, such @Resource usage is allowed and it can be utilized by Spring etc. -- 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, 10 months

3
3
0 / 0

[JBoss JIRA] Created: (JGRP-1232) GossipRouter.stop() call to GossipRouter.clear() is ignored due to GossipRouter.running

by Scott Marlow (JIRA)

GossipRouter.stop() call to GossipRouter.clear() is ignored due to GossipRouter.running --------------------------------------------------------------------------------------- Key: JGRP-1232 URL: https://jira.jboss.org/browse/JGRP-1232 Project: JGroups Issue Type: Bug Affects Versions: 2.10 Reporter: Scott Marlow Assignee: Scott Marlow Came across this while working on Infinispan integration into AS 6. One of the AS test cases (integration branch view http://anonsvn.jboss.org/repos/jbossas/branches/infinispan-int/testsuite/...) is starting a gossip router for testing (with two members). After testing a few things, we stop the gossip router. We then test to see if the group membership (via AS cluster partition abstraction) has been updated). It is expected that each AS node will see one member in their view but they still see two (which triggers a failure). Anyway, while looking into the above, I noticed that GossipRouter.stop invokes GossipRouter.clear but only after setting GossipRouter.running = false. GossipRouter.clear will not close the client connections as a result. Perhaps we should have GossipRouter.stop + GossipRouter.clear both call an internal clear that is unguarded (e.g. let the public methods guard against GossipRouter.running being false). As a short term workaround for the above unit test failure, I changed DRMTestCase to call GossipRouter.clear() before GossipRouter.stop(). -- 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, 10 months

3
5
0 / 0

[JBoss JIRA] Created: (JBJCA-417) Use j.u.l instead of jboss logging in the generated code to avoid import jars

by Jeff Zhang (JIRA)

Use j.u.l instead of jboss logging in the generated code to avoid import jars ----------------------------------------------------------------------------- Key: JBJCA-417 URL: https://jira.jboss.org/browse/JBJCA-417 Project: IronJacamar Issue Type: Task Components: Code Generator Reporter: Jeff Zhang Assignee: Jeff Zhang Fix For: 1.0.0.Beta2 Since jboss logging defined in the depchain pom.xml is "runtime" scope, we need depends jboss logging jars in the pom.xml for compiling. Change generated code to use jdk util logger -- 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, 10 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 September 2010