You are viewing a plain text version of this content. The canonical link for it is here.
Posted to xmlrpc-dev@ws.apache.org by Rob Butler <cr...@yahoo.com> on 2006/06/05 17:18:27 UTC
3.0 ETA?
Hello all,
Just wondering if there is any ETA on a 3.0 final?
Even if it's a wild guess, I'd appreciate something.
Also, would it be possible to add some support for
additional types? java.util.Set could easily be
supported with output similar to a java.util.List. If
java.util.Set support were added should it be an
extension with the apache xmlrpc extension namespace,
or should it just output the same as a java.util.List?
It would be nice if this were configurable so people
could choose.
Thanks!
Rob
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: xmlrpc-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: xmlrpc-dev-help@ws.apache.org
Re: 3.0 ETA?
Posted by Jochen Wiedmann <jo...@gmail.com>.
Rob Butler wrote:
> Is there any reason that
> org.apache.xmlrpc.common.TypeFactory specifies
> NamespaceContextImpl as its second arg instead of
> javax.xml.namespace.NamespaceContext? Using the later
> would make the code less dependent on a particular
> implementation of NamespaceContext.
Yes, see the methods startPrefixMapping, and endPrefixMapping, in
RecursiveTypeParserImpl.
Jochen
---------------------------------------------------------------------
To unsubscribe, e-mail: xmlrpc-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: xmlrpc-dev-help@ws.apache.org
Re: 3.0 ETA?
Posted by Rob Butler <cr...@yahoo.com>.
Jochen,
Sounds like a good idea. I would love to contrib a
patch but no time. If somehow I come up with some
time, I will create a patch.
Is there any reason that
org.apache.xmlrpc.common.TypeFactory specifies
NamespaceContextImpl as its second arg instead of
javax.xml.namespace.NamespaceContext? Using the later
would make the code less dependent on a particular
implementation of NamespaceContext.
Rob
--- Jochen Wiedmann <jo...@gmail.com> wrote:
> Rob Butler wrote:
>
> > Just wondering if there is any ETA on a 3.0 final?
>
> > Even if it's a wild guess, I'd appreciate
> something.
>
> My personal plan is to have some internal
> workarounds and cleanups done,
> which will hopefully be done til the end of June. At
> which point I'd assume
> the code to be API stable and call for a vote on
> 3.0beta, with additional
> four weeks for both 3.0RC1, and 3.0.
>
>
> > Also, would it be possible to add some support for
> > additional types? java.util.Set could easily be
> > supported with output similar to a java.util.List.
>
> Thinking about it, I see no reason for not replacing
> java.util.List with
> java.util.Collection. Wanna propose a patch that
> does this?
>
>
> Jochen
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> xmlrpc-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail:
> xmlrpc-dev-help@ws.apache.org
>
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: xmlrpc-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: xmlrpc-dev-help@ws.apache.org
Re: 3.0 ETA?
Posted by Jochen Wiedmann <jo...@gmail.com>.
Rob Butler wrote:
> Just wondering if there is any ETA on a 3.0 final?
> Even if it's a wild guess, I'd appreciate something.
My personal plan is to have some internal workarounds and cleanups done,
which will hopefully be done til the end of June. At which point I'd assume
the code to be API stable and call for a vote on 3.0beta, with additional
four weeks for both 3.0RC1, and 3.0.
> Also, would it be possible to add some support for
> additional types? java.util.Set could easily be
> supported with output similar to a java.util.List.
Thinking about it, I see no reason for not replacing java.util.List with
java.util.Collection. Wanna propose a patch that does this?
Jochen
---------------------------------------------------------------------
To unsubscribe, e-mail: xmlrpc-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: xmlrpc-dev-help@ws.apache.org