If you have tested that the built-in FileSystem was working correctly,
I am questioning myself why your customised client was not working.
I guess the first action to consider is to check your
subscribe-request XML. Does it have the same XML content with the
given example? You might use the packet capture software to see what
is the XML content exchanged when you submit any soap document.
I have tried using filesystem example in a completely different
environment, and it was working fine. I was just trying to match the
SOAP document in every request my client made compared with the given
SOAP doc example. Therefore, a new client should always compose the
correct XML text.
Sorry if somehow I misinterpreted your question.
regards.
On 6/23/06, Ralf Schroth <
ralf@...> wrote:
> Hi,
>
> I'm currently evaluating if pubscribe is uasble for my thesis' task.
>
> The FileSystem example worked with the supplied SoapClient and the
> supplied SOAP-request, so I tried to create a client n my own. My
> first try was to create one using WSDL2Java from the WS-Addressing
> package based on the created WSDL file for the service.
>
> After fixing some initial problems caused by a missing
> <wsa:Action>-header and some fiddling around with the passing of the
> subscribe-requests parameters I'm now stuck with some error telling me
> the topic path "fs:MountPointDirectory" was referencing an unknown
> topic namespace.
>
> Are there any working client implementations available or at least
> some documentation on creating a client to perform the subscriptions?
>
> TIA & Best regards
> Ralf
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
pubscribe-user-unsubscribe@...
> For additional commands, e-mail:
pubscribe-user-help@...
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail:
pubscribe-user-unsubscribe@...
For additional commands, e-mail:
pubscribe-user-help@...
