In Phoenix an xinfo is collocated with the component implementation
class - MyComponentInplementation.xinfo sits along side
MyComponentInplementation.class.  Phoneix does not support metainfo
for services.

You should have one .xinfo per component implementation.  Its the
.xinfo file that tells Phoenix what the components needs.

Stephen.



Saurabh Manohar wrote:

Hi Pete,
Thanks for the tip I  updated nmy files as above. Now it is throwing the
foll error:

org.apache.excalibur.containerkit.lifecycle.LifecycleException: Component
named "myClass" failed to pass through the Creation stage. (Reason:
java.lang.InstantiationException: com.myPackage.myInterface).

I think the error is because myInterface is an interface. so it can't be
instantiated. Now here is where I'm not clear.
To the best of my knowledge :
A block  has to be an instantiable class.
A service has to be an interface.
To offer the service, the block has to implement the interface.
Every block, interface has to have an .xinfo file.
Now If i put two .xinfo files in my com.mypackage, Phoenix doesn't start as
it doesn't file the myInterface.xinfo file (it is there but phoenix doesn't
find it.)
When I run the sar created eith only one .xinfo file (myInterface.xinfo), i
get the above error.
So should I have ONLY one .xinfo file per jar?

Thanks,
Saurabh

----- Original Message -----
From: "peter royal" <[EMAIL PROTECTED]>
To: "Avalon framework users" <[EMAIL PROTECTED]>
Sent: Thursday, November 20, 2003 7:03 AM
Subject: Re: Configuration error




On Nov 19, 2003, at 11:41 AM, Saurabh Manohar wrote:


Here's the code. all the xml files. I have included the code for the
interface also, which does nothing much. But i was lookin to configure
the
interface as a service and the myClass as a block. Also where do I add
the
dependencies, in the .xinfo file or the assembly file.


assembly.xml should contain:

<assembly>
<block class="com.mindflow.runmode.myBlock" name="myInterface" />
</assembly>

rather than myInterface

from your description, that may be the only problem..

the interfaces that MyBlock implements only become an issue when you
add another block that depends on MyInterface..

-pete


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



------------------------------------------------------------------------

<?xml version="1.0"?>

<assembly>
<block class="com.mindflow.runmode.jRunInterface" name="jRunmode" />
</assembly>


------------------------------------------------------------------------

<?xml version="1.0"?>

<config>
<!-- this section is specific to the the MyFxConversion Block -->
<myClass>
<port>5656</port>
</myClass>
</config>


------------------------------------------------------------------------

<?xml version="1.0"?>

<environment>
        <logs>
                <category name="" target="default" priority="DEBUG" />
                <log-target name="default" location="/logs/avalon-demo.log" />
        </logs>
        <policy>
                <grant code-base="file:${app.home}${/}SAR-INF${/}lib${/}*">
                        <permission class="java.security.AllPermission" />
                </grant>
        </policy>
</environment>



------------------------------------------------------------------------

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


--


Stephen J. McConnell
mailto:[EMAIL PROTECTED]

|------------------------------------------------|
| Magic by Merlin                                |
| Production by Avalon                           |
|                                                |
| http://avalon.apache.org/merlin                |
| http://dpml.net/                               |
|------------------------------------------------|





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to