[ http://issues.apache.org/jira/browse/MUSE-65?page=comments#action_12428763 ] Dan Jemiolo commented on MUSE-65: ---------------------------------
One possibility, while very hack-ish, is to create a very simple servlet that is initialized on server startup (via web.xml) and just pings a resource type in the muse application using an improper operation request. Note that it doesn't matter if the request is for a proper operation or if it succeeds - it just has to go through to Axis2 and cause it to initialize its services because a request is coming. It would get around the problem of Axis2 not creating its services when initialized with no changes to the current code; the only downsides are that a) we'd have to add the extra servlet to the user's WAR and somehow give it enough info to send the SOAP request to the right endpoint, and b) it's an ugly hack. How much we put into this depends on whether we consider this "our" problem or one of the environment we run in. Thoughts? > 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]
