[JBoss JIRA] (JBJCA-953) Add a WARN for missing <recovery> element
by Jesper Pedersen (JIRA)
Jesper Pedersen created JBJCA-953:
-------------------------------------
Summary: Add a WARN for missing <recovery> element
Key: JBJCA-953
URL: https://issues.jboss.org/browse/JBJCA-953
Project: IronJacamar
Issue Type: Task
Components: Deployer
Affects Versions: 1.1.0.Beta3, 1.0.14.Final
Reporter: Jesper Pedersen
Assignee: Jesper Pedersen
Fix For: 1.0.15.Final, 1.1.0.Beta4
Resource adapters that uses no security or application security needs to have an explicit <recovery> element in order for XA recovery to be enabled
--
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
[JBoss JIRA] (AS7-3694) Allow management client to associate metadata with DeploymentUnit
by SBS JIRA Integration (JIRA)
[ https://issues.jboss.org/browse/AS7-3694?page=com.atlassian.jira.plugin.s... ]
SBS JIRA Integration updated AS7-3694:
--------------------------------------
Forum Reference: https://community.jboss.org/message/782610#782610
> Allow management client to associate metadata with DeploymentUnit
> -----------------------------------------------------------------
>
> Key: AS7-3694
> URL: https://issues.jboss.org/browse/AS7-3694
> Project: Application Server 7
> Issue Type: Feature Request
> Components: OSGi, Server
> Reporter: Thomas Diesler
> Assignee: Thomas Diesler
> Priority: Critical
> Fix For: 7.2.0.CR1
>
>
> Currently there is no way to pass some metadata through the deployment API such that they could show up with the DU.
> As a client I'd like to say autostart=false and in my DUP I'd like to pick that up and not start a deployment (i.e. a bundle) automatically
> Generally it should be possible for the client to set some properties for the deployment in a generic way such that they get associated with the DeploymentUnit
> For an OSGi deployment it would be necessary to be able to define that start behaviour and the start level.
--
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
[JBoss JIRA] (AS7-6234) WAB deployment showing as successful, but not responding
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/AS7-6234?page=com.atlassian.jira.plugin.s... ]
Thomas Diesler closed AS7-6234.
-------------------------------
Assignee: Thomas Diesler (was: Jean-Frederic Clere)
Fix Version/s: (was: 7.2.0.CR1)
Resolution: Rejected
Thanks. Rejecting - seems to be a spring issue
> WAB deployment showing as successful, but not responding
> --------------------------------------------------------
>
> Key: AS7-6234
> URL: https://issues.jboss.org/browse/AS7-6234
> Project: Application Server 7
> Issue Type: Bug
> Components: OSGi
> Affects Versions: 7.2.0.Alpha1
> Environment: Windows 7
> Reporter: jarkko rantavuori
> Assignee: Thomas Diesler
> Attachments: jboss-7.2.0-server-output-deployment-showing-as-successful.txt, server.springapp.log, spring-app-1.0.0-BUILD-SNAPSHOT-looks-to-start-normally-but-doesnt.war, spring-app-1.0.0-BUILD-SNAPSHOT-no-manifest-works.war, spring-app-source-codes.zip
>
>
> Simple Spring WAB file, that I think should work, doesn't seem to. Deployment goes seemingly without issues - no errors are reported - but servlet does not respond to requests. Both OSGi panel and deployment management panel in admin console show the deployment as successful.
> Attached server output and .war file, that should respond to /spring-app request.
--
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