ws-sandesha-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Illsley (JIRA)" <j...@apache.org>
Subject [jira] Closed: (SANDESHA2-170) Determining whether to offer code needs making more robost
Date Mon, 18 Aug 2008 13:31:45 GMT

     [ https://issues.apache.org/jira/browse/SANDESHA2-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

David Illsley closed SANDESHA2-170.
-----------------------------------

    Resolution: Fixed

> Determining whether to offer code needs making more robost
> ----------------------------------------------------------
>
>                 Key: SANDESHA2-170
>                 URL: https://issues.apache.org/jira/browse/SANDESHA2-170
>             Project: Sandesha2
>          Issue Type: Bug
>            Reporter: Dave Parsons
>         Attachments: DecideToOfferMoreRobust.patch
>
>
> There could be cases e.g. JAX-WS dispatch clients where nothing is known about the AxisOperations
being invoked on the AxisService when the Sandesha module is loaded.  Therefore we cannot
always rely on deciding to offer at that point.  I suggest adding an extra check based on
what sort of MEP Axis thinks is being used at the point the createSeq msg is built.  

-- 
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: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org


Mime
View raw message