Deploying Ears and Wars through ProfileService| JBoss.org Content Archive (Read Only)

1 2 Previous Next 24 Replies Latest reply on Dec 11, 2008 7:33 PM by alesj Go to original post

15. Re: Deploying Ears and Wars through ProfileService

starksm64 Jun 11, 2008 8:33 PM (in response to bytor99999)

Its there:
https://svn.jboss.org/repos/jbossas/trunk/system/src/main/org/jboss/deployers/spi/management/KnownDeploymentTypes.java

part of the 74397 revision.
Actions
16. Re: Deploying Ears and Wars through ProfileService

bytor99999 Jun 12, 2008 10:37 AM (in response to bytor99999)

Hmm, interesting, I must have my IntelliJ classpath messed up. :D I do see the file there. Just not showing up in IJ, but KnownComponentTypes is, so I guess it is pointing to a jar instead of the src I have locally.

Thanks

Mark
Actions
17. Re: Deploying Ears and Wars through ProfileService

bytor99999 Jun 12, 2008 1:29 PM (in response to bytor99999)

Yeah, my IJ is pointing to jboss-as-system-5.0.0-snapshot.jar

Mark
Actions
18. Re: Deploying Ears and Wars through ProfileService

bytor99999 Jun 12, 2008 2:21 PM (in response to bytor99999)

In the test classes, can we have a test in there that checks getting a list of deployments using the KnownDeploymentTypes enum?

thanks

Mark
Actions
19. Re: Deploying Ears and Wars through ProfileService

starksm64 Jun 13, 2008 11:36 AM (in response to bytor99999)
Yes, testMCBeansDeploymentType, testSarDeploymentType, testWarDeploymentType:

public void testWarDeploymentType() throws Exception { ManagementView mgtView = getManagementView(); Set<String> names = mgtView.getDeploymentNamesForType(KnownDeploymentTypes.JavaEEWebApplication.getType());

The KnownDeploymentTypes value is only used to obtain the string form of the type as the ManagementView api uses a string type since its really an arbitrary notion that we don't want to restrict with an enum. The KnownDeploymentTypes is just a convenience for the well known deployment types.

The DeployUnitTestCase checks for the deployment types it deploys, but it just uses the string type directly.
Actions
20. Re: Deploying Ears and Wars through ProfileService

bytor99999 Jun 13, 2008 12:09 PM (in response to bytor99999)

Perfect
Actions
21. Re: Deploying Ears and Wars through ProfileService

bytor99999 Jun 16, 2008 4:11 PM (in response to bytor99999)

So with that, then we can just use the String to get the actual ManagedDeployment object?

Thanks

Mark
Actions
22. Re: Deploying Ears and Wars through ProfileService

starksm64 Jun 16, 2008 4:18 PM (in response to bytor99999)

You either need to get the deployment names or the set of ManagedDeployments for the deployment type.
Actions
23. Re: Deploying Ears and Wars through ProfileService

rob.stryker Dec 11, 2008 7:25 PM (in response to bytor99999)

Is there any way for any of these methods to be executed by a different VM? Specifically, from eclipse / JBDS tooling.

Currently we launch eclipse as its own process and then designate a far-away folder as an additional deploy location that should be scanned (in addition to the standard server/configName/deploy). This way the user can deploy the same app with minor changes to identical server configs without one deployment conflicting with the other or polluting the shared deploy folder.

The APIs mentioned seem pretty handy. Are any exposed for execution via JMX, or am I going to have to find some other solution entirely?
Actions
24. Re: Deploying Ears and Wars through ProfileService

alesj Dec 11, 2008 7:33 PM (in response to bytor99999)

"rob.stryker@jboss.com" wrote:
Is there any way for any of these methods to be executed by a different VM?

The tests act like clients --> different JVM.

"rob.stryker@jboss.com" wrote:

Are any exposed for execution via JMX, or am I going to have to find some other solution entirely?

No need for JMX.
PS hides the service impl - pojo, mbean, ...
You just need Managed annotations, but this is already there if the service if pojo or mbean.
Actions

1 2 Previous Next

Go to original post