September 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-2113) TimerService is not available at java:comp/TimerService

by jaikiran pai (JIRA)

TimerService is not available at java:comp/TimerService ------------------------------------------------------- Key: EJBTHREE-2113 URL: https://jira.jboss.org/browse/EJBTHREE-2113 Project: EJB 3.0 Issue Type: Bug Components: core Affects Versions: bom-eap5-0.1.2, EJB3_1 1.0.7, Plugin 1.0.19 Reporter: jaikiran pai Assignee: jaikiran pai Fix For: EJB3_1 1.0.8 Although we allow TimerService to be injected into beans through @Resource, we don't really pull it from the java:comp/TimerService. Infact, java:comp/TimerService is not really bound for any of the EJB types. The injection works because of a special org.jboss.injection.TimerServicePropertyInjector which bypasses the ENC during injection. TimerServicePropertyInjector will henceforth be deprecated and TimerService injection should henceforth happen through java:comp/TimerService. -- 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: (EJBTHREE-2129) Integrate async with Singleton container

by jaikiran pai (JIRA)

Integrate async with Singleton container ---------------------------------------- Key: EJBTHREE-2129 URL: https://jira.jboss.org/browse/EJBTHREE-2129 Project: EJB 3.0 Issue Type: Task Components: singleton Reporter: jaikiran pai Assignee: jaikiran pai Fix For: EJB3_1 1.0.8 EJBTHREE-1721 introduces async into core containers. This affects singleton containers too. The necessary changes will be tracked in this JIRA. -- 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: (EJBTHREE-2169) @Startup @Singleton beans should be started after the auto-timers have been initialized

by jaikiran pai (JIRA)

@Startup @Singleton beans should be started after the auto-timers have been initialized --------------------------------------------------------------------------------------- Key: EJBTHREE-2169 URL: https://jira.jboss.org/browse/EJBTHREE-2169 Project: EJB 3.0 Issue Type: Bug Components: singleton Reporter: jaikiran pai Assignee: jaikiran pai When a @Startup @Singleton is created (i.e. the @PostConstruct is invoked), the auto-timers should already have been created and functional. Currently, the instance gets created even before the auto-timers are processed. -- 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: (JGRP-996) AUTH: handle multiple physical addresses in FixedMembershipToken

by Bela Ban (JIRA)

AUTH: handle multiple physical addresses in FixedMembershipToken ---------------------------------------------------------------- Key: JGRP-996 URL: https://jira.jboss.org/jira/browse/JGRP-996 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.9 -- 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

1
5
0 / 0

[JBoss JIRA] Created: (JBAS-8274) Over-zealous deprecation of *JBoss* artifacts breaks *JBoss* projects

by Andrew Dinn (JIRA)

Over-zealous deprecation of *JBoss* artifacts breaks *JBoss* projects --------------------------------------------------------------------- Key: JBAS-8274 URL: https://jira.jboss.org/browse/JBAS-8274 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Build System Affects Versions: 6.0.0.M4 Reporter: Andrew Dinn Assignee: Paul Gier apache-log4j:log4j.jar appears to have been moved to the JBoss deprecated repository (also the versions located in maven central under groupid apache-log4j appear to have been excluded form the JBoss public repo). This has broken the JBossTS hudson test builds. Can we please have our ball back? -- 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

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-5599) Eliminate build time configuration directories and replace with tool for generating configuration through the profile service API

by Andrig Miller (JIRA)

Eliminate build time configuration directories and replace with tool for generating configuration through the profile service API --------------------------------------------------------------------------------------------------------------------------------- Key: JBAS-5599 URL: http://jira.jboss.com/jira/browse/JBAS-5599 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Build System, Getting Started Guide, Installation Guide, Installer, Management services, ProfileService, Server Configuration Guide, Test Suite Reporter: Andrig Miller Assigned To: Paul Gier Fix For: No Release With the addition of the profile service, it seems silly to generate various configurations, like "all", "default" and "minimal" through the build. Instead we should have a tool that generates the configuration through the profile service, with the understanding of the dependencies of the various features. The tool could still have the concepts of "all", "default" and "minimal" embedded in it to make the transition easier, but most times to do the testing that we need to do we customize the configuration. We also add an additional configuration in productizing the EAP, and this would simplify that process as well. This tool would have to be usable at the command-line, in JBoss Tools, and from the installer. -- 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, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (JGRP-1234) S3_PING: don't use access key and secret key

by Bela Ban (JIRA)

S3_PING: don't use access key and secret key --------------------------------------------- Key: JGRP-1234 URL: https://jira.jboss.org/browse/JGRP-1234 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.11 Useful when accessing public buckets -- 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
3
0 / 0

[JBoss JIRA] Created: (JBAS-8403) <service-ref> element specified in jboss-web.xml is ignored

by Richard Opalka (JIRA)

<service-ref> element specified in jboss-web.xml is ignored ------------------------------------------------------------ Key: JBAS-8403 URL: https://jira.jboss.org/browse/JBAS-8403 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Reporter: Richard Opalka Assignee: Emanuel Muckenhuber Priority: Blocker Fix For: 6.0.0.CR1 I have Servlet 3 spec. compliant servlet that injects Web Service references. I provide jboss-web.xml to override some runtime data (wsdl-location namely). However this jboss-web.xml provided file seems ignored. I was debugging this problem and I found that org.jboss.web.deployers.WarAnnotationMetaDataDeployer creates JBossWebMetaData that are later used for Web Service References injection. What I'm missing is some "merge" code that will override WarAnnotationMetaDataDeployer provided JBossWebMetaData with JBossWebMetaData specified in jboss-web.xml -- 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
17
0 / 0

[JBoss JIRA] Created: (JBWEB-178) Error in the Jboss Web FAQ for Tomcat release number based ?

by Yannick LE NY (JIRA)

Error in the Jboss Web FAQ for Tomcat release number based ? ------------------------------------------------------------ Key: JBWEB-178 URL: https://jira.jboss.org/browse/JBWEB-178 Project: JBoss Web Issue Type: Task Security Level: Public (Everyone can see) Environment: none Reporter: Yannick LE NY Assignee: Remy Maucherat In the Jboss Web FAQ at http://www.jboss.org/jbossweb/faq.html, there is : "JBoss Web is based on Tomcat 6.0.13 and we have been porting the needed fixes for Tomcat to JBoss Web." but at http://docs.jboss.org/jbossweb/latest/changelog.html I saw that the latest patched Tomcat release used by Jboss is Tomcat 6.0.15. Then, is JBoss Web based on Tomcat 6.0.13 or on Tomcat 6.0.15 ? It is very important for me to know this information because some software editors support only Tomcat and with a minimal release number for their applications. -- 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

2
4
0 / 0

[JBoss JIRA] Created: (JBMETA-297) lookup-name not found as child of ejb-local-ref

by Carlo de Wolf (JIRA)

lookup-name not found as child of ejb-local-ref ----------------------------------------------- Key: JBMETA-297 URL: https://jira.jboss.org/browse/JBMETA-297 Project: JBoss Metadata Issue Type: Bug Security Level: Public (Everyone can see) Components: common Reporter: Carlo de Wolf Assignee: Carlo de Wolf Priority: Critical Fix For: jboss-metadata-common-2.0.0-alpha-17 -- 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