[
https://jira.jboss.org/browse/JBESB-2874?page=com.atlassian.jira.plugin.s...
]
Daniel Bevenius commented on JBESB-2874:
----------------------------------------
Daniel, we haven't updated trunk to 5.1 yet. Does it behave the
same way in trunk?
JBoss AS 5.1.0 was the target version for our A5 deployers as far
as I remember. Sorry if I misunderstood you question here but what did you mean that trunk
has not been updated to 5.1? If you mean that we don't bundle 5.1 in our release you
are right. It was decided that doing so would make the distribution to big.
The issue I've been having might be a JBoss WS issue but I need to ask those guys
about it. I'll post back with a reference if this is related.
Deployers do not cleanly represent dependencies
-----------------------------------------------
Key: JBESB-2874
URL:
https://jira.jboss.org/browse/JBESB-2874
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Deployment
Affects Versions: 4.7
Reporter: Kevin Conner
Assignee: Magesh Kumar B
Fix For: 4.9
Attachments: redeploy-issue.jar
The deployers create a separate object to represent the ESB deployment, expressing the
contained dependencies, but any forced restart of this object (due to dependencies) does
not redo any of the work contained in the deployer.
We now have a lot of work which, as a consequence, misses out on this process.
- ebws
- http gateway
- property substitution
We need to move all this functionality into a separate object which can cleanly take part
in the dependency process.
--
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