Filter javaee.api
-----------------
Key: JBAS-8984
URL: https://issues.jboss.org/browse/JBAS-8984
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Reporter: David Lloyd
Fix For: 7.0.0.CR1
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Allow simplified high-level stack configuration
-----------------------------------------------
Key: JBAS-9172
URL: https://issues.jboss.org/browse/JBAS-9172
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: Clustering
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Fix For: 7.0.0.CR1
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Simplify definition of inherited jgroups stacks, e.g. udp-sync, udp-async, etc.
-------------------------------------------------------------------------------
Key: JBAS-9171
URL: https://issues.jboss.org/browse/JBAS-9171
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: Clustering
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Fix For: 7.0.0.CR1
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
James Perkins created AS7-3397:
----------------------------------
Summary: Removing a logger with an attached file handler fails with a missing dependency
Key: AS7-3397
URL: https://issues.jboss.org/browse/AS7-3397
Project: Application Server 7
Issue Type: Bug
Components: Logging
Reporter: James Perkins
Assignee: James Perkins
Priority: Critical
Fix For: 7.1.0.Final
When attempting to remove a logger that has a file handler attached the following error is reported:
JBAS014775: New missing/unsatisfied dependencies:
service jboss.logging.logger."org.jboss.as.logging" (missing) dependents: [service jboss.logging.logger-handler."org.jboss.as.logging".fh]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Paul Ferraro created AS7-3341:
---------------------------------
Summary: Upgrade Infinispan to 5.1.0.CR4
Key: AS7-3341
URL: https://issues.jboss.org/browse/AS7-3341
Project: Application Server 7
Issue Type: Component Upgrade
Components: Clustering
Affects Versions: 7.1.0.CR1b
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Priority: Critical
Fix For: 7.1.0.Final
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Convert modules to use JBoss Logging and message bundles
--------------------------------------------------------
Key: AS7-809
URL: https://issues.jboss.org/browse/AS7-809
Project: Application Server 7
Issue Type: Task
Reporter: James Perkins
Assignee: James Perkins
Fix For: 7.0.0.CR1
Use JBoss Logging 3 to create annotated interfaces for messages and logging. Also include the tooling to generate the concrete classes at compile time for the interfaces.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.jboss.org/browse/AS7-333?page=com.atlassian.jira.plugin.sy... ]
Brian Stansberry updated AS7-333:
---------------------------------
Component/s: Domain Management
> Context is lost if a service fails to start for a 'random' reason
> -----------------------------------------------------------------
>
> Key: AS7-333
> URL: https://issues.jboss.org/browse/AS7-333
> Project: Application Server 7
> Issue Type: Feature Request
> Components: Domain Management
> Reporter: Carlo de Wolf
> Assignee: David Lloyd
> Priority: Minor
> Fix For: 7.1.0.Final
>
>
> The error message only contains "Failed to start service" it would be nice if the optional causing message is also appended.
> {noformat}
> 13:58:53,058 INFO [org.jboss.as.server] (MSC service thread 1-9) Service status report
> Services which failed to start:
> service jboss.deployment.unit."welcome.war": org.jboss.msc.service.StartException in service jboss.deployment.unit."welcome.war": Failed to start service
> {noformat}
> https://github.com/jbossas/jboss-msc/blob/1.0.0.Beta8/src/main/java/org/j...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Ondrej Zizka created AS7-3394:
---------------------------------
Summary: resteasy-jaxrs-2.3.0.GA.jar and async-http-servlet-3.0-2.3.0.GA.jar both define org.jboss.resteasy.plugins.server.servlet.* classes.
Key: AS7-3394
URL: https://issues.jboss.org/browse/AS7-3394
Project: Application Server 7
Issue Type: Quality Risk
Reporter: Ondrej Zizka
org.jboss.resteasy.plugins.server.servlet.ConfigurationBootstrap resteasy-jaxrs-2.3.0.GA.jar
org.jboss.resteasy.plugins.server.servlet.Filter30Dispatcher async-http-servlet-3.0-2.3.0.GA.jar
org.jboss.resteasy.plugins.server.servlet.FilterBootstrap resteasy-jaxrs-2.3.0.GA.jar
...
org.jboss.resteasy.plugins.server.servlet.ResteasyContextParameters resteasy-jaxrs-2.3.0.GA.jar
org.jboss.resteasy.plugins.server.servlet.Servlet3AsyncHttpRequest async-http-servlet-3.0-2.3.0.GA.jar
org.jboss.resteasy.plugins.server.servlet.Servlet3AsyncHttpRequest$1 async-http-servlet-3.0-2.3.0.GA.jar
org.jboss.resteasy.plugins.server.servlet.ServletBootstrap resteasy-jaxrs-2.3.0.GA.jar
org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher resteasy-jaxrs-2.3.0.GA.jar
See https://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-Miscellaneous/job/... .
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira