You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by Peter Donald <do...@apache.org> on 2001/09/21 16:36:06 UTC
Re: Centrally specified interfaces for Phoenix services
On Sat, 22 Sep 2001 01:07, Paul Hammant wrote:
> 1) Central definition of interfaces (and exceptions)
>
> Pros : Simple solution
> Cons : Not version tolerant, though could have heretical version
> numbers in package or class names (ref LayoutManager2). Only good for
> regular server concepts (HTTPServer) as opposed to bespoke concepts
> (company X's ABC Server)
>
> 2) Promotion of interfaces (and exceptions). SAR file contains a jar of
> interfaces that it implements, it could hand it to the parent component
> (Phoenix) and Phoenix could make them available seperately, not
> necessarily at promordial level. It's an RMI type concept, but RMI is
> overkill for several reasons, not least of which is the ill-defined
> RemoteException.
>
> Pros : Can tolerate different versions. Good for standards based
> services as well as bespoke ones.
> Cons : Difficult to implement
>
> Thoughts?
I like (1)
--
Cheers,
Pete
-----------------------------------------------------------------------
| I thought there was a knob on the TV to turn up the intelligence. |
| There's a knob called "brightness", but it doesn't work. |
-----------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: Centrally specified interfaces for Phoenix services
Posted by Eung-ju Park <co...@apache.org>.
> Proposal : We move org.apache.avalon.cornerstone.services.* to
> org.apache.avalon.pheonix.services.*
-1.
Phoenix does not provide services. Phoenix just manage services.
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: Centrally specified interfaces for Phoenix services
Posted by Paul Hammant <Pa...@yahoo.com>.
Peter ,
>
>Cornerstone pushes to phoenix during install? So basically cornerstone will
>export all .sars into
>
>${install.dir}/apps
>
>and any service interface jars into
>
>${install.dir}/lib
>
>Like?
>
Will do.
- PH
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: Centrally specified interfaces for Phoenix services
Posted by Peter Donald <do...@apache.org>.
On Tue, 25 Sep 2001 21:01, Paul Hammant wrote:
> Peter,
>
> >Go for it re: cornerstone but what needs to be changed in phoenix
> >build-process ?
>
> Good question. Should cornerstone push the jar to phoenix, or should
> phoenix pull from cornerstone? Related - should it be automatic (part
> of dist) or should it be an "import" or "export" target.
Cornerstone pushes to phoenix during install? So basically cornerstone will
export all .sars into
${install.dir}/apps
and any service interface jars into
${install.dir}/lib
Like?
--
Cheers,
Pete
-------------------------------------------------------
To fight and conquer in all your battles is not supreme
excellence; supreme excellence consists in breaking the
enemy's resistance without fighting. - Sun Tzu, 300 B.C.
-------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: Centrally specified interfaces for Phoenix services
Posted by Peter Donald <do...@apache.org>.
On Tue, 25 Sep 2001 17:11, Peter Donald wrote:
> On Tue, 25 Sep 2001 18:12, Paul Hammant wrote:
> > Peter
> >
> > >$ cp cornerstone-services.jar $PHOENIX_HOME/lib
> >
> > Can I go ahead an effect the changes in Cornerstone and Phoenix
> > (include, exclude, copy)?
> >
> > Any objections?
>
> Go for it re: cornerstone but what needs to be changed in phoenix
> build-process ?
Also the new cornerstone-services.jar can replace cornerstone-compilation.jar
aswell ;)
--
Cheers,
Pete
----------------------------------------
Why does everyone always overgeneralize?
----------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: Centrally specified interfaces for Phoenix services
Posted by Paul Hammant <Pa...@yahoo.com>.
Peter,
>Go for it re: cornerstone but what needs to be changed in phoenix
>build-process ?
>
Good question. Should cornerstone push the jar to phoenix, or should
phoenix pull from cornerstone? Related - should it be automatic (part
of dist) or should it be an "import" or "export" target.
- PH
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: Centrally specified interfaces for Phoenix services
Posted by Peter Donald <do...@apache.org>.
On Tue, 25 Sep 2001 18:12, Paul Hammant wrote:
> Peter
>
> >$ cp cornerstone-services.jar $PHOENIX_HOME/lib
>
> Can I go ahead an effect the changes in Cornerstone and Phoenix
> (include, exclude, copy)?
>
> Any objections?
Go for it re: cornerstone but what needs to be changed in phoenix
build-process ?
--
Cheers,
Pete
-------------------------------------------------------
"I would like to take you seriously but to do so would
affront your intelligence" -William F. Buckley, JR
-------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: Centrally specified interfaces for Phoenix services
Posted by Paul Hammant <Pa...@yahoo.com>.
>
>
>$ cp cornerstone-services.jar $PHOENIX_HOME/lib
>
In the phoenix build script?
+1
:-)
-PH
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: Centrally specified interfaces for Phoenix services
Posted by Paul Hammant <Pa...@yahoo.com>.
Peter
>$ cp cornerstone-services.jar $PHOENIX_HOME/lib
>
Can I go ahead an effect the changes in Cornerstone and Phoenix
(include, exclude, copy)?
Any objections?
-PH
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: Centrally specified interfaces for Phoenix services
Posted by Peter Donald <do...@apache.org>.
On Mon, 24 Sep 2001 07:30, Paul Hammant wrote:
> Peter,
>
> >>Proposal : We move org.apache.avalon.cornerstone.services.* to
> >>org.apache.avalon.pheonix.services.*
> >
> >I am not sure I like that. The Phoenix project is for the Application
> >Server/Kernel code. These services are not directly tied to kernel and we
> >could through them away and all would be fine and dandy in Phoenix land.
> > So I say we keep them where they are for the time being.
>
> OK then, can we think up a mechanism for an subset of cornerstone
> (service interfaces & exceptions) to be visible at some root level in a
> running phoenix machine? You are ruling out distribution, my other
> option leaned towards runtime publication..... I think I am losing you
> re the need....
How about something as simple as
$ cp cornerstone-services.jar $PHOENIX_HOME/lib
?
--
Cheers,
Pete
-----------------------------------------------
"You can't depend on your eyes when your
imagination is out of focus." -Mark Twain
-----------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: Centrally specified interfaces for Phoenix services
Posted by Paul Hammant <Pa...@yahoo.com>.
Peter,
>>Proposal : We move org.apache.avalon.cornerstone.services.* to
>>org.apache.avalon.pheonix.services.*
>>
>
>I am not sure I like that. The Phoenix project is for the Application
>Server/Kernel code. These services are not directly tied to kernel and we
>could through them away and all would be fine and dandy in Phoenix land. So I
>say we keep them where they are for the time being.
>
OK then, can we think up a mechanism for an subset of cornerstone
(service interfaces & exceptions) to be visible at some root level in a
running phoenix machine? You are ruling out distribution, my other
option leaned towards runtime publication..... I think I am losing you
re the need....
Regards,
- Paul H
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: Centrally specified interfaces for Phoenix services
Posted by Peter Donald <do...@apache.org>.
On Sun, 23 Sep 2001 08:36, Paul Hammant wrote:
> Proposal : We move org.apache.avalon.cornerstone.services.* to
> org.apache.avalon.pheonix.services.*
I am not sure I like that. The Phoenix project is for the Application
Server/Kernel code. These services are not directly tied to kernel and we
could through them away and all would be fine and dandy in Phoenix land. So I
say we keep them where they are for the time being.
--
Cheers,
Pete
*------------------------------------------------------*
| Hlade's Law: If you have a difficult task, give it |
| to a lazy person -- they will find an easier |
| way to do it. |
*------------------------------------------------------*
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: Centrally specified interfaces for Phoenix services
Posted by Paul Hammant <Pa...@yahoo.com>.
Peter,
>>1) Central definition of interfaces (and exceptions)
>>
>> Pros : Simple solution
>> Cons : Not version tolerant, though could have heretical version
>>numbers in package or class names (ref LayoutManager2). Only good for
>>regular server concepts (HTTPServer) as opposed to bespoke concepts
>>(company X's ABC Server)
>>
>>2) Promotion of interfaces (and exceptions). SAR file contains a jar of
>>interfaces that it implements, it could hand it to the parent component
>>(Phoenix) and Phoenix could make them available seperately, not
>>necessarily at promordial level. It's an RMI type concept, but RMI is
>>overkill for several reasons, not least of which is the ill-defined
>>RemoteException.
>>
>> Pros : Can tolerate different versions. Good for standards based
>>services as well as bespoke ones.
>> Cons : Difficult to implement
>>
>>Thoughts?
>>
>
>I like (1)
>
OK, that's cool. Often simple is best.
Proposal : We move org.apache.avalon.cornerstone.services.* to
org.apache.avalon.pheonix.services.*
This will pave the way for a central & default implementation of a
particular service. Assemblers can still choose to have a particular
impl bundled in their SAR file, but can (in the future) use a default
block impl for the service.
As we introduce other blocks for really large server components, we can
introduce services that express the features of those in a general way.
I'm thinking multiple implementations of HTTP and EJB server all being
interchangable given the same interfaces. As Peter says we should mark
some of the interfaces as "in progress" in some way.
Regards,
- Paul H
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org