[ http://issues.apache.org/jira/browse/AXIS2-1120?page=comments#action_12433813 ] Deepal Jayasinghe commented on AXIS2-1120: ------------------------------------------
Well , the problem with option 2 is , Axis2 have no idea about the behavior of the handler. I mean Axis2 does not know which handler capable for what, so Axis2 can not take the decision at the run time by looking at the message context. But as a handler author he knows what he is doing , that is why I mentioned at the runtime handler can check the message context to check whether it is need to invoke or just ignore the message. Hmm , I dont think we are in a position to make these changes for 1.1 even if we really need to take this into consideration. So I will reduce the priority :) > Phases concept is too confusing - please change for v1.1 > -------------------------------------------------------- > > Key: AXIS2-1120 > URL: http://issues.apache.org/jira/browse/AXIS2-1120 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Improvement > Components: core > Affects Versions: 1.0 > Reporter: Thilo Frotscher > Priority: Blocker > > With Axis2 1.0 it can easily happen that you engage a module with services > without realizing it! > This is because even if explicitly engaging a module with a *single* service > or a *single* operation, its handlers will automatically be invoked for *all* > services if they belong to a global phase. There's no warning messages or > anything that prevent's you from doing this. IMHO this bevaviour is very > confusing, especially for beginners. > I think there are two possible solutions to this: > - disallow engagement with single services or operations for all modules that > contain handlers in global phases > (at the very least, display a warning message that the module will actually > be invoked for *all* services) > - or make sure that handlers in global phases are *available* to all > services, but will only be invoked for services that they were *explicitly* > engaged with > Either way, the release of Axis2 1.1 is a very good opportunity to change > this behaviour. The later you do this, the more backwards compatibility might > have to be sacrificed. > I am sure that many users will vote for this change once the use of Axis2 in > general and modules in particular is more widespread. > There was a discussion about this on the mailing list, but somehow it died > out: http://marc.theaimsgroup.com/?l=axis-dev&m=115394666310204&w=2 > Please consider making this change for v1.1 > Thanks! -- 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]
