I didn't look at the code you mentioned, but I did pull the repo today and the problem seems to have gone away. I made the change to BigBank using an EP name of "AccountServiceEP" and it ran fine.
Thanks, maybe I'll try one more time as a sanity check tomorrow and then close out the JIRA. On 4/26/06, Jim Marino (JIRA) <[email protected]> wrote: > > [ > http://issues.apache.org/jira/browse/TUSCANY-235?page=comments#action_12376607] > > Jim Marino commented on TUSCANY-235: > ------------------------------------ > > I haven't had time to reproduce this but looking at the latest repo > revision it appears as if the target name on the SourceWireFactory > (retrieved through getConfiguration() ) has the incorrect service name. The > target component name is valid since the target context is returned (there > is a null check for that) but the service name appears to be set to the > entry point name (cf. line 584 AbstractComponentContext). > > I'm going to be out tomorrow so can someone please look at this? Either > the model is not being loaded properly, it is not setting correct > relationships, or the runtime builder is using the model erroneously. In > the latter case, DefaultWireFactoryService.createSourceFactory(..) is the > palce to look to see if the model is being used improperly. This seems kind > of strange since we do have unit tests where the ep is named differently > than the target service. > > It also may be good to do a sanity check against the latest version since > a lot of changes were introduced into core lately. > > Jim > > > > > EntryPoint name must match wired-to Service name > > ------------------------------------------------ > > > > Key: TUSCANY-235 > > URL: http://issues.apache.org/jira/browse/TUSCANY-235 > > Project: Tuscany > > Type: Bug > > > Components: Java SCA Core > > Environment: Ran after pulling SVN contents April 17th in Tomcat on > Windows > > Reporter: Scott Kurz > > Priority: Minor > > > > > With a WS binding you currently need to match the EntryPoint name with > the name of the Service it is wired to via the <references> tag. > > So, for example, in the HelloWorld WS sample's sca.module file, you > have: > > <entryPoint name="HelloWorldService"> > > <interface.wsdl interface=" > http://helloworldaxis.samples.tuscany.apache.org#HelloWorldServiceImpl"/> > > <binding.ws port=" > http://helloworldaxis.samples.tuscany.apache.org#helloworld"/> > > > <reference>HelloWorldServiceComponent/HelloWorldService</reference> > > </entryPoint> > > You should be able to rename the entryPoint as: > > <entryPoint name="HelloWorldServiceEP"> > > but be able to keep the reference as: > > <reference>HelloWorldServiceComponent/HelloWorldService</reference> > > But when I tried this recently in Tomcat I had this problem. > > SEVERE: Error deploying web application archive helloworldws.war > > org.apache.tuscany.core.context.ContextInitException: No proxy factory > found for service [HelloWorldServiceEP] > > Context stack trace: [tuscany.root > ][/helloworldws][/helloworldws][HelloWorldServiceEP][HelloWorldServiceComponent] > > at > org.apache.tuscany.core.context.impl.AbstractCompositeContext.wireSource( > AbstractCompositeContext.java:568) > > at > org.apache.tuscany.core.context.impl.AbstractCompositeContext.start( > AbstractCompositeContext.java:149) > > at > org.apache.tuscany.core.context.scope.CompositeScopeContext.registerFactory > (CompositeScopeContext.java:95) > > at > org.apache.tuscany.core.context.impl.AbstractCompositeContext.registerConfiguration > (AbstractCompositeContext.java:457) > > at > org.apache.tuscany.core.context.impl.AbstractCompositeContext.registerModelObject > (AbstractCompositeContext.java:404) > > at org.apache.tuscany.tomcat.TuscanyContextListener.loadContext( > TuscanyContextListener.java:133) > > at org.apache.tuscany.tomcat.TuscanyContextListener.startContext( > TuscanyContextListener.java:85) > > at org.apache.tuscany.tomcat.TuscanyContextListener.lifecycleEvent > (TuscanyContextListener.java:71) > > at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent( > LifecycleSupport.java:119) > > at org.apache.catalina.core.StandardContext.start( > StandardContext.java:4119) > > at org.apache.catalina.core.ContainerBase.addChildInternal( > ContainerBase.java:759) > > at org.apache.catalina.core.ContainerBase.addChild( > ContainerBase.java:739) > > at org.apache.catalina.core.StandardHost.addChild( > StandardHost.java:524) > > at org.apache.tuscany.tomcat.TuscanyHost.addChild(TuscanyHost.java > :117) > > at org.apache.catalina.startup.HostConfig.deployWAR( > HostConfig.java:809) > > at org.apache.catalina.startup.HostConfig.deployWARs( > HostConfig.java:698) > > at org.apache.catalina.startup.HostConfig.deployApps( > HostConfig.java:472) > > at org.apache.catalina.startup.HostConfig.start(HostConfig.java > :1122) > > at org.apache.catalina.startup.HostConfig.lifecycleEvent( > HostConfig.java:310) > > at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent( > LifecycleSupport.java:119) > > at org.apache.catalina.core.ContainerBase.start(ContainerBase.java > :1021) > > at org.apache.catalina.core.StandardHost.start(StandardHost.java > :718) > > at org.apache.tuscany.tomcat.TuscanyHost.start(TuscanyHost.java > :60) > > at org.apache.catalina.core.ContainerBase.start(ContainerBase.java > :1013) > > at org.apache.catalina.core.StandardEngine.start( > StandardEngine.java:442) > > at org.apache.catalina.core.StandardService.start( > StandardService.java:450) > > at org.apache.catalina.core.StandardServer.start( > StandardServer.java:709) > > at org.apache.catalina.startup.Catalina.start(Catalina.java:551) > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > at sun.reflect.NativeMethodAccessorImpl.invoke( > NativeMethodAccessorImpl.java:64) > > at sun.reflect.DelegatingMethodAccessorImpl.invoke( > DelegatingMethodAccessorImpl.java:43) > > at java.lang.reflect.Method.invoke(Method.java:615) > > at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:294) > > at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:432) > > -- > This message is automatically generated by JIRA. > - > If you think it was sent incorrectly contact one of the administrators: > http://issues.apache.org/jira/secure/Administrators.jspa > - > For more information on JIRA, see: > http://www.atlassian.com/software/jira > >
