April 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Assigned: (JBAS-2408) JCA1.5 EJB3 integration

by Jesper Pedersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2408?page=all ] Jesper Pedersen reassigned JBAS-2408: ------------------------------------- Assignee: Jesper Pedersen (was: Weston Price) > JCA1.5 EJB3 integration > ----------------------- > > Key: JBAS-2408 > URL: http://jira.jboss.com/jira/browse/JBAS-2408 > Project: JBoss Application Server > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: JCA service > Affects Versions: JBossAS-4.0.3 Final, JBossAS-4.0.3 SP1 > Reporter: Adrian Brock > Assigned To: Jesper Pedersen > Fix For: JBossAS-4.2.3.GA > > > Need to refactor JCA1.5 inbound messaging to work with both EJB2.1 and EJB3.0 -- 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

17 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-263) Revert common beans until Schema resolver problem is fixed

by Adrian Brock (JIRA)

Revert common beans until Schema resolver problem is fixed ---------------------------------------------------------- Key: JBMICROCONT-263 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-263 Project: JBoss MicroContainer Issue Type: Sub-task Components: Deployment Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossMC-2.0.0.Beta11 I'm going to revert the header's xsd:redefine until the JBossXB SchemaResolver StackOverflow problem is fixed. This issue will remain open until it works properly with the xsd:redefine -- 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

17 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-261) Update aop-mc-int schema to use jboss-beans-common_2_0.xsd

by Kabir Khan (JIRA)

Update aop-mc-int schema to use jboss-beans-common_2_0.xsd ---------------------------------------------------------- Key: JBMICROCONT-261 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-261 Project: JBoss MicroContainer Issue Type: Feature Request Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: JBossMC-2.0.0.CR1 -- 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

17 years, 8 months

3
4
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-375) Grouping of messages

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-375?page=all ] Tim Fox updated JBMESSAGING-375: -------------------------------- Summary: Grouping of messages (was: Grouping of messages with JMSXGroupId) Description: We should add an ability to group messages by a group id so any messages with the same group id always go to the same consumer on a queue. This would be useful when having competing consumers on a queue and you want each consumer to handle all messages with a particular value of group id. was: We should add an ability to group messages by JMSXGroupID, so any messages with the same group id always go to the same consumer on a queue. This would be useful when having competing consumers on a queue and you want each consumer to handle all messages with a particular value of JMSXGroupID > Grouping of messages > -------------------- > > Key: JBMESSAGING-375 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-375 > Project: JBoss Messaging > Issue Type: Feature Request > Reporter: Tim Fox > Assigned To: Jeff Mesnil > Fix For: 2.0.0 Beta > > Attachments: jbmessaging-375.patch, patch-JBMESSAGING-375.txt, patch-JBMESSAGING-375.txt > > Original Estimate: 1 week > Remaining Estimate: 1 week > > We should add an ability to group messages by a group id so any messages with the same group id always go to the same consumer on a queue. > This would be useful when having competing consumers on a queue and you want each consumer to handle all messages with a particular value of group id. -- 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

17 years, 8 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBMESSAGING-375) Grouping of messages with JMSXGroupId

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-375?page=comments#action_12... ] Tim Fox commented on JBMESSAGING-375: ------------------------------------- We shouldn't use JMSXGroupid for this since this is core functionality. > Grouping of messages with JMSXGroupId > ------------------------------------- > > Key: JBMESSAGING-375 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-375 > Project: JBoss Messaging > Issue Type: Feature Request > Reporter: Tim Fox > Assigned To: Jeff Mesnil > Fix For: 2.0.0 Beta > > Attachments: jbmessaging-375.patch, patch-JBMESSAGING-375.txt, patch-JBMESSAGING-375.txt > > Original Estimate: 1 week > Remaining Estimate: 1 week > > We should add an ability to group messages by JMSXGroupID, so any messages with the same group id always go to the same consumer on a queue. > This would be useful when having competing consumers on a queue and you want each consumer to handle all messages with a particular value of JMSXGroupID -- 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

17 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1730) IdentityServiceControllerImpl : unregister existing MBean service before to re register them

by Antoine Herzog (JIRA)

IdentityServiceControllerImpl : unregister existing MBean service before to re register them -------------------------------------------------------------------------------------------- Key: JBPORTAL-1730 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1730 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal Identity Affects Versions: 2.6.1 Final Reporter: Antoine Herzog Priority: Optional Fix For: 2.6.3 Final In IdentityServiceControllerImpl (service name="portal:service=Module,type=IdentityServiceController") the Identity Beans are registered as JMX MBeans. When redeploying the service, an exception is thrown, as the services are yet deployed. javax.management.InstanceAlreadyExistsException: portal:service=Module,type=User already registered. Let's put this code before to register the bean, at line 378 of IdentityServiceControllerImpl.java // Unregister the former service is if it is yet there. // This to avoid the exception when redeploying this service if (getServer().isRegistered( new ObjectName(module.getServiceName()))) { getServer().unregisterMBean( new ObjectName(module.getServiceName())); } Thanks, -- 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

17 years, 8 months

2
10
0 / 0

[JBoss JIRA] Created: (JBMETA-12) Update to jbossws-spi 1.0.2.GA

by Heiko Braun (JIRA)

Update to jbossws-spi 1.0.2.GA ------------------------------ Key: JBMETA-12 URL: http://jira.jboss.com/jira/browse/JBMETA-12 Project: JBoss Metadata Issue Type: Task Security Level: Public (Everyone can see) Reporter: Heiko Braun Assigned To: Alexey Loubyansky It's a shared dependency between EJB3 and the meta data project. -- 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

17 years, 8 months

1
6
0 / 0

[JBoss JIRA] Created: (SECURITY-175) RequestContext and ResponseContext should hold on to Document Element if parsing was used

by Anil Saldhana (JIRA)

RequestContext and ResponseContext should hold on to Document Element if parsing was used ----------------------------------------------------------------------------------------- Key: SECURITY-175 URL: http://jira.jboss.com/jira/browse/SECURITY-175 Project: JBoss Security and Identity Management Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JBossXACML Affects Versions: 2.0.2-BETA6 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.2.GA -- 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

17 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBBUILD-459) Add missing thirdparty jars to maven repository.

by Paul Gier (JIRA)

Add missing thirdparty jars to maven repository. ------------------------------------------------ Key: JBBUILD-459 URL: http://jira.jboss.com/jira/browse/JBBUILD-459 Project: JBoss Build System Issue Type: Task Components: Maven Reporter: Paul Gier Assigned To: Paul Gier Fix For: Maven Build - App Server There are several thirdparty app server dependencies that are not currently in the maven repo. These should be added. -- 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

17 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (SECURITY-173) Marshaller/Unmarshaller for the XACMLAuthzDecisionStatementType

by Anil Saldhana (JIRA)

Marshaller/Unmarshaller for the XACMLAuthzDecisionStatementType --------------------------------------------------------------- Key: SECURITY-173 URL: http://jira.jboss.com/jira/browse/SECURITY-173 Project: JBoss Security and Identity Management Issue Type: Feature Request Security Level: Public (Everyone can see) Components: saml-xacml Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.2.GA SAML payload can contain XACMLAuthzDecisionStatementType elements representing a xacml decision. -- 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

17 years, 8 months

1
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2008