[
https://issues.apache.org/jira/browse/MUSE-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Jemiolo closed MUSE-65.
---------------------------
Resolution: Incomplete
We hashed this out here:
http://marc.theaimsgroup.com/?l=muse-user&m=116775708010331&w=2
and other places, but still don't have a solution.
Joel also noted that changing the behavior on OSGi and not J2EE would be
inconsistent and confusing to users. So I think we're stuck with this, unless
people want to implement the described hack for their situation.
> The current hosting environments create a chicken-egg scenario with respect
> to Resource Creation and Notification
> -----------------------------------------------------------------------------------------------------------------
>
> Key: MUSE-65
> URL: https://issues.apache.org/jira/browse/MUSE-65
> Project: Muse
> Issue Type: Wish
> Components: Deployment - Mini SOAP Engine
> Affects Versions: 2.0.0 M2
> Environment: All
> Reporter: Joel Hawkins
> Assigned To: Dan Jemiolo
> Fix For: 2.2.0
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
