[ 
https://issues.apache.org/jira/browse/MUSE-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465752
 ] 

Christian Ewers commented on MUSE-182:
--------------------------------------

It works for me, in a way that the ServiceGroup doesn't accept my addEntry with 
a terminationTime without a InitialTerminationTime-capability. But I don't know 
why I don't get the correct FaultMessage that is thrown in the modified 
SimpleServiceGroup (I used the muse-2.2.0-2007-01-18-02-00-bin snapshot)
I get the following message from the ServiceGroup as AddResponse:

<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope";>
    <soap:Header>
        <wsa:To 
xmlns:wsa="http://www.w3.org/2005/08/addressing";>http://www.w3.org/2005/08/addressing/role/anonymous</wsa:To>
        <wsa:Action 
xmlns:wsa="http://www.w3.org/2005/08/addressing";>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
        <wsa:MessageID 
xmlns:wsa="http://www.w3.org/2005/08/addressing";>uuid:82fd3921-b461-1915-361b-d03ea3547f76</wsa:MessageID>
        <wsa:RelatesTo RelationshipType="wsa:Reply" 
xmlns:wsa="http://www.w3.org/2005/08/addressing";>uuid:d2a3e68d-6663-9fd1-8a4c-725b9751a083</wsa:RelatesTo>
        <wsa:From xmlns:wsa="http://www.w3.org/2005/08/addressing";>
            
<wsa:Address>http://localhost:8080/RegistryService/services/ServiceGroup</wsa:Address>
        </wsa:From>
    </soap:Header>
    <soap:Body>
        <soap:Fault>
            <soap:Code>
                <soap:Value>soap:Receiver</soap:Value>
            </soap:Code>
            <soap:Reason>
                <soap:Text/>
            </soap:Reason>
        </soap:Fault>
    </soap:Body>
</soap:Envelope>

> ServiceGroup.add must return a fault if it can not process a given 
> InitialTerminationTime
> -----------------------------------------------------------------------------------------
>
>                 Key: MUSE-182
>                 URL: https://issues.apache.org/jira/browse/MUSE-182
>             Project: Muse
>          Issue Type: Bug
>          Components: WSRF WSSG ServiceGroup
>    Affects Versions: 2.1.0
>            Reporter: Christian Ewers
>         Assigned To: Dan Jemiolo
>             Fix For: 2.2.0
>
>
> I tried to add a Resource  to a ServiceGroup with an InitialTerminationTime
> by using the standard WS-ServiceGroupEntry-1_2.wsdl.
> But the Entries were never destroyed...
> I figured out that I didn't declare the wsrl-TerminationTime and
> wsrl-CurrentTime properties and I didn't declare the
> ScheduledTermination-Capability.
> The SimpleServiceGroup capability checks for the
> ScheduledTermination-Capability and only if it gets it it schedules the
> terminaton of the entry.
> When looking for the fault I found a incompatibility to the specification.
> According to the standard the add() method should fail when it can not
> schedule the termnination:
> From http://docs.oasis-open.org/wsrf/wsrf-ws_service_group-1.2-spec-os.pdf
> - line 493
> ---
> If the ServiceGroup is unable or unwilling to set the TerminationTime
> resource property of  the ServiceGroupEntry resource to the given value of
> the "absolute time" form or a value greater, then the Add request MUST
> fault"
> ---
> So I think the createEntry-method of the SimpleServiceGroup should throw a
> AddRefusedFault when it can't find the "scheduled-termination"-capability.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://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]

Reply via email to