The current Axis2 hosting environment creates a chicken-egg scenario with
respect to Resource Creation and Notification
-----------------------------------------------------------------------------------------------------------------------
Key: MUSE-65
URL: http://issues.apache.org/jira/browse/MUSE-65
Project: Muse
Issue Type: Wish
Components: Deployment - Axis2
Affects Versions: 2.0.0 M2
Environment: Axis2
Reporter: Joel Hawkins
Assigned To: Dan Jemiolo
The Axis2 environment (and the muse runtime) only get initiatized once a
request has come in to the axis servlet. Which means that all Advertisement and
Notifications cannot occur until an initial request has been made. This seems
unfortunate, as the underlying resource may very well be available and in need
of some serious 'managing'.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
