You are viewing a plain text version of this content. The canonical link for it is here.
Posted to muse-dev@ws.apache.org by "Joel Hawkins (JIRA)" <ji...@apache.org> on 2006/08/17 21:19:13 UTC
[jira] Created: (MUSE-65) The current Axis2 hosting environment
creates a chicken-egg scenario with respect to Resource Creation and
Notification
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: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org
[jira] Updated: (MUSE-65) The current hosting environments create a
chicken-egg scenario with respect to Resource Creation and Notification
Posted by "Dan Jemiolo (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/MUSE-65?page=all ]
Dan Jemiolo updated MUSE-65:
----------------------------
Component/s: Deployment - Mini SOAP Engine
(was: Deployment - Axis2)
Summary: The current hosting environments create a chicken-egg scenario with respect to Resource Creation and Notification (was: The current Axis2 hosting environment creates a chicken-egg scenario with respect to Resource Creation and Notification)
Fix Version/s: 2.2.0
Environment: All (was: Axis2)
This applies to all the hosting environments, but I think we'll only be able to solve it with the Mini platform. Fortunately, this runs on J2EE and OSGi. I'd like to use the Servlet.init() method and some kind of "fake" addressing context to allow initialization prior to a request. The current MiniIsolationLayer requires a HttpServletRequest object for construction, so I'll have to make an alternate constructor that still gets the same init data it needs. I think we can achieve this in 2.2.
> The current hosting environments create 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 - 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.
-
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: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org
[jira] Closed: (MUSE-65) The current hosting environments create a
chicken-egg scenario with respect to Resource Creation and Notification
Posted by "Dan Jemiolo (JIRA)" <ji...@apache.org>.
[ 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: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org
[jira] Commented: (MUSE-65) The current Axis2 hosting environment
creates a chicken-egg scenario with respect to Resource Creation and
Notification
Posted by "Dan Jemiolo (JIRA)" <ji...@apache.org>.
[ 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: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org
[jira] Commented: (MUSE-65) The current Axis2 hosting environment
creates a chicken-egg scenario with respect to Resource Creation and
Notification
Posted by "Joel Hawkins (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/MUSE-65?page=comments#action_12428770 ]
Joel Hawkins commented on MUSE-65:
----------------------------------
I'd like to seperate the problem into two parts. One is the tight coupling of the initialization code to the requirement of an Axis operation context, and the other is the actual kicking into service of the Axis servlet. I want to do some prototyping to see if Notification can work without an actual Axis request (at least for the OSGi implementation). For that, I'd like to have a protected method in the IsolationLayer that returns the necessary information that is extracted from the initial operation context, and then have a constructor for the environment that consumes this information directly, rather than using the operation context as a carrier.
Of course, this probably only makes sense for the OSGi environment, where I'm already in control prior to any external requests.
> 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: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org