-
15. Re: aggregator sample deploy in AS
kurtstam May 30, 2007 8:16 AM (in response to system.out)Yes, but you can probably deploy esb archives in an ear.
-
16. Re: aggregator sample deploy in AS
kconner May 30, 2007 8:48 AM (in response to system.out)"kurt.stam@jboss.com" wrote:
Yes, but you can probably deploy esb archives in an ear.
Almost certainly, provided it is explicitly declared.
The way I would try it would be to include a section in the jboss-app.xml file similar to the following<module> <service>xxx.esb</service> </module>
As far as I am aware the service element can contain any deployable artifact even though this may not have been it's intended function.
Of course this is untested :) -
17. Re: aggregator sample deploy in AS
system.out May 30, 2007 9:18 AM (in response to system.out)I am using maven to build the helloworld example. Maven has an elegant way to build ear, rar, jar, but not sar yet.
That is why I am interested to embed it in .ear. With maven I can also use maven:jboss plugin to deploy it remotely in AS from command line.
I am not sure if I need<service>xxx.esb</service>
as maven ear plugin includes all modules in application.xml -
18. Re: aggregator sample deploy in AS
system.out May 30, 2007 9:21 AM (in response to system.out)That would be great. Thanks Kevin!
"Kevin.Conner@jboss.com" wrote:
"system.out" wrote:
Is there any way to have a 4.2MR2-bundle, similar to 4.0-bundle ?
I am going through these now with the intent of making it easier to execute the quickstarts (especially in the jbossesb-server).
This is a slow process with all the combinations being tested but should be finished soon.
Please bear with me. -
19. Re: aggregator sample deploy in AS
tfennelly May 30, 2007 9:24 AM (in response to system.out)"system.out" wrote:
I am using maven to build the helloworld example. Maven has an elegant way to build ear, rar, jar, but not sar yet.
Have you tried this:
http://mojo.codehaus.org/jboss-packaging-maven-plugin/
I used it before and it works fine. -
20. Re: aggregator sample deploy in AS
kconner May 30, 2007 10:19 AM (in response to system.out)"system.out" wrote:
maven ear plugin includes all modules in application.xml
If it includes all the modules in application.xml then it should work.
My choice to use the jboss-app.xml would solely be because this is a jboss specific deplyment archive. -
21. Re: aggregator sample deploy in AS
system.out May 30, 2007 11:03 AM (in response to system.out)I am giving another try to build the product from svn. Here is the exception after running product/ant -v install
[java] org.jboss.esb.install: [java] [echo] Installation directory : D:\backup\jbossesb-4.2.MR2\product\build\jbossesb [java] [echo] Installing jar files [java] [copy] Copying 35 files to D:\backup\jbossesb-4.2.MR2\product\build\jbossesb\lib\ext [java] [copy] Copying 1 file to D:\backup\jbossesb-4.2.MR2\product\build\jbossesb\lib [java] [echo] Installing xml D:\backup\jbossesb-4.2.MR2\product\build\jbossesb [java] [mkdir] Created dir: D:\backup\jbossesb-4.2.MR2\product\build\jbossesb\xml [java] [copy] Copying 7 files to D:\backup\jbossesb-4.2.MR2\product\build\jbossesb\xml [java] [echo] Installed EULA [java] [copy] Copying 1 file to D:\backup\jbossesb-4.2.MR2\product\build\jbossesb [java] [echo] Installing tools D:\backup\jbossesb-4.2.MR2\product\build\jbossesb/tools [java] [mkdir] Created dir: D:\backup\jbossesb-4.2.MR2\product\build\jbossesb\tools [java] [mkdir] Created dir: D:\backup\jbossesb-4.2.MR2\product\build\jbossesb\tools\configeditor [java] [mkdir] Created dir: D:\backup\jbossesb-4.2.MR2\product\build\jbossesb\tools\configeditor\resources [java] [mkdir] Created dir: D:\backup\jbossesb-4.2.MR2\product\build\jbossesb\tools\configeditor\dist [java] [java] BUILD FAILED [java] D:\backup\jbossesb-4.2.MR2\product\build.xml:252: Warning: Could not find file D:\backup\jbossesb-4.2.MR2\product\tools\configeditor\editor\dist\jbossesb-config-editor.war to copy. [java] [java] Total time: 19 seconds BUILD FAILED
-
22. Re: aggregator sample deploy in AS
kconner May 30, 2007 11:23 AM (in response to system.out)"system.out" wrote:
Here is the exception after running product/ant -v install
Useant dist
-
23. Re: aggregator sample deploy in AS
system.out May 30, 2007 1:11 PM (in response to system.out)Thanks Kevin! It is working finally.
I had to move the build/jbossesb-server-4.2.MR1 folder to the root dir. and rename it to D:\jbossesb-server-4.2 -
24. Re: aggregator sample deploy in AS
system.out May 30, 2007 11:41 PM (in response to system.out)From SVN:Version 4.2MR2, now I am trying to deploy it in AS (it is working with standalone esb server). I ran product/install/ant install with no error (build AS and deploying all esb dependencies). Not sure why I am getting this error when deploying helloworld:
org.jboss.deployment.DeploymentException: No ClassLoaders found for: org.jboss.jms.server.destination.QueueService; - nested throwable: (java.lang.ClassNotFoundException: No ClassLoaders found for: or g.jboss.jms.server.destination.QueueService) at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:196) at org.jboss.system.ServiceController.install(ServiceController.java:226) at sun.reflect.GeneratedMethodAccessor21.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy4.install(Unknown Source)
What are the steps to add esb dependencies to AS? -
25. Re: aggregator sample deploy in AS
bernard.tison May 31, 2007 3:28 AM (in response to system.out)The error message indicates you are trying to deploy queue definitions for JBoss Messaging on a server where JBoss Messaging isn't installed.
JBoss AS uses JBossMQ as JMS provider, rather than JBoss Messaging. The bundled jbossesb-server-4.2.MR1 uses JBoss Messaging. From a client perspective this doesn't make much difference, but it does for the configuration of the JMS queues.
For JBossMQ, you should deploy the esb-quickstart-jbmq-service.xml file (in quickstarts/conf/jms). If you're using JBoss Messaging, deploy esb-quickstart-jbm-service.xml. Also make sure the .esb archive you deploy doesn't contain a JBoss Massaging configuration file. When you build the HelloWord quickstart with Ant, it will add jbm-queue-service.xml in the archive. You have to remove this before deploying the archive on JBoss AS. The esb-quickstart-jbmq-service.xml file contains the queue definitions used by the quickstarts. -
26. Re: aggregator sample deploy in AS
kconner May 31, 2007 4:29 AM (in response to system.out)One of the changes I am making is to make the choice automatic, i.e. if the build notices that the server supports JBoss Messaging then it bundles up jbm-queue-service.xml for deployment otherwise it bundles up jbmq-queue-service.xml.
I have been creating the jbmq definitions as I go and updating the esb dependencies to reflect the queues.
Once this is checked in it will no longer be necessary to deploy the aggregated queue service found within conf. -
27. Re: aggregator sample deploy in AS
system.out May 31, 2007 9:48 AM (in response to system.out)I modified the build.xml and the queue definition as you suggested:
here is the queue definition for helloworld:<?xml version="1.0" encoding="UTF-8"?> <server> <mbean code="org.jboss.mq.server.jmx.Queue" name="jboss.mq.destination:service=Queue,name=quickstart_helloworld_Request_esb"> <depends optional-attribute-name="DestinationManager"> jboss.mq:service=DestinationManager </depends> </mbean> <mbean code="org.jboss.mq.server.jmx.Queue" name="jboss.mq.destination:service=Queue,name=quickstart_helloworld_Request_gw"> <depends optional-attribute-name="DestinationManager"> jboss.mq:service=DestinationManager </depends> </mbean> </server>
and deployment.xml<jbossesb-deployment> <!-- <depends>jboss.messaging.destination:service=Queue,name=quickstart_helloworld_Request_esb</depends> <depends>jboss.messaging.destination:service=Queue,name=quickstart_helloworld_Request_gw</depends> --> <depends>jboss.mq.destination:service=Queue,name=quickstart_helloworld_Request_esb</depends> <depends>jboss.mq.destination:service=Queue,name=quickstart_helloworld_Request_gw</depends> </jbossesb-deployment>
JBOSS AS is not happy with these changes:09:06:47,452 INFO [JBoss4ESBDeployer] create esb service, Quickstart_helloworld.esb 09:06:47,483 ERROR [URLDeploymentScanner] Incomplete Deployment listing: --- MBeans waiting for other MBeans --- ObjectName: jboss.esb:deployment=Quickstart_helloworld.esb State: NOTYETINSTALLED I Depend On: jboss.mq.destination:service=Queue,name=quickstart_helloworld_Request_esb jboss.mq.destination:service=Queue,name=quickstart_helloworld_Request_gw --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM --- ObjectName: jboss.mq.destination:service=Queue,name=quickstart_helloworld_Request_esb State: NOTYETINSTALLED Depends On Me: jboss.esb:deployment=Quickstart_helloworld.esb
-
28. Re: aggregator sample deploy in AS
kconner May 31, 2007 10:14 AM (in response to system.out)"system.out" wrote:
JBOSS AS is not happy with these changes:
It looks as if the deployment dependencies have been picked up but the queues haven't deployed. -
29. Re: aggregator sample deploy in AS
system.out May 31, 2007 10:16 AM (in response to system.out)My mistake on not including the jbmq-queue-service.xml in .esb. It is working like a charm now :)
By the way, is there any advantage of using Jboss Messaging over JbossMQ? Wondering why JBoss has 2 messaging solutions !?