You are viewing a plain text version of this content. The canonical link for it is here.
Posted to slide-dev@jakarta.apache.org by Don Smith <sm...@UMDNJ.EDU> on 2001/03/28 23:35:26 UTC
private variables in org.apache.webdav.methods.PropFindMethod
Would it be possible to convert the private variables
type propertyNames
to protected instead of private variables?
I am trying to extend Propfind so that I can have more than one namespace
and namespaceinfo and am
having trouble overriding the generateQuery method because these two
variables are private.
Is there a better way to do this?
many thanks
Don Smith
Re: private variables in org.apache.webdav.methods.PropFindMethod
Posted by Don Smith <sm...@UMDNJ.EDU>.
Well the getter for type fixes half of the problem(sorry I missed that)
but I only see a setter for propertynames, which I need if I want to
reimpliment generateQuery (again so i can get that MS HTTPMail String)
Don Smith
On Wed, 28 Mar 2001, Remy Maucherat wrote:
> Quoting Don Smith <sm...@UMDNJ.EDU>:
>
> > Also not to clutter the list but I was more interested in having
> > protected
> > methods in the client not the server.
>
> Which methods in particular ?
> There are some private fields, but with public accessors/mutators.
>
> Remy
>
Re: private variables in org.apache.webdav.methods.PropFindMethod
Posted by Remy Maucherat <re...@betaversion.org>.
Quoting Don Smith <sm...@UMDNJ.EDU>:
> Also not to clutter the list but I was more interested in having
> protected
> methods in the client not the server.
Which methods in particular ?
There are some private fields, but with public accessors/mutators.
Remy
Re: private variables in org.apache.webdav.methods.PropFindMethod
Posted by Don Smith <sm...@UMDNJ.EDU>.
Also not to clutter the list but I was more interested in having protected
methods in the client not the server.
Again many thanks
Don Smith
On Wed, 28 Mar 2001, Don Smith wrote:
> I just got the cvs commit email, thanks very much.
>
> Is extending Propfind the way to do this, or is there already support to
> generate:
>
> <D:pruopfind xmlns:D="DAV:"
> xmlns:h="http://schemas.microsoft.com/hotmail/"
> xmlns:hm="urn:schemas:httpmail:" >
>
> I saw the boolean ms proprietary support, (though i don't see it in the
> webcvs?) should I try to do this a different way?
>
> many thanks
>
> Don Smith
> On Wed, 28 Mar 2001, Remy Maucherat wrote:
>
> > Quoting Don Smith <sm...@UMDNJ.EDU>:
> >
> > > Actually what I'd like to do is to be able to generate this line
> > >> >
> > > and the only way I found out how to do it was to extend PropFindMethod
> > > and
> > > XMLPrinter so that I could pass an array of namespaces, again any other
> > > ideas would always be appreciated.
> >
> > You should be able to extend PROPFIND now :)
> >
> > Remy
> >
>
Re: private variables in org.apache.webdav.methods.PropFindMethod
Posted by Don Smith <sm...@UMDNJ.EDU>.
I just got the cvs commit email, thanks very much.
Is extending Propfind the way to do this, or is there already support to
generate:
<D:pruopfind xmlns:D="DAV:"
xmlns:h="http://schemas.microsoft.com/hotmail/"
xmlns:hm="urn:schemas:httpmail:" >
I saw the boolean ms proprietary support, (though i don't see it in the
webcvs?) should I try to do this a different way?
many thanks
Don Smith
On Wed, 28 Mar 2001, Remy Maucherat wrote:
> Quoting Don Smith <sm...@UMDNJ.EDU>:
>
> > Actually what I'd like to do is to be able to generate this line
> >> >
> > and the only way I found out how to do it was to extend PropFindMethod
> > and
> > XMLPrinter so that I could pass an array of namespaces, again any other
> > ideas would always be appreciated.
>
> You should be able to extend PROPFIND now :)
>
> Remy
>
Re: private variables in org.apache.webdav.methods.PropFindMethod
Posted by Remy Maucherat <re...@betaversion.org>.
Quoting Don Smith <sm...@UMDNJ.EDU>:
> Actually what I'd like to do is to be able to generate this line
>
> <D:propfind xmlns:D="DAV:"
> xmlns:h="http://schemas.microsoft.com/hotmail/"
> xmlns:hm="urn:schemas:httpmail:" >
>
> and the only way I found out how to do it was to extend PropFindMethod
> and
> XMLPrinter so that I could pass an array of namespaces, again any other
> ideas would always be appreciated.
You should be able to extend PROPFIND now :)
Remy
Re: private variables in org.apache.webdav.methods.PropFindMethod
Posted by Don Smith <sm...@UMDNJ.EDU>.
Actually what I'd like to do is to be able to generate this line
<D:propfind xmlns:D="DAV:" xmlns:h="http://schemas.microsoft.com/hotmail/"
xmlns:hm="urn:schemas:httpmail:" >
and the only way I found out how to do it was to extend PropFindMethod and
XMLPrinter so that I could pass an array of namespaces, again any other
ideas would always be appreciated.
thanks
Don Smith
On Wed, 28 Mar 2001, Remy Maucherat wrote:
> Quoting Don Smith <sm...@UMDNJ.EDU>:
>
> > Would it be possible to convert the private variables
> > type propertyNames
> > to protected instead of private variables?
> > I am trying to extend Propfind so that I can have more than one
> > namespace
> > and namespaceinfo and am
> > having trouble overriding the generateQuery method because these two
> > variables are private.
> >
> > Is there a better way to do this?
>
> Good idea. I'll change that to protected.
>
> I don't quite understand what you're trying to do here. Do you want to add
> special processing for some properties ?
> If you want to be able to have some properties in different namespaces, it
> should already be working fine.
>
> I plan to reorganize a bit PROPFIND in the near future, to make it faster (if
> possible), but more importantly more modular.
>
> Remy
>
Re: private variables in org.apache.webdav.methods.PropFindMethod
Posted by Remy Maucherat <re...@betaversion.org>.
Quoting Don Smith <sm...@UMDNJ.EDU>:
> Would it be possible to convert the private variables
> type propertyNames
> to protected instead of private variables?
> I am trying to extend Propfind so that I can have more than one
> namespace
> and namespaceinfo and am
> having trouble overriding the generateQuery method because these two
> variables are private.
>
> Is there a better way to do this?
Good idea. I'll change that to protected.
I don't quite understand what you're trying to do here. Do you want to add
special processing for some properties ?
If you want to be able to have some properties in different namespaces, it
should already be working fine.
I plan to reorganize a bit PROPFIND in the near future, to make it faster (if
possible), but more importantly more modular.
Remy