May 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBLOGGING-43) Provide the ability to pull jboss-logging into a project's package space via maven

by David Lloyd (JIRA)

Provide the ability to pull jboss-logging into a project's package space via maven ---------------------------------------------------------------------------------- Key: JBLOGGING-43 URL: https://jira.jboss.org/jira/browse/JBLOGGING-43 Project: JBoss Logging Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: David Lloyd Assignee: David Lloyd Fix For: 3.0.0.Beta3-jboss-logging Via shade plugin perhaps, in order to avoid requiring an explicit dep for users on jboss-logging. -- 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

14 years, 8 months

3
8
0 / 0

[JBoss JIRA] Created: (AS7-744) Provide a replacement for Felix OSGI management web interface

by Heiko Braun (JIRA)

Provide a replacement for Felix OSGI management web interface ------------------------------------------------------------- Key: AS7-744 URL: https://issues.jboss.org/browse/AS7-744 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Yes, OSGi has its own management console (which we simply took from Felix as you say). It would be better to integrate with our management console, the cross JavaEE/OSGi concepts in AS7 are not covered in the Felix console and having OSGi as an 'island' in AS7 isn't ultimately the way forward IMHO. But yes, I agree that we can postpone this a little bit and then take the time to do it properly. Cheers, David -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

4
8
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1604) Do not create new WebServiceContext when already provided

by Alessio Soldano (JIRA)

Do not create new WebServiceContext when already provided ---------------------------------------------------------- Key: EJBTHREE-1604 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1604 Project: EJB 3.0 Issue Type: Feature Request Reporter: Alessio Soldano Assignee: Alessio Soldano The StatelessContainer's method invokeEndpoint(Method method, Object[] args, InvocationContextCallback invCtxCallback) currently get the WebServiceContext instance using the right jbossws-spi factory. This is an issue with the JBossWS-Metro stack as we should use the WebServiceContext it already provides. This should be passed in as an attachment in the InvocationContextCallback. Something like this should work: ... WebServiceContext providedCtx = invCtxCallback.getAttachment(WebServiceContext.class); if (providedCtx != null) { //use the provided one through a delegate jaxwsContext = new WebServiceContextDelegate(providedCtx); } else { //do as we used to do jaxwsContext = contextFactory.newWebServiceContext(InvocationType.JAXWS_EJB3, invCtxCallback.get(javax.xml.ws.handler.MessageContext.class)); } ... This requires jbossws-spi 1.0.7 to be released and specified in the dependencies because of the WebServiceContextDelegate. -- 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

14 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-8605) Add support for legacy MC configuration

by Ales Justin (JIRA)

Add support for legacy MC configuration --------------------------------------- Key: JBAS-8605 URL: https://jira.jboss.org/browse/JBAS-8605 Project: JBoss Application Server Issue Type: Feature Request Components: MicroContainer bus Affects Versions: 7.0.0.Alpha1 Reporter: Ales Justin Assignee: Ales Justin Fix For: 7.0.0.Alpha2 Add support for legacy MC (-jboss-beans.xml) configuration files. -- 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

14 years, 8 months

5
7
0 / 0

[JBoss JIRA] Created: (JBEE-21) Add jboss-persistence-api_2.0_spec

by Shelly McGowan (JIRA)

Add jboss-persistence-api_2.0_spec ---------------------------------- Key: JBEE-21 URL: https://jira.jboss.org/jira/browse/JBEE-21 Project: JBoss JavaEE APIs Issue Type: Sub-task Reporter: Shelly McGowan Assignee: Shelly McGowan Fix For: 6.0.0.Alpha1 -- 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

14 years, 8 months

4
11
0 / 0

[JBoss JIRA] Created: (AS7-921) Booting AS7 on a system without any network connection throws up an error from ModClusterService

by jaikiran pai (JIRA)

Booting AS7 on a system without any network connection throws up an error from ModClusterService ------------------------------------------------------------------------------------------------ Key: AS7-921 URL: https://issues.jboss.org/browse/AS7-921 Project: Application Server 7 Issue Type: Bug Environment: AS7 upstream (dated May 30 2011) Reporter: jaikiran pai Assignee: Jean-Frederic Clere Fix For: 7.0.0.CR1 Starting AS7 (upstream) on a system which doesn't have any network connection throws up the following error during startup: {code} 15:38:22,766 ERROR [org.jboss.modcluster.ModClusterService] (MSC service thread 1-1) Error starting advertise listener: java.net.SocketException: No such device at java.net.PlainDatagramSocketImpl.join(Native Method) [:1.6.0_21] at java.net.PlainDatagramSocketImpl.join(PlainDatagramSocketImpl.java:172) [:1.6.0_21] at java.net.MulticastSocket.joinGroup(MulticastSocket.java:277) [:1.6.0_21] at org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl.init(AdvertiseListenerImpl.java:181) at org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl.start(AdvertiseListenerImpl.java:193) at org.jboss.modcluster.ModClusterService.init(ModClusterService.java:174) at org.jboss.modcluster.catalina.CatalinaEventHandlerAdapter.init(CatalinaEventHandlerAdapter.java:335) at org.jboss.modcluster.catalina.CatalinaEventHandlerAdapter.start(CatalinaEventHandlerAdapter.java:115) at org.jboss.as.modcluster.ModClusterService.start(ModClusterService.java:188) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1675) [jboss-msc-1.0.0.Beta8.jar:1.0.0.Beta8] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_21] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_21] at java.lang.Thread.run(Thread.java:619) [:1.6.0_21] {code} Note that the server startup continues and starts up fine even with this error. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

5
7
0 / 0

[JBoss JIRA] Created: (JBEE-19) Update jboss-ejb-api to EJB 3.1

by Carlo de Wolf (JIRA)

Update jboss-ejb-api to EJB 3.1 ------------------------------- Key: JBEE-19 URL: https://jira.jboss.org/jira/browse/JBEE-19 Project: JBoss JavaEE APIs Issue Type: Task Components: EJB API Reporter: Carlo de Wolf Assignee: Carlo de Wolf Priority: Critical -- 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

14 years, 8 months

3
5
0 / 0

[JBoss JIRA] Created: (JBAS-8911) Expose ServerEnvironment as a management resource

by Brian Stansberry (JIRA)

Expose ServerEnvironment as a management resource ------------------------------------------------- Key: JBAS-8911 URL: https://issues.jboss.org/browse/JBAS-8911 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.Beta1 Expose the information in the ServerEnvironment (which is the data acquired from the command line rather than the domain config) as a read-only management resource. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

4
5
0 / 0

[JBoss JIRA] Created: (JBAS-8136) Consistent mechanism for masking passwords across the configuration

by Brian Stansberry (JIRA)

Consistent mechanism for masking passwords across the configuration ------------------------------------------------------------------- Key: JBAS-8136 URL: https://jira.jboss.org/browse/JBAS-8136 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: Unscheduled This JIRA is based on feedback we received after the Andiamo BOF at JBoss World 2010: >> The means to mask passwords is different for >> the newer jboss-beans.xml files from the older mbean >> configurations. Would much rather have a one and done solution >> instead of managing two different solutions. With the AS 7 unified domain configuration this should fall out naturally, but we need to guard that no subsystems introduce non-standard ways of doing this. -- 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

14 years, 8 months

7
10
0 / 0

[JBoss JIRA] Created: (JBAS-8975) Annotation scanner for @Remote

by David Lloyd (JIRA)

Annotation scanner for @Remote ------------------------------ Key: JBAS-8975 URL: https://issues.jboss.org/browse/JBAS-8975 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: 7.0.0.Beta3 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

3
4
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 May 2011