skipping the schema processing in method InvokeFactoryServiceConstructor.constructCoreServiceImplementation(), when schema is null, but there
exists a test case (TestInvokeFactoryServiceConstructor), that explicitly tests
for this case.
You can use the parameters-occurs attribute to overcome this problem:
<service-point id="HibernateSessionFactory" interface="org.apache.hivemind.ServiceImplementationFactory" parameters-occurs="0..n">
Achim Huegen
Am Sat, 2 Oct 2004 13:07:46 -0400 schrieb James Carman <[EMAIL PROTECTED]>:
I have created a custom service implementation factory and I didn't include
a parameters schema for it..
<service-point id="HibernateSessionFactory" interface="org.apache.hivemind.ServiceImplementationFactory">
<invoke-factory service-id="hivemind.BuilderFactory">
<construct
class="example.hibernate.impl.HibernateSessionFactory"
initialize-method="init"/>
</invoke-factory>
</service-point>
When the registry creates my instance, I get the following error message.
[EMAIL PROTECTED]:49:12 ERROR (hivemind.article.HibernateSession) - Error at file:/
C:/Java/libraries/jakarta-tomcat-4.1.30/webapps/hivemind-article/WEB-INF/cla sses
/META-INF/hivemodule.xml, line 66, column 76: Parameters to service implementati
on factory HibernateSessionFactory contains no contributions but expects exactly
one contribution.
I see in the code that the default value for parameterOccurs is REQUIRED,
but what if I don't HAVE any parameters schema defined? Shouldn't it skip
the check if there is no parameters schema?
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
