[
https://jira.jboss.org/jira/browse/JBESB-2950?page=com.atlassian.jira.plu...
]
Daniel Bevenius commented on JBESB-2950:
----------------------------------------
EsbWebServiceDeployer is staged at the POST_PARSE stage and has a dependency on the
PropertyService. The problem with this is that the PropertyService is an mbean and is not
deployed until the REAL stage, so upon deployment there will be nothing for the
EsbWebServiceDeployer to do which is the problem we are having.
This can be worked around by defining the PropertyService as a bean in
esb-deployers-jboss-beans.xml:
<bean name="EsbPropertyService"
class="org.jboss.soa.esb.common.JBossESBPropertyService">
<annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(name="jboss.esb:service=PropertyService",
exposedInterface=org.jboss.soa.esb.common.JBossESBPropertyServiceMBean.class,
registerDirectly=true)</annotation>
<property name="propertyFile">
<!-- Use the ServiceBindingManager to process (xslt)
jbossesb-properties.xml and set the result to the PropertyFile attribute.-->
<value-factory bean="ServiceBindingManager"
method="getResourceBinding">
<!-- serviceName -->
<parameter>EsbPropertyService</parameter>
<!-- input -->
<parameter>${jboss.server.home.url}${/}deployers${/}esb.deployer${/}/jbossesb-properties.xml</parameter>
</value-factory>
</property>
<property
name="propertiesFileDir">${jboss.server.data.dir}</property>
</bean>
This way the EsbWebServcieDeployer can depend on the EsbPropertyService bean:
<bean name="EsbWebServiceDeployer"
class="org.jboss.soa.esb.listeners.deployers.mc.EsbWebServiceDeployer">
<depends>EsbPropertyService</depends>
</bean>
For this to work we need to extract the TransactionStrategy code from
JBossEsbPropertyService and put it into its own mbean as the current property service
declares this as a dependency and set the transaction strategy in the createService()
method.
I've tried this out manually by running the above quickstarts on both AS4 and AS5 and
this works for me.
I'll now run the integration tests and if they pass check this in.
AS5 ESB web deployments broken on server re-start
-------------------------------------------------
Key: JBESB-2950
URL:
https://jira.jboss.org/jira/browse/JBESB-2950
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Deployment, Examples
Affects Versions: 4.7
Environment: ESB 4.7 (trunk) deployed into JBoss AS 5.1.0 (running on JDK 1.6,
although that part shouldn't matter)
Reporter: David Ward
Assignee: Daniel Bevenius
Fix For: 4.7
This is a problem on ESB 4.7 (trunk) deployed into JBoss AS 5.1.0. It is *not* a problem
on ESB 4.7 (trunk) deployed into JBoss AS 4.2.3.
If you have the ESB server running, and hot-deploy either the http_gateway (uses the
HttpGatewayServlet) or the publish_as_webservice (uses EBWS) quickstart, everything works
fine. However, if you leave the quickstart deployed, then stop and re-start the server,
then although no errors appear in the log, those HTTP "endpoints" are not
available. For example, if you try hitting
http://localhost:8080/Quickstart_http_gateway/http/sales in a web browser after a restart,
you get a 404 status error.
I chatted briefly with TomF about this, and he thinks there might be an issue with the
EsbWebServiceDeployer or related web metadata / web model, or undeploy code?
--
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