Thanks for the reply Stephen.
The excalibur-monitor jar indeed does not come "shipped" with any .xinfo file in it (and I would guess most excalibur components do not). I updated the ActiveMonitor and PassiveMonitor source with the complete tags (see diff - if you want the source, let me know).
I did unravel the excalibur-monitor jar and put the xinfo files in, and it solved my current problem. Is this the only way to get the xinfo to the kernel?
Also, is there a reason why the excalibur jars don't build with the xinfo files?
Thanks, R-
Index: ActiveMonitor.java
===================================================================
RCS file: /home/cvspublic/avalon-excalibur/monitor/src/java/org/apache/avalon/excalibur/monitor/ActiveMonitor.java,v
retrieving revision 1.20
diff -r1.20 ActiveMonitor.java
77,78c77,78
< * @avalon.component
< * @avalon.service type=org.apache.avalon.excalibur.monitor.Monitor
---
> * @avalon.component name="active-monitor" lifestyle="singleton"
> * @avalon.service type="org.apache.avalon.excalibur.monitor.Monitor" version="1.0"
Index: PassiveMonitor.java
===================================================================
RCS file: /home/cvspublic/avalon-excalibur/monitor/src/java/org/apache/avalon/excalibur/monitor/PassiveMonitor.java,v
retrieving revision 1.16
diff -r1.16 PassiveMonitor.java
75,76c75,76
< * @avalon.component
< * @avalon.service type=org.apache.avalon.excalibur.monitor.Monitor
---
> * @avalon.component name="passive-monitor" lifestyle="singleton"
> * @avalon.service type="org.apache.avalon.excalibur.monitor.Monitor" version="1.0"
At 06:56 AM 9/24/2003 +0200, Stephen McConnell wrote:
Robb Penoyer wrote:
I have what I hope is an easy one. I am working on getting an ActiveMonitor from Excalibur up in Merlin. From what I have read on the Stephen/Alex/Tim Bennett exchange earlier this month, I can reuse the .xinfo file I generated with ant and the avalon meta tags.
Hi Rob:
The avalon meta tags in the monitor package are the subset of tags used by Fortress prior to the finalization of the avalon-meta package. The sources in monitor need to be updated to the current tag spec and xinfo content regenerated using the task defintion in avalon-meta-tools-1.1.jar (or the avalon-meta-plugin-1.1.jar if your building with maven).
oh, yeah a question: for now I am using the maven merlin:simulate to test, however it blows the TypeUnknownException. Is the a way to present the .xinfo file without unwrapping the excalibur jar and putting it in there?
If there is a valid avalon-meta complianty xinfo in the monitor jar file (which is unlikely) then merlin will locate it automatically.
Stephen.
--
Stephen J. McConnell mailto:[EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
