On Thursday, March 28, 2002, at 07:36 PM, [EMAIL PROTECTED] wrote: > dobbs 02/03/28 18:36:50 > > Added: src/test/org/apache/fulcrum/xmlrpc Fulcrum.properties > XmlRpcTest.java > Log: > Testcase for xmlrpc. > > Currently demonstrates that Fulcrum.class does not stand on its own at > the moment. Reverse the comments in the catch() block in > testInitializeFulcrum to see the test fail (unless I fix Fulcrum.class > before you get to it. 8^)
Thought I should elaborate a bit for the list. Those of you on IRC have already heard this. 8^) Background: I'm trying to get Fulcrum, and in particular Fulcrum's XMLRPC working with a Turbine 2.2 application. And it hasn't been easy. It all started here: TurbineXmlRpc.getService().executeRpc(...) TurbineXmlRpc, following the convention for the Fulcrum facade classes, calls TurbineServices.getInstance().getService() in order to call methods on the service. But Turbine 2.2 does not initialize TurbineServices, it initializes Fulcrum (the class, not the project). And Fulcrum does not offer anything equivalent to TurbineServices.getInstance() for the facade classes to use instead. A short-term fix would be to create a Component for TurbineServices and configure Turbine to load that instead of Fulcrum. But I think The Right Thing is to fix Fulcrum so that it is an adequate replacement for TurbineServices, and change the facade classes accordingly. -Eric -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
