[JBoss JIRA] Updated: (JBESB-387) jUDDI-registry (juddi.war) is missing deploy/undeploy ant task
by Mark Little (JIRA)
[ http://jira.jboss.com/jira/browse/JBESB-387?page=all ]
Mark Little updated JBESB-387:
------------------------------
Fix Version/s: 4.2 Milestone Release 2
(was: 5.0)
> jUDDI-registry (juddi.war) is missing deploy/undeploy ant task
> --------------------------------------------------------------
>
> Key: JBESB-387
> URL: http://jira.jboss.com/jira/browse/JBESB-387
> Project: JBoss ESB
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Registry and Repository
> Reporter: jarkko Lietolahti
> Assigned To: Kurt Stam
> Fix For: 4.2 Milestone Release 2
>
> Attachments: build.xml, deployment.properties
>
>
> As I hate copying files I found out that jUDDI-registry in trunk/product/install/jUDDI-registry is missing proper ant build.xml. Find it attacted here.
> The build.xml relies on a new global deployment.properties located at ../../../deployment.properties from trunk/product/install/jUDDI-registry that is in the root of the project. This new file should be there that one only has to configure org.jboss.esb.appserver.home and org.jboss.esb.appserver.config only ONCE to make deployment a lot easier for new checkouts and installations. I hate nothing more than copying files to some weird location (e.g. H:/dev/etc ) when running ant first time in a directory ;)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 1 month
[JBoss JIRA] Updated: (JBESB-193) Need support for notification generatoin from within ActionProcessor.process method
by Mark Little (JIRA)
[ http://jira.jboss.com/jira/browse/JBESB-193?page=all ]
Mark Little updated JBESB-193:
------------------------------
Fix Version/s: 4.2
(was: 5.0)
> Need support for notification generatoin from within ActionProcessor.process method
> -----------------------------------------------------------------------------------
>
> Key: JBESB-193
> URL: http://jira.jboss.com/jira/browse/JBESB-193
> Project: JBoss ESB
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Rosetta
> Affects Versions: 5.0
> Reporter: Tom Fennelly
> Assigned To: Mark Little
> Fix For: 4.2
>
>
> In version 4.0, the Action Processing pipeline management code raises notifications in response to an exception from the ActionProcessor.process method. The pipeline managemnt code calls the getOkNotification (no exception) or getErrorNotification (exception) to get the notification message.
> For many reasons, this is a very flawed model. Notifications should be raised from within the process method by means of attaching the notifications (error or otherwise) to the message (the mechanism is a design issue). Once the process method returns, the pipline processing management code can check the message for notifications. If there are errors, it can/should (?) abort the message processing, send the error notification (by whatever notification options are configured on the listener) and signal the failure to the calling process (by whatever failure config is configured on the listener).
> The getOk and getErro methods can then be removed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 1 month