You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hivemind.apache.org by Jean-Francois Poilpret <jf...@hcm.vnn.vn> on 2005/01/07 14:12:45 UTC
HiveMind 1.1-1.0 compatibility
Hi,
I did not check out the latest HM1.1 yet (I am still working on the
"official" release exclusively), but I know there are already some
incompatibilities for libraries developed with HM1.0. In particular, in the
case of HiveTranse, I have developed several ServiceImplementationFactory
classes, and I read on the web that they will have to be rewritten for use
with 1.1.
I don't mind much about rewriting some classes for HM1.1, but I would like
however to be able to deliver libraries that can work with both HM1.0 and
1.1, without having to maintain two different sources.
Would it be possible to maintain some compatibility with HM1.1 in HM1.0, or
would it be too big an effort (and not worthy?)?
Cheers
Jean-Francois
---------------------------------------------------------------------
To unsubscribe, e-mail: hivemind-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: hivemind-dev-help@jakarta.apache.org
Re: HiveMind 1.1-1.0 compatibility
Posted by Achim Huegen <ah...@gmx-topmail.de>.
I would like to change the ServiceImplementationFactory another time
for the jmx support. I hoped that we could integrate the change in
release 1.1.
The intent behind the change is to allow the factories to return management
informationen to the caller. For example the BuilderFactory returns
construction details like property values and constructor parameter values.
The interface would return an instance of ServiceInstance where it returned
an Object reference before:
public ServiceInstance createCoreServiceImplementation(
ServiceImplementationFactoryParameters factoryParameters);
public class ServiceInstance
{
private Object _serviceInstance;
private Object _managementInfo;
...
}
So what to do? Change it now, never or create a ManagedServiceImplementationFactory
interface later?
Achim Huegen
Am Fri, 7 Jan 2005 08:29:35 -0500 schrieb Howard Lewis Ship <hl...@gmail.com>:
> Introducing that non-backwards compatible change was painful,but (in
> the long run) not as painful as having a ServiceImplementationFactory2
> kind of interface!
>
> I know its awkward, but perhaps you could have two implementations of
> your service; the 1.1 impl and a backwards compatibility impl.
>
> Use a HiveMind symbol to control which one is is instantiated:
>
> <invoke-factory>
> <construct class="${hivetrans.foo-service-impl-class}" ....
>
> Then if you want compatibility with 1.0, provide an
> ApplicationDefault for hivetrans.foo-service-impl-class that overrides
> the default (which would be the 1.1 implementation).
>
>
> On Fri, 7 Jan 2005 20:12:45 +0700, Jean-Francois Poilpret
> <jf...@hcm.vnn.vn> wrote:
>> Hi,
>>
>> I did not check out the latest HM1.1 yet (I am still working on the
>> "official" release exclusively), but I know there are already some
>> incompatibilities for libraries developed with HM1.0. In particular, in the
>> case of HiveTranse, I have developed several ServiceImplementationFactory
>> classes, and I read on the web that they will have to be rewritten for use
>> with 1.1.
>> I don't mind much about rewriting some classes for HM1.1, but I would like
>> however to be able to deliver libraries that can work with both HM1.0 and
>> 1.1, without having to maintain two different sources.
>>
>> Would it be possible to maintain some compatibility with HM1.1 in HM1.0, or
>> would it be too big an effort (and not worthy?)?
>>
>> Cheers
>>
>> Jean-Francois
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: hivemind-dev-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: hivemind-dev-help@jakarta.apache.org
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: hivemind-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: hivemind-dev-help@jakarta.apache.org
Re: HiveMind 1.1-1.0 compatibility
Posted by Howard Lewis Ship <hl...@gmail.com>.
Introducing that non-backwards compatible change was painful,but (in
the long run) not as painful as having a ServiceImplementationFactory2
kind of interface!
I know its awkward, but perhaps you could have two implementations of
your service; the 1.1 impl and a backwards compatibility impl.
Use a HiveMind symbol to control which one is is instantiated:
<invoke-factory>
<construct class="${hivetrans.foo-service-impl-class}" ....
Then if you want compatibility with 1.0, provide an
ApplicationDefault for hivetrans.foo-service-impl-class that overrides
the default (which would be the 1.1 implementation).
On Fri, 7 Jan 2005 20:12:45 +0700, Jean-Francois Poilpret
<jf...@hcm.vnn.vn> wrote:
> Hi,
>
> I did not check out the latest HM1.1 yet (I am still working on the
> "official" release exclusively), but I know there are already some
> incompatibilities for libraries developed with HM1.0. In particular, in the
> case of HiveTranse, I have developed several ServiceImplementationFactory
> classes, and I read on the web that they will have to be rewritten for use
> with 1.1.
> I don't mind much about rewriting some classes for HM1.1, but I would like
> however to be able to deliver libraries that can work with both HM1.0 and
> 1.1, without having to maintain two different sources.
>
> Would it be possible to maintain some compatibility with HM1.1 in HM1.0, or
> would it be too big an effort (and not worthy?)?
>
> Cheers
>
> Jean-Francois
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: hivemind-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: hivemind-dev-help@jakarta.apache.org
>
>
--
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind
Professional Tapestry training, mentoring, support
and project work. http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: hivemind-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: hivemind-dev-help@jakarta.apache.org