just had an interesting IM with hiram. He essentially has implemented the proxy factory we were talking about. I think he is missing the client/server side of it but we can very simply add these.
Essentially it would revolve around a central
proxyFactory.createProxy(Interfaces, client-interceptors, client-configurations, server-interceptors, serverconfigurations targetMbean);
that returns a Dynamic Proxy, hooked up for remote/local calls with client and server side interceptors. If you are in one vm you can safely assume client=server and only configure one or the other. (meaning if one is null then don't configure transport it will be invm
In the case of hiram he has only one aspect of it (and he calls it aspect everywhere) but that construct is really what we need. I also think we should have the "MBean" in there, even though we are talking about a POJO.
I believe he has solid code for it and I am really interested in adding this to the base. I am not sure it is a JMX level construct (due to the pojo nature) but having the JMX base manage these configurations and associations between target and interceptors/configuration is the only sane way I can imagine to have these puppies manageable. I want visibility on that configuration for a given mbean (the generalized mbean againg being just a pojo or target). This is our generalized
The AOP framework of the future is staring us in the eye... we got it.
Apache Axis service locators do not enter the game with WS4EE. They are axis specific, hence not portable.
Is it true, that you hava a service interface, that extends javax.xml.rpc.Service and it has no package?
Most people use
I replaced the <service-interface> tag as <service-interface>javax.xml.rpc.Service</service-interface> in my web.xml but I am getting the same error.
Any other idea or suggestion will be helpful, as to how can I implement a servlet to access a remote web service.
A J2EE web componet client does not need stubs because it uses the service enpoint interface and the jaxrpc-mapping file of the service.
The wiki states "The web service client must have access to the same mapping information as described for the EJB service endpoint or the Java service endpoint. The jaxrpc mapping file must be part of the deployment, it cannot be obtained at runtime."
Which, for all practical purposes, means that a J2EE web service component client can only communicate with a J2EE service endpoint. If you are talking to a remote web service which is not a J2EE service endpoint (you don't have a jaxrpc-mapping file) then you must use another method of accessing the service. You can either use DII, or you can generate ordinary stubs with any web services toolkit. Be forewarned that AXIS client stubs are not portable. I would try using wscompile generated stubs from suns JWSDP to do this.
Thanks for ur reply. I will try to use wscompile tool and see what I can get.
This is in reply to ur question " Is it true, that you hava a service interface, that extends javax.xml.rpc.Service and it has no package? '
Yes, I do have a serveice interface that extends javax.xml.rpc.Service and it has a package name, which I have specified in my web.xml :
I am not able to figure out why the serlvet cannot locate and lookup the web service name defined in web.xml !!Any help !!