[JBoss JIRA] Created: (JBESB-2760) Verify that the ESB works with the main AS trunk (code base for AS6)
1:49 p.m.
Verify that the ESB works with the main AS trunk (code base for AS6)
--------------------------------------------------------------------
Key: JBESB-2760
URL: https://jira.jboss.org/jira/browse/JBESB-2760
Project: JBoss ESB
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Rosetta
Reporter: Daniel Bevenius
Assignee: Daniel Bevenius
Fix For: 4.7
While merging https://jira.jboss.org/jira/browse/JBWS-2619 into the AS main trunk I was
not able to deploy the esb.
Even without deploying the esb code I get an error upon startup of the as server.
I also get an error with our build since conf/jboss-log4.xml does not exist in the server
created by the as trunk. This file is replaced by build.xml in
product/install/embedded-console. This might be temporary as the trunk code base is a
moving target but we should still make sure when they get closer to a release date to make
sure that we are not depending on something that is going to be removed.
I'm not sure that this is required for our 4.7 release, as this depends on the release
schedule for AS6. But I'm setting the version to 4.7 so that a decision should be made
about this.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:55 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-2760) Verify that the ESB works with the main AS trunk (code base for AS6)
[
https://jira.jboss.org/jira/browse/JBESB-2760?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-2760:
-------------------------------------
4.7 is being targeted against the 5.1.0 release and SOA 5/EAP 5. Do you know if this will
be an issue for either of these?
Verify that the ESB works with the main AS trunk (code base for AS6)
--------------------------------------------------------------------
Key: JBESB-2760
URL: https://jira.jboss.org/jira/browse/JBESB-2760
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Rosetta
Reporter: Daniel Bevenius
Assignee: Daniel Bevenius
Fix For: 4.7
While merging https://jira.jboss.org/jira/browse/JBWS-2619 into the AS main trunk I was
not able to deploy the esb.
Even without deploying the esb code I get an error upon startup of the as server.
I also get an error with our build since conf/jboss-log4.xml does not exist in the server
created by the as trunk. This file is replaced by build.xml in
product/install/embedded-console. This might be temporary as the trunk code base is a
moving target but we should still make sure when they get closer to a release date to make
sure that we are not depending on something that is going to be removed.
I'm not sure that this is required for our 4.7 release, as this depends on the
release schedule for AS6. But I'm setting the version to 4.7 so that a decision should
be made about this.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:03 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-2760) Verify that the ESB works with the main AS trunk (code base for AS6)
[
https://jira.jboss.org/jira/browse/JBESB-2760?page=com.atlassian.jira.plu...
]
Daniel Bevenius commented on JBESB-2760:
----------------------------------------
This is not an issue for AS 5.1.0. So I think we can move this to a later release then.
Verify that the ESB works with the main AS trunk (code base for AS6)
--------------------------------------------------------------------
Key: JBESB-2760
URL: https://jira.jboss.org/jira/browse/JBESB-2760
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Rosetta
Reporter: Daniel Bevenius
Assignee: Daniel Bevenius
Fix For: 4.7
While merging https://jira.jboss.org/jira/browse/JBWS-2619 into the AS main trunk I was
not able to deploy the esb.
Even without deploying the esb code I get an error upon startup of the as server.
I also get an error with our build since conf/jboss-log4.xml does not exist in the server
created by the as trunk. This file is replaced by build.xml in
product/install/embedded-console. This might be temporary as the trunk code base is a
moving target but we should still make sure when they get closer to a release date to make
sure that we are not depending on something that is going to be removed.
I'm not sure that this is required for our 4.7 release, as this depends on the
release schedule for AS6. But I'm setting the version to 4.7 so that a decision should
be made about this.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:18 a.m.
New subject: [JBoss JIRA] Work started: (JBESB-2760) Verify that the ESB works with the main AS trunk (code base for AS6)
[
https://jira.jboss.org/jira/browse/JBESB-2760?page=com.atlassian.jira.plu...
]
Work on JBESB-2760 started by Daniel Bevenius.
Verify that the ESB works with the main AS trunk (code base for AS6)
--------------------------------------------------------------------
Key: JBESB-2760
URL: https://jira.jboss.org/jira/browse/JBESB-2760
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Rosetta
Reporter: Daniel Bevenius
Assignee: Daniel Bevenius
Fix For: 4.7
While merging https://jira.jboss.org/jira/browse/JBWS-2619 into the AS main trunk I was
not able to deploy the esb.
Even without deploying the esb code I get an error upon startup of the as server.
I also get an error with our build since conf/jboss-log4.xml does not exist in the server
created by the as trunk. This file is replaced by build.xml in
product/install/embedded-console. This might be temporary as the trunk code base is a
moving target but we should still make sure when they get closer to a release date to make
sure that we are not depending on something that is going to be removed.
I'm not sure that this is required for our 4.7 release, as this depends on the
release schedule for AS6. But I'm setting the version to 4.7 so that a decision should
be made about this.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:20 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2760) Verify that the ESB works with the main AS trunk (code base for AS6)
[
https://jira.jboss.org/jira/browse/JBESB-2760?page=com.atlassian.jira.plu...
]
Daniel Bevenius commented on JBESB-2760:
----------------------------------------
After discussing this with Kev we decided to investigate this just to be on the safe
side.
Verify that the ESB works with the main AS trunk (code base for AS6)
--------------------------------------------------------------------
Key: JBESB-2760
URL: https://jira.jboss.org/jira/browse/JBESB-2760
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Rosetta
Reporter: Daniel Bevenius
Assignee: Daniel Bevenius
Fix For: 4.7
While merging https://jira.jboss.org/jira/browse/JBWS-2619 into the AS main trunk I was
not able to deploy the esb.
Even without deploying the esb code I get an error upon startup of the as server.
I also get an error with our build since conf/jboss-log4.xml does not exist in the server
created by the as trunk. This file is replaced by build.xml in
product/install/embedded-console. This might be temporary as the trunk code base is a
moving target but we should still make sure when they get closer to a release date to make
sure that we are not depending on something that is going to be removed.
I'm not sure that this is required for our 4.7 release, as this depends on the
release schedule for AS6. But I'm setting the version to 4.7 so that a decision should
be made about this.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:12 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-2760) Verify that the ESB works with the main AS trunk (code base for AS6)
[
https://jira.jboss.org/jira/browse/JBESB-2760?page=com.atlassian.jira.plu...
]
Daniel Bevenius commented on JBESB-2760:
----------------------------------------
This might not have been such an big issue after all. I noticed that my host file was
incorrect for my local machine name. This is what caused the error I saw when starting up
the AS without any ESB stuff deployed.
After deploying the ESB I get the following error upon startup:
13:13:02,967 ERROR [org.apache.catalina.startup.TldConfig] Exception processing JAR at
resource path
/opt/jboss/as/src/trunk/build/output/jboss-6.0.0.Alpha1/server/default/tmp/3j001-il4ug9-fxpyi7je-1-fxpyk6tm-af/jbpm-console.war/WEB-INF/lib/gravel-1.0.0.GA.jar
in context /jbpm-console: java.util.zip.ZipException: error in opening zip file
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(ZipFile.java:203)
at java.util.jar.JarFile.<init>(JarFile.java:132)
at java.util.jar.JarFile.<init>(JarFile.java:97)
at org.apache.catalina.startup.TldConfig.tldScanJar(TldConfig.java:461)
at org.apache.catalina.startup.TldConfig.execute(TldConfig.java:301)
at org.apache.catalina.core.StandardContext.processTlds(StandardContext.java:4540)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4308)
at
org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:310)
at
org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:142)
at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:462)
at org.jboss.web.deployers.WebModule.startModule(WebModule.java:116)
at org.jboss.web.deployers.WebModule.start(WebModule.java:95)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
Just deploying the jbpm-console.war will produce the same issue.
Also stopping the server does not work as there are jars that are missing for the shutdown
task:
<classpath>
<pathelement
location="(a){serverHome}/bin/shutdown.jar"/>
<pathelement
location="(a){serverHome}/client/jbossall-client.jar"/>
<pathelement
location="(a){serverHome}/lib/jboss-bootstrap-spi-as.jar"/>
<pathelement
location="(a){serverHome}/lib/jboss-bootstrap-spi-mc.jar"/>
<pathelement
location="(a){serverHome}/lib/jboss-bootstrap-spi.jar"/>
<pathelement
location="(a){serverHome}/lib/jboss-system-jmx.jar"/>
<pathelement
location="(a){serverHome}/lib/jboss-kernel.jar"/>
</classpath>
Adding the above will shutdown the server. Note that these jars are not in shutdown.sh and
it displays the same errors when run.
There is still an issue with the build though as this version of AS does not seem to write
any string to server.log which means that the stop-server target will always timeout
causing the build to fail.
Verify that the ESB works with the main AS trunk (code base for AS6)
--------------------------------------------------------------------
Key: JBESB-2760
URL: https://jira.jboss.org/jira/browse/JBESB-2760
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Rosetta
Reporter: Daniel Bevenius
Assignee: Daniel Bevenius
Fix For: 4.7
While merging https://jira.jboss.org/jira/browse/JBWS-2619 into the AS main trunk I was
not able to deploy the esb.
Even without deploying the esb code I get an error upon startup of the as server.
I also get an error with our build since conf/jboss-log4.xml does not exist in the server
created by the as trunk. This file is replaced by build.xml in
product/install/embedded-console. This might be temporary as the trunk code base is a
moving target but we should still make sure when they get closer to a release date to make
sure that we are not depending on something that is going to be removed.
I'm not sure that this is required for our 4.7 release, as this depends on the
release schedule for AS6. But I'm setting the version to 4.7 so that a decision should
be made about this.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:20 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-2760) Verify that the ESB works with the main AS trunk (code base for AS6)
[
https://jira.jboss.org/jira/browse/JBESB-2760?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-2760:
-------------------------------------
Given your findings I think it would be a good idea to leave this for now and wait until
the AS trunk settles down. We can revisit this once we start looking at this version of
the app server.
Verify that the ESB works with the main AS trunk (code base for AS6)
--------------------------------------------------------------------
Key: JBESB-2760
URL: https://jira.jboss.org/jira/browse/JBESB-2760
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Rosetta
Reporter: Daniel Bevenius
Assignee: Daniel Bevenius
Fix For: 4.7
While merging https://jira.jboss.org/jira/browse/JBWS-2619 into the AS main trunk I was
not able to deploy the esb.
Even without deploying the esb code I get an error upon startup of the as server.
I also get an error with our build since conf/jboss-log4.xml does not exist in the server
created by the as trunk. This file is replaced by build.xml in
product/install/embedded-console. This might be temporary as the trunk code base is a
moving target but we should still make sure when they get closer to a release date to make
sure that we are not depending on something that is going to be removed.
I'm not sure that this is required for our 4.7 release, as this depends on the
release schedule for AS6. But I'm setting the version to 4.7 so that a decision should
be made about this.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:34 p.m.
New subject: [JBoss JIRA] Work stopped: (JBESB-2760) Verify that the ESB works with the main AS trunk (code base for AS6)
[
https://jira.jboss.org/jira/browse/JBESB-2760?page=com.atlassian.jira.plu...
]
Work on JBESB-2760 stopped by Daniel Bevenius.
Verify that the ESB works with the main AS trunk (code base for AS6)
--------------------------------------------------------------------
Key: JBESB-2760
URL: https://jira.jboss.org/jira/browse/JBESB-2760
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Rosetta
Reporter: Daniel Bevenius
Assignee: Daniel Bevenius
Fix For: 4.7
While merging https://jira.jboss.org/jira/browse/JBWS-2619 into the AS main trunk I was
not able to deploy the esb.
Even without deploying the esb code I get an error upon startup of the as server.
I also get an error with our build since conf/jboss-log4.xml does not exist in the server
created by the as trunk. This file is replaced by build.xml in
product/install/embedded-console. This might be temporary as the trunk code base is a
moving target but we should still make sure when they get closer to a release date to make
sure that we are not depending on something that is going to be removed.
I'm not sure that this is required for our 4.7 release, as this depends on the
release schedule for AS6. But I'm setting the version to 4.7 so that a decision should
be made about this.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:50 p.m.
New subject: [JBoss JIRA] Updated: (JBESB-2760) Verify that the ESB works with the main AS trunk (code base for AS6)
[
https://jira.jboss.org/jira/browse/JBESB-2760?page=com.atlassian.jira.plu...
]
Daniel Bevenius updated JBESB-2760:
-----------------------------------
Fix Version/s: 4.x
(was: 4.7)
Moving this as the target is currently for AS 5.1.x
Verify that the ESB works with the main AS trunk (code base for AS6)
--------------------------------------------------------------------
Key: JBESB-2760
URL: https://jira.jboss.org/jira/browse/JBESB-2760
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Rosetta
Reporter: Daniel Bevenius
Assignee: Daniel Bevenius
Fix For: 4.x
While merging https://jira.jboss.org/jira/browse/JBWS-2619 into the AS main trunk I was
not able to deploy the esb.
Even without deploying the esb code I get an error upon startup of the as server.
I also get an error with our build since conf/jboss-log4.xml does not exist in the server
created by the as trunk. This file is replaced by build.xml in
product/install/embedded-console. This might be temporary as the trunk code base is a
moving target but we should still make sure when they get closer to a release date to make
sure that we are not depending on something that is going to be removed.
I'm not sure that this is required for our 4.7 release, as this depends on the
release schedule for AS6. But I'm setting the version to 4.7 so that a decision should
be made about this.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:43 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2760) Verify that the ESB works with the main AS trunk (code base for AS6)
[
https://jira.jboss.org/jira/browse/JBESB-2760?page=com.atlassian.jira.plu...
]
jarkko Lietolahti commented on JBESB-2760:
------------------------------------------
Btw and off-topic, but just wanting to provide the information. The jbpm-console (from esb
4.6/4.7) doesn work properly with AS 6. The problem is that deployed processed are not
visible on the processes page.
Verify that the ESB works with the main AS trunk (code base for AS6)
--------------------------------------------------------------------
Key: JBESB-2760
URL: https://jira.jboss.org/jira/browse/JBESB-2760
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Rosetta
Reporter: Daniel Bevenius
Assignee: Daniel Bevenius
Fix For: 4.x
While merging https://jira.jboss.org/jira/browse/JBWS-2619 into the AS main trunk I was
not able to deploy the esb.
Even without deploying the esb code I get an error upon startup of the as server.
I also get an error with our build since conf/jboss-log4.xml does not exist in the server
created by the as trunk. This file is replaced by build.xml in
product/install/embedded-console. This might be temporary as the trunk code base is a
moving target but we should still make sure when they get closer to a release date to make
sure that we are not depending on something that is going to be removed.
I'm not sure that this is required for our 4.7 release, as this depends on the
release schedule for AS6. But I'm setting the version to 4.7 so that a decision should
be made about this.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:41 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-2760) Verify that the ESB works with the main AS trunk (code base for AS6)
[
https://jira.jboss.org/jira/browse/JBESB-2760?page=com.atlassian.jira.plu...
]
Daniel Bevenius commented on JBESB-2760:
----------------------------------------
Jarkko: Thanks for letting us know! We will look into this when we resume this task.
Verify that the ESB works with the main AS trunk (code base for AS6)
--------------------------------------------------------------------
Key: JBESB-2760
URL: https://jira.jboss.org/jira/browse/JBESB-2760
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Rosetta
Reporter: Daniel Bevenius
Assignee: Daniel Bevenius
Fix For: 4.x
While merging https://jira.jboss.org/jira/browse/JBWS-2619 into the AS main trunk I was
not able to deploy the esb.
Even without deploying the esb code I get an error upon startup of the as server.
I also get an error with our build since conf/jboss-log4.xml does not exist in the server
created by the as trunk. This file is replaced by build.xml in
product/install/embedded-console. This might be temporary as the trunk code base is a
moving target but we should still make sure when they get closer to a release date to make
sure that we are not depending on something that is going to be removed.
I'm not sure that this is required for our 4.7 release, as this depends on the
release schedule for AS6. But I'm setting the version to 4.7 so that a decision should
be made about this.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:18 a.m.
New subject: [JBoss JIRA] Work started: (JBESB-2760) Verify that the ESB works with the main AS trunk (code base for AS6)
[
https://jira.jboss.org/browse/JBESB-2760?page=com.atlassian.jira.plugin.s...
]
Work on JBESB-2760 started by Daniel Bevenius.
Verify that the ESB works with the main AS trunk (code base for AS6)
--------------------------------------------------------------------
Key: JBESB-2760
URL: https://jira.jboss.org/browse/JBESB-2760
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Rosetta
Reporter: Daniel Bevenius
Assignee: Daniel Bevenius
Fix For: 4.x
While merging https://jira.jboss.org/jira/browse/JBWS-2619 into the AS main trunk I was
not able to deploy the esb.
Even without deploying the esb code I get an error upon startup of the as server.
I also get an error with our build since conf/jboss-log4.xml does not exist in the server
created by the as trunk. This file is replaced by build.xml in
product/install/embedded-console. This might be temporary as the trunk code base is a
moving target but we should still make sure when they get closer to a release date to make
sure that we are not depending on something that is going to be removed.
I'm not sure that this is required for our 4.7 release, as this depends on the
release schedule for AS6. But I'm setting the version to 4.7 so that a decision should
be made about this.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:20 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2760) Verify that the ESB works with the main AS trunk (code base for AS6)
[
https://jira.jboss.org/browse/JBESB-2760?page=com.atlassian.jira.plugin.s...
]
Daniel Bevenius commented on JBESB-2760:
----------------------------------------
Looking into this as I'm investigating an issue with JBossWS and need to see if the
issue exist in AS 6.x
I'm using jboss-6.0.0.20100429-M3
Verify that the ESB works with the main AS trunk (code base for AS6)
--------------------------------------------------------------------
Key: JBESB-2760
URL: https://jira.jboss.org/browse/JBESB-2760
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Rosetta
Reporter: Daniel Bevenius
Assignee: Daniel Bevenius
Fix For: 4.x
While merging https://jira.jboss.org/jira/browse/JBWS-2619 into the AS main trunk I was
not able to deploy the esb.
Even without deploying the esb code I get an error upon startup of the as server.
I also get an error with our build since conf/jboss-log4.xml does not exist in the server
created by the as trunk. This file is replaced by build.xml in
product/install/embedded-console. This might be temporary as the trunk code base is a
moving target but we should still make sure when they get closer to a release date to make
sure that we are not depending on something that is going to be removed.
I'm not sure that this is required for our 4.7 release, as this depends on the
release schedule for AS6. But I'm setting the version to 4.7 so that a decision should
be made about this.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:33 p.m.
New subject: [JBoss JIRA] Work stopped: (JBESB-2760) Verify that the ESB works with the main AS trunk (code base for AS6)
[
https://jira.jboss.org/browse/JBESB-2760?page=com.atlassian.jira.plugin.s...
]
Work on JBESB-2760 stopped by Daniel Bevenius.
Verify that the ESB works with the main AS trunk (code base for AS6)
--------------------------------------------------------------------
Key: JBESB-2760
URL: https://jira.jboss.org/browse/JBESB-2760
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Rosetta
Reporter: Daniel Bevenius
Assignee: Daniel Bevenius
Fix For: 4.x
While merging https://jira.jboss.org/jira/browse/JBWS-2619 into the AS main trunk I was
not able to deploy the esb.
Even without deploying the esb code I get an error upon startup of the as server.
I also get an error with our build since conf/jboss-log4.xml does not exist in the server
created by the as trunk. This file is replaced by build.xml in
product/install/embedded-console. This might be temporary as the trunk code base is a
moving target but we should still make sure when they get closer to a release date to make
sure that we are not depending on something that is going to be removed.
I'm not sure that this is required for our 4.7 release, as this depends on the
release schedule for AS6. But I'm setting the version to 4.7 so that a decision should
be made about this.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:33 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-2760) Verify that the ESB works with the main AS trunk (code base for AS6)
[
https://jira.jboss.org/browse/JBESB-2760?page=com.atlassian.jira.plugin.s...
]
Daniel Bevenius commented on JBESB-2760:
----------------------------------------
To get this working with AS 6.0.0.M3 I did the following:
1. Copy jbossts-commons.jar to server/default/deployers/esb.deployer/lib
2. Added a hornetq-jms.xml for jbossesb.xml:
<configuration xmlns="urn:hornetq"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:hornetq /schema/hornetq-jms.xsd">
<queue name="DeadMessageQueue">
<entry name="/queue/DeadMessageQueue"/>
</queue>
<queue name="DataCollectorQueue">
<entry name="/queue/DataCollectorQueue"/>
</queue>
<queue name="OperationsCollectorQueue">
<entry name="/queue/OperationsCollectorQueue"/>
</queue>
<queue name="OperationsResultCollectorQueue">
<entry name="/queue/OperationsResultCollectorQueue"/>
</queue>
</configuration>
3. Updated jbossesb.esb/META-INF/deployment.xml:
<depends>org.hornetq:module=JMS,name="DeadMessageQueue",type=Queue</depends>
<depends>org.hornetq:module=JMS,name="DataCollectorQueue",type=Queue</depends>
<depends>org.hornetq:module=JMS,name="OperationsCollectorQueue",type=Queue</depends>
<depends>org.hornetq:module=JMS,name="OperationsResultCollectorQueue",type=Queue</depends>
4. Added a hornetq-jms.xml for jbpm.esb:
<configuration xmlns="urn:hornetq"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:hornetq /schema/hornetq-jms.xsd">
<queue name="CallbackQueue">
<entry name="/queue/CallbackQueue"/>
</queue>
</configuration>
5. Updated jbpm.esb/deployment.xml:
<depends>org.hornetq:module=JMS,name="CallbackQueue",type=Queue</depends>
6. Renamed jbossesb.sar to jboss-esb.sar
This is because in org.jboss.reloaded.naming.deployers.AppNamingDeployer, line 65, the
appName variable is the name simple name of the deployment unit but without the suffix. So
this means that jbossesb.sar will first be used as
'jboss.naming:application=jbossesb", and then when jbossesb.esb is deployed the
same name will be deployed.
I don't mean that this is fix for this issue but at least someone trying this later
will be aware of the problem and a way to work around it for the time being.
7. Updated ivy.xml
<dependency org="org.jboss.deployers" name="jboss-deployers-vfs"
rev="2.2.0.Alpha4"/>
<dependency org="org.jboss.deployers" name="jboss-deployers-spi"
rev="2.2.0.Alpha4"/>
<dependency org="org.jboss.deployers"
name="jboss-deployers-core-spi" rev="2.2.0.Alpha4"/>
<dependency org="org.jboss.deployers" name="jboss-deployers-core"
rev="2.2.0.Alpha4"/>
<dependency org="org.jboss.deployers" name="jboss-deployers-impl"
rev="2.2.0.Alpha4"/>
<dependency org="org.jboss.deployers"
name="jboss-deployers-structure-spi" rev="2.2.0.Alpha4"/>
<dependency org="org.jboss.deployers" name="jboss-deployers-client"
rev="2.2.0.Alpha4"/>
<dependency org="org.jboss.deployers"
name="jboss-deployers-client-spi" rev="2.2.0.Alpha4"/>
<dependency org="org.jboss.deployers"
name="jboss-deployers-client-spi" rev="2.2.0.Alpha4"/>
<dependency org="org.jboss" name="jboss-vfs"
rev="3.0.0.CR5"/>
<dependency org="org.jboss.metadata" name="jboss-metadata-war"
rev="2.0.0.Alpha14"/>
<dependency org="org.jboss.metadata" name="jboss-metadata-common"
rev="2.0.0.Alpha14"/>
8. Updated install/esb-deployer-jboss-beans.xml
Changed the class of GroupingStructure to the one in VFS as it is now available in the new
version:
<bean name="GroupingStructure"
class="org.jboss.deployers.vfs.plugins.structure.dir.GroupingStructure">
9. Update package name changes in VFS
org.jboss.virtual.VirtualFile -> org.jboss.vfs.VirtualFile;
org.jboss.virtual.VirtualFileFilter -> org.jboss.vfs.VirtualFileFilter;
10. Update install/build.xml
Add a check or hornetq as the messaging provider
<target name="jms.config.check">
...
<available property="jbm.present"
file="${deploy.dir}/hornetq"/>
<target/>
11. Update samples/quickstarts/conf/base-build.xml:
Add a check for hornetq:
<target name="messaging-config" depends="jbossesb-dependencies-as4,
jbossesb-dependencies-as5">
...
<condition property="hornetq.present">
<available
file="${org.jboss.esb.server.deploy.dir}/hornetq"/>
</condition>
<condition property="jbossmq.present">
<and>
<not>
<isset property="messaging.present"/>
</not>
<not>
<isset property="hornetq.present"/>
</not>
</and>
</condition>
</target>
<!-- dependencies specific to JBoss Hornetq -->
<target name="hornetq-dependencies" if="hornetq.present"
depends="messaging-config">
<property name="jms.service.file"
value="hornetq-jms.xml"/>
<property name="jms.description" value="JBoss
Hornetq"/>
</target>
<target name="classpath-dependencies-as5" if="jbossas5"
depends="hornetq-dependencies,messaging-dependencies, jbossmq-dependencies,
quickstart-specific-dependencies">
<target name="classpath-dependencies-as4" if="jbossas4"
depends="hornetq-dependencies, messaging-dependencies, jbossmq-dependencies,
quickstart-specific-dependencies">
12. Add hornetq-jms.xml to quickstart
Verify that the ESB works with the main AS trunk (code base for AS6)
--------------------------------------------------------------------
Key: JBESB-2760
URL: https://jira.jboss.org/browse/JBESB-2760
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Rosetta
Reporter: Daniel Bevenius
Assignee: Daniel Bevenius
Fix For: 4.x
While merging https://jira.jboss.org/jira/browse/JBWS-2619 into the AS main trunk I was
not able to deploy the esb.
Even without deploying the esb code I get an error upon startup of the as server.
I also get an error with our build since conf/jboss-log4.xml does not exist in the server
created by the as trunk. This file is replaced by build.xml in
product/install/embedded-console. This might be temporary as the trunk code base is a
moving target but we should still make sure when they get closer to a release date to make
sure that we are not depending on something that is going to be removed.
I'm not sure that this is required for our 4.7 release, as this depends on the
release schedule for AS6. But I'm setting the version to 4.7 so that a decision should
be made about this.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:54 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-2760) Verify that the ESB works with the main AS trunk (code base for AS6)
[
https://issues.jboss.org/browse/JBESB-2760?page=com.atlassian.jira.plugin...
]
Rok Bertoncelj commented on JBESB-2760:
---------------------------------------
What is the state of this issue? I've checked the trunk version of jbossesb and did
not notice any changes indicating that AS6 support is being worked on...
Verify that the ESB works with the main AS trunk (code base for AS6)
--------------------------------------------------------------------
Key: JBESB-2760
URL: https://issues.jboss.org/browse/JBESB-2760
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Rosetta
Reporter: Daniel Bevenius
Assignee: Daniel Bevenius
Fix For: 4.x
While merging https://jira.jboss.org/jira/browse/JBWS-2619 into the AS main trunk I was
not able to deploy the esb.
Even without deploying the esb code I get an error upon startup of the as server.
I also get an error with our build since conf/jboss-log4.xml does not exist in the server
created by the as trunk. This file is replaced by build.xml in
product/install/embedded-console. This might be temporary as the trunk code base is a
moving target but we should still make sure when they get closer to a release date to make
sure that we are not depending on something that is going to be removed.
I'm not sure that this is required for our 4.7 release, as this depends on the
release schedule for AS6. But I'm setting the version to 4.7 so that a decision should
be made about this.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:03 p.m.
New subject: [JBoss JIRA] Assigned: (JBESB-2760) Verify that the ESB works with the main AS trunk (code base for AS6)
[
https://issues.jboss.org/browse/JBESB-2760?page=com.atlassian.jira.plugin...
]
Tom Cunningham reassigned JBESB-2760:
-------------------------------------
Assignee: Tom Cunningham (was: Daniel Bevenius)
Verify that the ESB works with the main AS trunk (code base for AS6)
--------------------------------------------------------------------
Key: JBESB-2760
URL: https://issues.jboss.org/browse/JBESB-2760
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Rosetta
Reporter: Daniel Bevenius
Assignee: Tom Cunningham
Fix For: 4.x
While merging https://jira.jboss.org/jira/browse/JBWS-2619 into the AS main trunk I was
not able to deploy the esb.
Even without deploying the esb code I get an error upon startup of the as server.
I also get an error with our build since conf/jboss-log4.xml does not exist in the server
created by the as trunk. This file is replaced by build.xml in
product/install/embedded-console. This might be temporary as the trunk code base is a
moving target but we should still make sure when they get closer to a release date to make
sure that we are not depending on something that is going to be removed.
I'm not sure that this is required for our 4.7 release, as this depends on the
release schedule for AS6. But I'm setting the version to 4.7 so that a decision should
be made about this.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:05 p.m.
New subject: [JBoss JIRA] Updated: (JBESB-2760) Verify that the ESB works with AS6
[
https://issues.jboss.org/browse/JBESB-2760?page=com.atlassian.jira.plugin...
]
Tom Cunningham updated JBESB-2760:
----------------------------------
Summary: Verify that the ESB works with AS6 (was: Verify that the ESB works
with the main AS trunk (code base for AS6))
Fix Version/s: 4.10
(was: 4.x)
Affects Version/s: 4.9
Verify that the ESB works with AS6
----------------------------------
Key: JBESB-2760
URL: https://issues.jboss.org/browse/JBESB-2760
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.9
Reporter: Daniel Bevenius
Assignee: Tom Cunningham
Fix For: 4.10
While merging https://jira.jboss.org/jira/browse/JBWS-2619 into the AS main trunk I was
not able to deploy the esb.
Even without deploying the esb code I get an error upon startup of the as server.
I also get an error with our build since conf/jboss-log4.xml does not exist in the server
created by the as trunk. This file is replaced by build.xml in
product/install/embedded-console. This might be temporary as the trunk code base is a
moving target but we should still make sure when they get closer to a release date to make
sure that we are not depending on something that is going to be removed.
I'm not sure that this is required for our 4.7 release, as this depends on the
release schedule for AS6. But I'm setting the version to 4.7 so that a decision should
be made about this.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:42 p.m.
New subject: [JBoss JIRA] Closed: (JBESB-2760) Verify that the ESB works with AS6
[
https://issues.jboss.org/browse/JBESB-2760?page=com.atlassian.jira.plugin...
]
Tom Cunningham closed JBESB-2760.
---------------------------------
Verify that the ESB works with AS6
----------------------------------
Key: JBESB-2760
URL: https://issues.jboss.org/browse/JBESB-2760
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.9
Reporter: Daniel Bevenius
Assignee: Tom Cunningham
Fix For: 4.10
While merging https://jira.jboss.org/jira/browse/JBWS-2619 into the AS main trunk I was
not able to deploy the esb.
Even without deploying the esb code I get an error upon startup of the as server.
I also get an error with our build since conf/jboss-log4.xml does not exist in the server
created by the as trunk. This file is replaced by build.xml in
product/install/embedded-console. This might be temporary as the trunk code base is a
moving target but we should still make sure when they get closer to a release date to make
sure that we are not depending on something that is going to be removed.
I'm not sure that this is required for our 4.7 release, as this depends on the
release schedule for AS6. But I'm setting the version to 4.7 so that a decision should
be made about this.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:42 p.m.
New subject: [JBoss JIRA] Resolved: (JBESB-2760) Verify that the ESB works with AS6
[
https://issues.jboss.org/browse/JBESB-2760?page=com.atlassian.jira.plugin...
]
Tom Cunningham resolved JBESB-2760.
-----------------------------------
Resolution: Done
AS6 support is now in ESB, and works in the same way as AS5 support - set the server.home
in your deployment.properties to point to an AS6 server and the AS6-specific bits will be
deployed.
Verify that the ESB works with AS6
----------------------------------
Key: JBESB-2760
URL: https://issues.jboss.org/browse/JBESB-2760
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.9
Reporter: Daniel Bevenius
Assignee: Tom Cunningham
Fix For: 4.10
While merging https://jira.jboss.org/jira/browse/JBWS-2619 into the AS main trunk I was
not able to deploy the esb.
Even without deploying the esb code I get an error upon startup of the as server.
I also get an error with our build since conf/jboss-log4.xml does not exist in the server
created by the as trunk. This file is replaced by build.xml in
product/install/embedded-console. This might be temporary as the trunk code base is a
moving target but we should still make sure when they get closer to a release date to make
sure that we are not depending on something that is going to be removed.
I'm not sure that this is required for our 4.7 release, as this depends on the
release schedule for AS6. But I'm setting the version to 4.7 so that a decision should
be made about this.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4973
days inactive
5683
days old
19 comments
5 participants
participants (5)
-
Daniel Bevenius (JIRA) -
jarkko Lietolahti (JIRA)
-
Kevin Conner (JIRA)
-
Rok Bertoncelj (JIRA)
-
Tom Cunningham (JIRA)