SoapOpera port for GNU Smalltalk

Hi,

on and mostly off during the last week I have been porting SoapOpera to GNU
Smalltalk. The SoapCore functionality seems to work according to the test
cases. We are now missing the Server and Client part that needs to be
different for GNU Smalltalk.

I have the current code here[1]. The two issues with the SoapCore that are
left is date parsing of DateTime>>#readFrom: and that our XML Parser
integration does not make the namespaces available as attributes.

The Client functionality should be implemented with NetHTTP and the Server
functionality probably with Swazoo.

any help would be welcome
        holger



[1] http://gitorious.org/gnu-smalltalk-ports/soapopera

_______________________________________________
help-smalltalk mailing list
[hidden email]
http://lists.gnu.org/mailman/listinfo/help-smalltalk

On 02/27/2011 11:47 AM, Holger Hans Peter Freyther wrote:
> I have the current code here[1]. The two issues with the SoapCore that are
> left is date parsing of DateTime>>#readFrom: and that our XML Parser
> integration does not make the namespaces available as attributes.

What exactly is the problem with XML?  Namespace declarations are not
attributes, they have their own SAX events and (I think) their own
representation in the DOM.  If not, the latter can be added.

Paolo

_______________________________________________
help-smalltalk mailing list
[hidden email]
http://lists.gnu.org/mailman/listinfo/help-smalltalk

On 02/27/2011 03:54 PM, Paolo Bonzini wrote:
> On 02/27/2011 11:47 AM, Holger Hans Peter Freyther wrote:
>> I have the current code here[1]. The two issues with the SoapCore that are
>> left is date parsing of DateTime>>#readFrom: and that our XML Parser
>> integration does not make the namespaces available as attributes.
>
> What exactly is the problem with XML?  Namespace declarations are not
> attributes, they have their own SAX events and (I think) their own
> representation in the DOM.  If not, the latter can be added.

Hey,

the issue is with the testcode that parses the SOAP Document and then tries to
to verify the namespaces inside this document. Gitorious seems to have issues
right now and I can't point you to the code. The other part, also more with
the test code, it tries to parse some elements and the Squeak/Pharo XML parser
will not complain about missing namespaces, I subclassed the XMLParser to add
this behavior as well. Once I have my HTTP client integration I can see if
there is any real world implication...

_______________________________________________
help-smalltalk mailing list
[hidden email]
http://lists.gnu.org/mailman/listinfo/help-smalltalk

On 02/27/2011 11:47 AM, Holger Hans Peter Freyther wrote:

>
> The Client functionality should be implemented with NetHTTP and the Server
> functionality probably with Swazoo.

Hi,

I have implemented the HTTP client side of things using Net.HTTP.HTTPClient. A
simple query (the one I need right now) seems to work, I know that redirection
and errors are not handled properly yet. I have pushed this to the repository
on gitorious.

holger

_______________________________________________
help-smalltalk mailing list
[hidden email]
http://lists.gnu.org/mailman/listinfo/help-smalltalk

On 03/11/2011 01:06 PM, Holger Hans Peter Freyther wrote:

> I have implemented the HTTP client side of things using Net.HTTP.HTTPClient. A
> simple query (the one I need right now) seems to work, I know that redirection
> and errors are not handled properly yet. I have pushed this to the repository
> on gitorious.

Hey,

okay I handle HTTP ERROR (NetClient.ProtocolError) and HTTP Redirects
(NetClient.HTTP.RedirectError) to some degree now. The SoapOpera port can do
what I need right now, I plan to merge back some patches to Pharo now.

cheers
        holger

_______________________________________________
help-smalltalk mailing list
[hidden email]
http://lists.gnu.org/mailman/listinfo/help-smalltalk