December 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-8699) Upgrade Bean Validation to 4.1.0.Final

by Shelly McGowan (JIRA)

Upgrade Bean Validation to 4.1.0.Final -------------------------------------- Key: JBAS-8699 URL: https://jira.jboss.org/browse/JBAS-8699 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Shelly McGowan Assignee: Shelly McGowan -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-8703) Upgrade JAXR to 2.0.2

by Richard Opalka (JIRA)

Upgrade JAXR to 2.0.2 --------------------- Key: JBAS-8703 URL: https://jira.jboss.org/browse/JBAS-8703 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JAXR service Reporter: Richard Opalka Assignee: Richard Opalka Fix For: 6.0.0.Final -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-6588) Move to HASingletonProfileActivator

by Brian Stansberry (JIRA)

Move to HASingletonProfileActivator ----------------------------------- Key: JBAS-6588 URL: https://jira.jboss.org/jira/browse/JBAS-6588 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: JBossAS-6.0.0.Alpha1 When the profile service moves to XML-based configuration, switch deploy-hasingleton to a subprofile that gets created at bootstrap but not activated. Differs from 5.1 impl which creates the subprofile when HASingletonProfileManager is deployed. -- 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, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-6355) ServiceBindingManager docs

by Brian Stansberry (JIRA)

ServiceBindingManager docs -------------------------- Key: JBAS-6355 URL: https://jira.jboss.org/jira/browse/JBAS-6355 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Docs/Administration and Configuration Guide Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: JBossAS-5.0.1.CR1 -- 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, 7 months

3
10
0 / 0

[JBoss JIRA] Created: (JBAS-7709) Review beans that bind in JNDI to add a dependency on Naming

by Brian Stansberry (JIRA)

Review beans that bind in JNDI to add a dependency on Naming ------------------------------------------------------------ Key: JBAS-7709 URL: https://jira.jboss.org/jira/browse/JBAS-7709 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: JBossAS-6.0.0.M3 There are a number of services/beans that bind things in JNDI that just assume a naming server is available. This assumption is only valid because historically the local Naming server has been deployed in a "deployment phase" prior to when those services are deployed. A proper dependency should be declared to make server startup more robust. The MC name of the bean to depend on is "LocalNamingBean" but IMHO we should give it a different name or an alias. Perhaps just "LocalJNDI". "JNDI" sounds tempting but some I think the name should make clear that no remote capability exists. -- 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, 7 months

3
5
0 / 0

[JBoss JIRA] Created: (JBAS-8700) JMX DeploymentScanner listDeployedURLs only returns the deployment roots

by Emanuel Muckenhuber (JIRA)

JMX DeploymentScanner listDeployedURLs only returns the deployment roots ------------------------------------------------------------------------ Key: JBAS-8700 URL: https://jira.jboss.org/browse/JBAS-8700 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMX Affects Versions: 6.0.0.M1 Reporter: Emanuel Muckenhuber Assignee: Emanuel Muckenhuber Priority: Minor Fix For: 6.0.0.Final -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBCOMMON-116) Bundle OSGI

by luca stancapiano (JIRA)

Bundle OSGI ----------- Key: JBCOMMON-116 URL: https://jira.jboss.org/browse/JBCOMMON-116 Project: JBoss Common Issue Type: Feature Request Security Level: Public (Everyone can see) Components: common-core (2.x) Affects Versions: 2.2.18.GA Environment: felix Reporter: luca stancapiano could be useful a conversion of the common core packge in OSGI so we can install it inside a OSGI Repository. I tested it with Felix. To do it we need to modify the packaging tag from 'jar' to 'bundle' in the pom.xml and add this plugin configuration:  <plugin> <groupId>org.apache.felix</groupId> <artifactId>maven-bundle-plugin</artifactId> <version>1.4.3</version> <extensions>true</extensions> <configuration> <instructions> <Bundle-DocURL>http://community.jboss.org/wiki/JBossCommonProject</Bundle-DocURL> <Export-Package> ${project.groupId}.*;version=${project.version};-split-package:=error </Export-Package> <Import-Package> ${project.groupId}.*;!org.apache.*,* </Import-Package> </instructions> </configuration> </plugin> -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-5554) Cross-cluster dependencies

by Brian Stansberry (JIRA)

Cross-cluster dependencies -------------------------- Key: JBAS-5554 URL: http://jira.jboss.com/jira/browse/JBAS-5554 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Clustering, Deployers Reporter: Brian Stansberry Assigned To: Brian Stansberry Service B on node 2 depends on Service A on node 1. Per Scott, "Dependencies on components that are marked as @Clustered needs a cluster aware dependency implementation. Custom dependencies are supported by the mc, but the component deployers generating the component metadata have to generate the correct dependency implementation." This also ties in with the coordinated deployment issue in JBAS-5553, as we wouldn't want Service B deployment to fail on node 2 just because it happened to deploy before Service A on node 1. -- 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, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-5550) Clustered deployments using the ProfileService

by Brian Stansberry (JIRA)

Clustered deployments using the ProfileService ---------------------------------------------- Key: JBAS-5550 URL: http://jira.jboss.com/jira/browse/JBAS-5550 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Clustering, ProfileService Reporter: Brian Stansberry Assigned To: Brian Stansberry Container task for work on bringing clustered deployments to the full ProfileService. Some of the subtasks will be for AS 5.0.0; others for later. See the forum reference as well as an earlier discussion at http://www.jboss.com/index.html?module=bb&op=viewtopic&t=63437 -- 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, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-5553) Coordinated cluster-wide deployment into the runtime

by Brian Stansberry (JIRA)

Coordinated cluster-wide deployment into the runtime ---------------------------------------------------- Key: JBAS-5553 URL: http://jira.jboss.com/jira/browse/JBAS-5553 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Clustering, ProfileService Reporter: Brian Stansberry Assigned To: Brian Stansberry Once deployment repository content is synchronized across a cluster, need to add the ability to do staged deployments of updated content into the runtime. -- 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, 7 months

1
2
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 December 2010