Allow specifying the profile name when remotely deploying to a JBoss 5.1.X-server

Details

Type: New Feature
Status: Closed
Priority: Major
Resolution: Fixed
Affects Version/s: 1.1.0
Fix Version/s: 1.1.1
Component/s: JBoss, Maven2
Labels:
None
Environment:
JBoss AS 5.1.0.GA, cargo-maven2-plugin version 1.1.0

Complexity:
Intermediate
Number of attachments :
0

Description

When running cargo:deploy with the configuration done according to http://cargo.codehaus.org/JBoss+5.1.x
(Remote deployment against a running container) this happens:

Cannot deploy deployable org.codehaus.cargo.container.jboss.deployable.JBossWAR@!26c06b

... long stack trace ...

Caused by: org.jboss.profileservice.spi.NoSuchProfileException: Profile does not
 support deployment actions: ProfileKey@199896a5[domain=default, server=myInstance, name=default]
        at org.jboss.profileservice.management.upload.DeploymentManagerImpl.chec
kProfile(DeploymentManagerImpl.java:293)
        at org.jboss.profileservice.management.upload.DeploymentManagerImpl.load
Profile(DeploymentManagerImpl.java:203)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:121)
        at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRem

Activity

Ascending order - Click to sort in descending order

Savas Ali Tokmen made changes - 23/May/11 8:36 AM

Field	Original Value	New Value
Fix Version/s		1.1.1 [ 17246 ]
Fix Version/s		1.2.0 [ 17088 ]
Description	When running cargo:deploy with the configuration done according to http://cargo.codehaus.org/JBoss+5.1.x (Remote deployment against a running container) this happens: Cannot deploy deployable org.codehaus.cargo.container.jboss.deployable.JBossWAR@!26c06b ... long stack trace ... Caused by: org.jboss.profileservice.spi.NoSuchProfileException: Profile does not support deployment actions: ProfileKey@199896a5[domain=default, server=myInstance, name=default] at org.jboss.profileservice.management.upload.DeploymentManagerImpl.chec kProfile(DeploymentManagerImpl.java:293) at org.jboss.profileservice.management.upload.DeploymentManagerImpl.load Profile(DeploymentManagerImpl.java:203) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:121) at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRem	When running cargo:deploy with the configuration done according to http://cargo.codehaus.org/JBoss+5.1.x (Remote deployment against a running container) this happens: Cannot deploy deployable org.codehaus.cargo.container.jboss.deployable.JBossWAR@!26c06b ... long stack trace ... {noformat} Caused by: org.jboss.profileservice.spi.NoSuchProfileException: Profile does not support deployment actions: ProfileKey@199896a5[domain=default, server=myInstance, name=default] at org.jboss.profileservice.management.upload.DeploymentManagerImpl.chec kProfile(DeploymentManagerImpl.java:293) at org.jboss.profileservice.management.upload.DeploymentManagerImpl.load Profile(DeploymentManagerImpl.java:203) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:121) at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRem {noformat}