|
Dan, (Sorry for the confusion, but the list server kept kicking
my messages out stating there were to large.) And to follow-up on my follow-up … of my
previous proxy-to-hibernate mapping problem... 2)After applying the above changes to my ServiceBean
definition I wound up with: <bean
id="XEchoServiceBean"
class="com.hp.ipgit.ssa.echoservice.remoting.xfire.EchoServiceBean" > <property
name="properties"> <map>
<entry>
<key><value>com.hp.ipgit.ssa.echoservice.model.IEcho.implementation</value></key>
<value>com.hp.ipgit.ssa.echoservice.model.Echo</value>
</entry> </map> </property> <property
name="serviceBean"> <ref
bean="EchoWebService"/> </property> <property
name="serviceClass">
<value>com.hp.ipgit.ssa.echoservice.remoting.xfire.IEchoWebService</value> </property> <property
name="inHandlers"> <list>
<value>addressingHandler</value> </list> </property> </bean> As you can see, my ServiceBean
"properties" are now set to use my implementation class
"com.hp.ipgit.ssa.echoservice.model.Echo" when resolving the proxy. However, I'm still getting the pesky Hibernate
Mapping Exception "Unknown entity: $Proxy14" (see below) when I
attempt to persist any IEcho objects that have been prox-ified. It would appear that my ServiceBean is still not
configured correctly. Is there any way to tell if the ServiceBean actually applied
my "properties"? 2006-04-21 12:13:01,862 DEBUG
[org.codehaus.xfire.transport.DefaultEndpoint] - Received message to
/ssa-echo-service/EchoServiceSoap11.xfireservice 2006-04-21 12:13:01,863 DEBUG
[org.codehaus.xfire.handler.HandlerPipeline] - Invoking handler
org.codehaus.xfire.soap.handler.ReadHeadersHandler in phase parse 2006-04-21 12:13:01,863 DEBUG
[org.codehaus.xfire.handler.HandlerPipeline] - Invoking handler
org.codehaus.xfire.handler.LocateBindingHandler in phase dispatch 2006-04-21 12:13:01,863 DEBUG
[org.codehaus.xfire.handler.HandlerPipeline] - Invoking handler
org.codehaus.xfire.soap.handler.SoapBodyHandler in phase dispatch 2006-04-21 12:13:01,864 DEBUG
[org.codehaus.xfire.handler.HandlerPipeline] - Invoking handler
org.codehaus.xfire.soap.handler.SoapActionInHandler in phase dispatch 2006-04-21 12:13:01,864 DEBUG
[org.codehaus.xfire.handler.HandlerPipeline] - Invoking handler
org.codehaus.xfire.handler.DispatchServiceHandler in phase dispatch 2006-04-21 12:13:01,864 DEBUG [org.codehaus.xfire.handler.HandlerPipeline]
- Invoking handler org.codehaus.xfire.soap.handler.ValidateHeadersHandler in
phase pre-invok e 2006-04-21 12:13:01,864 DEBUG
[org.codehaus.xfire.handler.HandlerPipeline] - Invoking handler
org.codehaus.xfire.service.binding.ServiceInvocationHandler in phase serv ice 2006-04-21 12:13:01,876 DEBUG
[org.codehaus.xfire.handler.DefaultFaultHandler] - Fault occurred! org.codehaus.xfire.fault.XFireFault: Unknown entity:
$Proxy14; nested exception is org.hibernate.MappingException: Unknown entity:
$Proxy14 at
org.codehaus.xfire.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:68) at
org.codehaus.xfire.service.binding.ServiceInvocationHandler.sendMessage(ServiceInvocationHandler.java:260) at
org.codehaus.xfire.service.binding.ServiceInvocationHandler$1.run(ServiceInvocationHandler.java:85) at
org.codehaus.xfire.service.binding.ServiceInvocationHandler.execute(ServiceInvocationHandler.java:132)
|
