March 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBEE-128) EJB 3.2 API (JSR-345) for EE7

by Shelly McGowan (JIRA)

[ https://issues.jboss.org/browse/JBEE-128?page=com.atlassian.jira.plugin.s... ] Shelly McGowan commented on JBEE-128: ------------------------------------- 1.0.0.Alpha2 was released which includes pull request #5 and #6 for use in additional testing: https://repository.jboss.org/nexus/content/groups/public/org/jboss/spec/j... > EJB 3.2 API (JSR-345) for EE7 > ------------------------------ > > Key: JBEE-128 > URL: https://issues.jboss.org/browse/JBEE-128 > Project: JBoss JavaEE Spec APIs > Issue Type: Sub-task > Components: jboss-ejb-api, jboss-javaee-specs > Reporter: jaikiran pai > Assignee: jaikiran pai > Fix For: JavaEE 7 Spec APIs 1.0.0.Beta1 > > > Update the Java EE EJB API to incorporate the EJB 3.2 updates. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (AS7-6673) Remove no-arg OperationContext.completeStep() variant and OperationContext.Stage.IMMEDIATE

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6673?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-6673: ---------------------------------- Summary: Remove no-arg OperationContext.completeStep() variant and OperationContext.Stage.IMMEDIATE (was: Remove no-arg OperationContext.completeStep() variant) Description: Remove OperationContext.completeStep() and Stage.IMMEDIATE that we deprecated in 7.2. (was: Remove OperationContext.completeStep() in favor of OperationContext.completeStep(RollbackHandler)) > Remove no-arg OperationContext.completeStep() variant and OperationContext.Stage.IMMEDIATE > ------------------------------------------------------------------------------------------ > > Key: AS7-6673 > URL: https://issues.jboss.org/browse/AS7-6673 > Project: Application Server 7 > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 8.0.0.Alpha1 > > > Remove OperationContext.completeStep() and Stage.IMMEDIATE that we deprecated in 7.2. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (AS7-6661) Ensure OperationFailedException constructors don't allow null failure description

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6661?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-6661: ---------------------------------- Assignee: Brian Stansberry > Ensure OperationFailedException constructors don't allow null failure description > --------------------------------------------------------------------------------- > > Key: AS7-6661 > URL: https://issues.jboss.org/browse/AS7-6661 > Project: Application Server 7 > Issue Type: Enhancement > Components: Domain Management > Environment: OFE.getFailureDescription() should not return null. > OperationClientException javadoc should clearly state this. > An OFE(Throwable cause) constructor would be good; just call this(cause.getMessage(), cause). > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 8.0.0.Alpha1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (AS7-6673) Remove no-arg OperationContext.completeStep() variant

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-6673: ------------------------------------- Summary: Remove no-arg OperationContext.completeStep() variant Key: AS7-6673 URL: https://issues.jboss.org/browse/AS7-6673 Project: Application Server 7 Issue Type: Task Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.2.0.Alpha1 Deprecate OperationContext.completeStep() in favor of OperationContext.completeStep(RollbackHandler) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (AS7-6673) Remove no-arg OperationContext.completeStep() variant

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6673?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-6673: ---------------------------------- Description: Remove OperationContext.completeStep() in favor of OperationContext.completeStep(RollbackHandler) (was: Deprecate OperationContext.completeStep() in favor of OperationContext.completeStep(RollbackHandler)) > Remove no-arg OperationContext.completeStep() variant > ----------------------------------------------------- > > Key: AS7-6673 > URL: https://issues.jboss.org/browse/AS7-6673 > Project: Application Server 7 > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 7.2.0.Alpha1 > > > Remove OperationContext.completeStep() in favor of OperationContext.completeStep(RollbackHandler) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (AS7-6673) Remove no-arg OperationContext.completeStep() variant

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6673?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-6673: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.2.0.Alpha1) > Remove no-arg OperationContext.completeStep() variant > ----------------------------------------------------- > > Key: AS7-6673 > URL: https://issues.jboss.org/browse/AS7-6673 > Project: Application Server 7 > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 8.0.0.Alpha1 > > > Remove OperationContext.completeStep() in favor of OperationContext.completeStep(RollbackHandler) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBEE-130) Interceptors 1.2

by Shelly McGowan (JIRA)

[ https://issues.jboss.org/browse/JBEE-130?page=com.atlassian.jira.plugin.s... ] Shelly McGowan commented on JBEE-130: ------------------------------------- Interceptors v1.2 APIs have been released: https://repository.jboss.org/nexus/content/groups/public/org/jboss/spec/j... > Interceptors 1.2 > ---------------- > > Key: JBEE-130 > URL: https://issues.jboss.org/browse/JBEE-130 > Project: JBoss JavaEE Spec APIs > Issue Type: Sub-task > Components: jboss-interceptors-api > Reporter: Jozef Hartinger > Assignee: Jozef Hartinger > Fix For: JavaEE 7 Spec APIs 1.0.0.Beta1 > > > http://java.net/projects/interceptors-spec/sources/interceptors-spec-repo... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBEE-131) Update jboss-jaxrs-api to JAX-RS 2.0 APIs

by Shelly McGowan (JIRA)

Shelly McGowan created JBEE-131: ----------------------------------- Summary: Update jboss-jaxrs-api to JAX-RS 2.0 APIs Key: JBEE-131 URL: https://issues.jboss.org/browse/JBEE-131 Project: JBoss JavaEE Spec APIs Issue Type: Sub-task Reporter: Shelly McGowan Assignee: Shelly McGowan -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBEE-127) Java EE Connector Architecture (JSR-322)

by Shelly McGowan (JIRA)

[ https://issues.jboss.org/browse/JBEE-127?page=com.atlassian.jira.plugin.s... ] Shelly McGowan resolved JBEE-127. --------------------------------- Resolution: Done Release done. If additional changes are needed, they will be tracked under a separate JIRA. > Java EE Connector Architecture (JSR-322) > ---------------------------------------- > > Key: JBEE-127 > URL: https://issues.jboss.org/browse/JBEE-127 > Project: JBoss JavaEE Spec APIs > Issue Type: Sub-task > Components: jboss-connector-api > Reporter: Shelly McGowan > Assignee: Shelly McGowan > Fix For: JavaEE 7 Spec APIs 1.0.0.Beta1 > > > Project repo exists: > https://github.com/jboss/jboss-connector-api_spec > Need updates to for v1.7. > {code} > <groupId>org.jboss.spec.javax.resource</groupId> > <artifactId>jboss-connector-api_1.7_spec</artifactId> > <version>1.0.0-SNAPSHOT</version> > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (AS7-6663) Usability issue: 'Reload' operation in CLI returns information that another reload is required

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6663?page=com.atlassian.jira.plugin.s... ] Brian Stansberry reassigned AS7-6663: ------------------------------------- Assignee: Brian Stansberry > Usability issue: 'Reload' operation in CLI returns information that another reload is required > ---------------------------------------------------------------------------------------------- > > Key: AS7-6663 > URL: https://issues.jboss.org/browse/AS7-6663 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Affects Versions: 7.1.2.Final (EAP), 7.1.3.Final (EAP), 7.2.0.Alpha1 > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Minor > Fix For: 8.0.0.Alpha1 > > > Jan Martiska reported: > Assume a server reload is required.. then you do this: > {code} > [standalone@localhost:9999 /] :reload > { > "outcome" => "success", > "response-headers" => {"process-state" => "reload-required"} > } > {code} > I think it is quite confusing that "reload-required" is returned from 'reload' operation. (if you do more operations, it will not appear again, only once). Is it possible to fix it? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
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 March 2013