You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apps-dev@avalon.apache.org by Peter Donald <pe...@apache.org> on 2002/10/21 14:04:25 UTC
[GUMP] Build Failure - jakarta-avalon-cornerstone
----------------------------------------------------
This email is autogenerated from the output from:
<http://jakarta.apache.org/builds/gump/2002-10-21/jakarta-avalon-cornerstone.html>
----------------------------------------------------
Buildfile: build.xml
Caught exception (org.apache.tools.ant.BuildException) while expanding tools.class.path: /home/rubys/jakarta/jakarta-site/lib not found.
Caught exception (org.apache.tools.ant.BuildException) while expanding test.class.path: /home/rubys/jakarta/jakarta-site/lib not found.
compile:
[mkdir] Created dir: /home/rubys/jakarta/jakarta-avalon-cornerstone/build/classes
[javac] Compiling 80 source files to /home/rubys/jakarta/jakarta-avalon-cornerstone/build/classes
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -deprecation for details.
metagenerate:
BUILD FAILED
file:/home/rubys/jakarta/jakarta-avalon-cornerstone/build.xml:192: taskdef class org.apache.avalon.phoenix.tools.metagenerate.MetaGenerateQdoxTask cannot be found
Total time: 10 seconds
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: BeanShell Kernel + Phoenix 4.0.3.
Posted by mati <ma...@ncdc.pl>.
> mati wrote:
> > Hi,
> >
> >
> > I have troubles lanuching Phoenix 4.0.3 with BeanShell Kernel. What I
saw is
> > that phoenix-engine.jar does not contain anymore the required kernel.
> >
> > I could copy old references from Phoenix 4.0.2 engine.jar but something
> > tells me this is not a good idea, although it should work.
> >
> > Any help appreciated.
>
> FYI: I noticed that the phoenix-bsh-commands.jar is not incluced in the
> lib directory of Phoenix 4.0.3 anymore. Since I don't use the BeanShell
> Kernel, I didn't worry about it.
>
> Ulrich
Yes I've spotted it too. But I added phoenix-bsh-commands.jar from 4.0.2
It does not matter for now since these are only commands (*.bsh) but the
whole BeanShell kernel is missing.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: BeanShell Kernel + Phoenix 4.0.3.
Posted by Ulrich Mayring <ul...@denic.de>.
mati wrote:
> Hi,
>
>
> I have troubles lanuching Phoenix 4.0.3 with BeanShell Kernel. What I saw is
> that phoenix-engine.jar does not contain anymore the required kernel.
>
> I could copy old references from Phoenix 4.0.2 engine.jar but something
> tells me this is not a good idea, although it should work.
>
> Any help appreciated.
FYI: I noticed that the phoenix-bsh-commands.jar is not incluced in the
lib directory of Phoenix 4.0.3 anymore. Since I don't use the BeanShell
Kernel, I didn't worry about it.
Ulrich
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: BeanShell Kernel + Phoenix 4.0.3.
Posted by Paul Hammant <pa...@yahoo.com>.
It has dissapeared from the 4.0.3 release by accident. It requires some things set in
ant.properties to make it included, and the download of the latest beanshell jar.
All my fault really. I don't use it for months at a time, so I did not notice it dropped off.
I'll automate something to make sure that 'dist' goes with it.
- Paul
--- mati <ma...@ncdc.pl> wrote: >
> ----- Original Message -----
> From: "mati" <ma...@ncdc.pl>
> To: "Avalon Developers List" <av...@jakarta.apache.org>
> Sent: Friday, December 27, 2002 4:24 PM
> Subject: BeanShell Kernel + Phoenix 4.0.3.
>
>
> > Hi,
> >
> >
> > I have troubles lanuching Phoenix 4.0.3 with BeanShell Kernel. What I saw
> is
> > that phoenix-engine.jar does not contain anymore the required kernel.
> >
> > I could copy old references from Phoenix 4.0.2 engine.jar but something
> > tells me this is not a good idea, although it should work.
> >
> > Any help appreciated.
> >
>
>
> I think I solved it and I even know why this has been changed. I've just
> made a jar only having inside beanshellkernel. I named it
> beanshell-kernel.jar and placed it inside /bin/lib
>
> Phoenix automatically loaded this jar as well as phoenix-engine.jar, which
> does not contain beanshell kernel.
>
> The reason this has been changed is that I think that as Paul Hammant said
> this is "hackers tool". When deployed some smart programmer or sb would
> really mess up. I dunno if this is it. it is just a guess.
>
>
>
>
>
>
>
>
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
>
__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: BeanShell Kernel + Phoenix 4.0.3.
Posted by mati <ma...@ncdc.pl>.
----- Original Message -----
From: "mati" <ma...@ncdc.pl>
To: "Avalon Developers List" <av...@jakarta.apache.org>
Sent: Friday, December 27, 2002 4:24 PM
Subject: BeanShell Kernel + Phoenix 4.0.3.
> Hi,
>
>
> I have troubles lanuching Phoenix 4.0.3 with BeanShell Kernel. What I saw
is
> that phoenix-engine.jar does not contain anymore the required kernel.
>
> I could copy old references from Phoenix 4.0.2 engine.jar but something
> tells me this is not a good idea, although it should work.
>
> Any help appreciated.
>
I think I solved it and I even know why this has been changed. I've just
made a jar only having inside beanshellkernel. I named it
beanshell-kernel.jar and placed it inside /bin/lib
Phoenix automatically loaded this jar as well as phoenix-engine.jar, which
does not contain beanshell kernel.
The reason this has been changed is that I think that as Paul Hammant said
this is "hackers tool". When deployed some smart programmer or sb would
really mess up. I dunno if this is it. it is just a guess.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
BeanShell Kernel + Phoenix 4.0.3.
Posted by mati <ma...@ncdc.pl>.
Hi,
I have troubles lanuching Phoenix 4.0.3 with BeanShell Kernel. What I saw is
that phoenix-engine.jar does not contain anymore the required kernel.
I could copy old references from Phoenix 4.0.2 engine.jar but something
tells me this is not a good idea, although it should work.
Any help appreciated.
Mateusz Szczap
mati@ncdc.pl
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Cornerstone addition and patch
Posted by Mauro Talevi <ma...@aquilonia.org>.
Paul Hammant wrote:
> Applied, thanks. Not sure about the 'throws (derivative of)
> RuntimeException' in one of the block method signatures. Will think
> about it some more.
I've modified the event Register to throw s a checked exception
Also the root event type is now configurable.
> Is there any chance there could be an example of use that we could add
> to the jakarta-avalon-apps/demo package? Maybe this is not a new
> demo, but a value added modifaction to an old one.. maybe not.
I've written an eventdemo for apps/demo. Still very basic - simply make
two blocks communicate via an event.
Things to come in it:
- have it notify of the scheduled event
- have it working in between distributed jvms
Patches for both are attached.
Regards, Mauro
Re: Cornerstone addition and patch
Posted by Mauro Talevi <ma...@aquilonia.org>.
Paul Hammant wrote:
> Applied, thanks. Not sure about the 'throws (derivative of)
> RuntimeException' in one of the block method signatures. Will think
> about it some more.
I've modified the event Register to throw s a checked exception
Also the root event type is now configurable.
> Is there any chance there could be an example of use that we could add
> to the jakarta-avalon-apps/demo package? Maybe this is not a new
> demo, but a value added modifaction to an old one.. maybe not.
I've written an eventdemo for apps/demo. Still very basic - simply make
two blocks communicate via an event.
Things to come in it:
- have it notify of the scheduled event
- have it working in between distributed jvms
Patches for both are attached.
Regards, Mauro
Re: Cornerstone addition and patch
Posted by Mauro Talevi <ma...@aquilonia.org>.
Paul Hammant wrote:
> Applied, thanks. Not sure about the 'throws (derivative of)
> RuntimeException' in one of the block method signatures. Will think
> about it some more.
I've modified the event Register to throw s a checked exception
Also the root event type is now configurable.
> Is there any chance there could be an example of use that we could add
> to the jakarta-avalon-apps/demo package? Maybe this is not a new
> demo, but a value added modifaction to an old one.. maybe not.
I've written an eventdemo for apps/demo. Still very basic - simply make
two blocks communicate via an event.
Things to come in it:
- have it notify of the scheduled event
- have it working in between distributed jvms
Patches for both are attached.
Regards, Mauro
Re: Cornerstone addition and patch
Posted by Mauro Talevi <ma...@aquilonia.org>.
Paul Hammant wrote:
> Mauro,
>
> Applied, thanks. Not sure about the 'throws (derivative of)
> RuntimeException' in one of the block method signatures. Will think
> about it some more.
The main reason it's there is that was suggested in the event notifier
pattern paper and I just went along with it - treating it as an
implementation detail which could be modified later.
The exception is not thrown if one registers an event which is a
subclass or subtype of the root event
(which should really be configured or you need to slightly modify to
present code to have the full Event class name as the rootEventType)
and that is the most common case.
But I do recognise the need to make the interface more solid and generic.
The preferred alternative is make the Register methods throw a checked
exception. One could also ignore the subscribtion if the
event is not a subclass of the root event but I do not like that.
I'll modify the interface to throw a checked exception and send in a patch.
> Is there any chance there could be an example of use that we could add
> to the jakarta-avalon-apps/demo package? Maybe this is not a new
> demo, but a value added modifaction to an old one.. maybe not.
I was thinking of writing one - I think it's probably best to have a new
demo package, say eventhelloworldserver
because I would like to have two different blocks "talk" to each other
via events.
I also want to write a little demo that allows the callback to remote
non phoenix blocks, eg a swing or servlet client, which is the real power
of the event notifier pattern
Cheers, Mauro
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Cornerstone addition and patch
Posted by Paul Hammant <Pa...@yahoo.com>.
Mauro,
Applied, thanks. Not sure about the 'throws (derivative of)
RuntimeException' in one of the block method signatures. Will think
about it some more.
Is there any chance there could be an example of use that we could add
to the jakarta-avalon-apps/demo package? Maybe this is not a new demo,
but a value added modifaction to an old one.. maybe not.
Regards,
- Paul
> I attach a new cornerstone service/block for event notification among
> services.
> It is based on the Event Notifier pattern by Gupta et al. (Java
> Report, Vol. 3, No. 7, July 1998, 19-36).
> It allows services to publish and subscribe to events of interest and
> be notified of them.
> It is useful in that it decouples greatly the services in big phoenix
> apps.
>
> At present, the implementation is for local interfaces although I've
> used it successfully in a distributed setting
> (via RMI). All is needed to be make the EventManager, Publisher and
> Register Remote interfaces.
> But perhaps one might want to implement other distributed method
> invocation, in particular AltRMI. It can be improved in several ways
> but a present I wanted to gauge if there was interest in it.
>
> I also attach a patch to extend the RMIfication service, adding the
> methods export() and unexport().
> There sometimes is the need to export a Remote interface without
> "publishing" it (ie binding it with a name).
> Eg, when a service (whose interface has been RMIfied and published)
> exposes other remote interfaces
> which are only accessible via the service interface (but not direcly
> via the RMI registry).
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Cornerstone addition and patch
Posted by Peter Royal <pr...@apache.org>.
On Monday, November 4, 2002, at 08:21 PM, Mauro Talevi wrote:
> At present, the implementation is for local interfaces although I've
> used it successfully in a distributed setting
> (via RMI). All is needed to be make the EventManager, Publisher and
> Register Remote interfaces.
> But perhaps one might want to implement other distributed method
> invocation, in particular AltRMI. It can be improved in several ways
> but a present I wanted to gauge if there was interest in it.
awesome... off to have a looksee.
-pete
--
peter royal -> proyal@apache.org
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Cornerstone addition and patch
Posted by Mauro Talevi <ma...@aquilonia.org>.
Hi,
I attach a new cornerstone service/block for event notification among
services.
It is based on the Event Notifier pattern by Gupta et al. (Java Report,
Vol. 3, No. 7, July 1998, 19-36).
It allows services to publish and subscribe to events of interest and be
notified of them.
It is useful in that it decouples greatly the services in big phoenix apps.
At present, the implementation is for local interfaces although I've
used it successfully in a distributed setting
(via RMI). All is needed to be make the EventManager, Publisher and
Register Remote interfaces.
But perhaps one might want to implement other distributed method
invocation, in particular AltRMI.
It can be improved in several ways but a present I wanted to gauge if
there was interest in it.
I also attach a patch to extend the RMIfication service, adding the
methods export() and unexport().
There sometimes is the need to export a Remote interface without
"publishing" it (ie binding it with a name).
Eg, when a service (whose interface has been RMIfied and published)
exposes other remote interfaces
which are only accessible via the service interface (but not direcly via
the RMI registry).
Cheers,
Mauro