You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Gerhard Froehlich <g-...@gmx.de> on 2002/02/10 12:36:58 UTC
[simplestore] methods in Store interface
Hi Juozas,
why did you removed the methods
containsKey,
isEmpty
size
clear
Ok maybe they are not meaningful anymore but then they
shouldn't be implemented in the SoftRefMemoryStore!
Could you please explain me your thoughts here.
~Gerhard
----------------------------
I just found the last bug...
----------------------------
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [simplestore] methods in Store interface
Posted by Juozas Baliuka <ba...@mwm.lt>.
Ok
----- Original Message -----
From: "Gerhard Froehlich" <g-...@gmx.de>
To: "Jakarta Commons Developers List" <co...@jakarta.apache.org>
Sent: Monday, February 11, 2002 6:13 PM
Subject: RE: [simplestore] methods in Store interface
> Juozas,
>
> >> Ok maybe they are not meaningful anymore but then they
> >> shouldn't be implemented in the SoftRefMemoryStore!
> >
> >Yes we will remove this from SoftRefMemoryStore, we dont need method
remove,
> >it not meaningful, it removes only maping , but we don't need to remove
> >maping if object is reacheble and Store will remove maping itself then
> >object is unreacheble.
>
> That's true!
>
> >at last we have Store interface (minimalistic Cache):
> >
> >public interface Store {
> >
> > Object get(Object key);
> >// null value means no maping;(the same as "contains")
> > void put(Object key,Object object);
> >//Object can be null , we can remove mapping if value is null.
>
> Ok then I will remove the other not public methods from SoftRefMemoryStore
> too!
>
> ~Gerhard
>
> -------------------------------------------
> Beer is God's way of showing us he loves us
> and wants us to be happy...
> -------------------------------------------
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: [simplestore] methods in Store interface
Posted by Gerhard Froehlich <g-...@gmx.de>.
Juozas,
>> Ok maybe they are not meaningful anymore but then they
>> shouldn't be implemented in the SoftRefMemoryStore!
>
>Yes we will remove this from SoftRefMemoryStore, we dont need method remove,
>it not meaningful, it removes only maping , but we don't need to remove
>maping if object is reacheble and Store will remove maping itself then
>object is unreacheble.
That's true!
>at last we have Store interface (minimalistic Cache):
>
>public interface Store {
>
> Object get(Object key);
>// null value means no maping;(the same as "contains")
> void put(Object key,Object object);
>//Object can be null , we can remove mapping if value is null.
Ok then I will remove the other not public methods from SoftRefMemoryStore
too!
~Gerhard
-------------------------------------------
Beer is God's way of showing us he loves us
and wants us to be happy...
-------------------------------------------
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [simplestore] methods in Store interface
Posted by Juozas Baliuka <ba...@mwm.lt>.
> Hi Juozas,
> why did you removed the methods
> containsKey,
> isEmpty
> size
> clear
>
> Ok maybe they are not meaningful anymore but then they
> shouldn't be implemented in the SoftRefMemoryStore!
Yes we will remove this from SoftRefMemoryStore, we dont need method remove,
it not meaningful, it removes only maping , but we don't need to remove
maping if object is reacheble and Store will remove maping itself then
object is unreacheble.
at last we have Store interface (minimalistic Cache):
public interface Store {
Object get(Object key);// null value means no maping;(the same as
"contains")
void put(Object key,Object object);
//Object can be null , we can remove mapping if value is null.
}
>
> Could you please explain me your thoughts here.
>
> ~Gerhard
>
> ----------------------------
> I just found the last bug...
> ----------------------------
>
>
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [betwixt] ID and IDREF attributes
Posted by robert burrell donkin <ro...@mac.com>.
On Sunday, February 10, 2002, at 04:11 PM, James Strachan wrote:
> Yes thats right. The only way to specify the ID and IDREF types is to use
> DTDs or some other schema language. Its a shame this kinda stuff wasn't in
> straight XML without the DTD/Schema layer being required but thats another
> story...
>
> From betwixt's perspective I guess the XMLBeanInfo should know what ID
> attribute ('foo') and IDREF attribute ('fooRef') to use.
good - that's what i was thinking too :)
maybe it'll be possible to do something with contexts and expressions to
get the correct value without adding special cases to BeanWriter.
to make life easier we could add properties (defaulting to the
conventional names) to XMLIntrospector. XMLIntrospector would then use
these to add appropriate AttributeDescription's when introspecting.
- robert
>
> James
> ----- Original Message -----
> From: "robert burrell donkin" <ro...@mac.com>
> To: "Jakarta Commons Developers List" <co...@jakarta.apache.org>
> Sent: Sunday, February 10, 2002 1:57 PM
> Subject: [betwixt] ID and IDREF attributes
>
>
>> the way that i read the xml spec, though 'id' and 'idref' are the most
>> commonly chosen (conventional) attribute names for the unique attributes
>> of type ID and IDREF, it is possible that each element could have
>> different names. for example, in the same document an element <alpha>
>> might have attribute 'foo' specified as ID and 'fooRef' as IDREF whilst
>> element <beta> uses attributes 'foobar' and 'foobarRef'.
>>
>> am i right?
>>
>> - robert
>>
>>
>> --
>> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
>> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>
>
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
>
>
> --
> To unsubscribe, e-mail: <mailto:commons-dev-unsubscribe@jakarta.apache.
> org>
> For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.
> org>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [betwixt] ID and IDREF attributes
Posted by James Strachan <ja...@yahoo.co.uk>.
Yes thats right. The only way to specify the ID and IDREF types is to use
DTDs or some other schema language. Its a shame this kinda stuff wasn't in
straight XML without the DTD/Schema layer being required but thats another
story...
>From betwixt's perspective I guess the XMLBeanInfo should know what ID
attribute ('foo') and IDREF attribute ('fooRef') to use.
James
----- Original Message -----
From: "robert burrell donkin" <ro...@mac.com>
To: "Jakarta Commons Developers List" <co...@jakarta.apache.org>
Sent: Sunday, February 10, 2002 1:57 PM
Subject: [betwixt] ID and IDREF attributes
> the way that i read the xml spec, though 'id' and 'idref' are the most
> commonly chosen (conventional) attribute names for the unique attributes
> of type ID and IDREF, it is possible that each element could have
> different names. for example, in the same document an element <alpha>
> might have attribute 'foo' specified as ID and 'fooRef' as IDREF whilst
> element <beta> uses attributes 'foobar' and 'foobarRef'.
>
> am i right?
>
> - robert
>
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
[betwixt] ID and IDREF attributes
Posted by robert burrell donkin <ro...@mac.com>.
the way that i read the xml spec, though 'id' and 'idref' are the most
commonly chosen (conventional) attribute names for the unique attributes
of type ID and IDREF, it is possible that each element could have
different names. for example, in the same document an element <alpha>
might have attribute 'foo' specified as ID and 'fooRef' as IDREF whilst
element <beta> uses attributes 'foobar' and 'foobarRef'.
am i right?
- robert
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>