RE: Looking for example code
Thanks Glen I will try Metro again. I was getting some interesting errors from it that I could not figure out what they meant so that is why I moved to CXF. It helped me clean up some issues with the wsdl so maybe Metro will work now. Though I hate to say it but I would have rather stayed with CXF (It seems to be better designed than Metro (SUN needs to work more on its software) and more robust. Can you guys work more on interop scenarios please? Thanks again, Blair Jennings Senior Software Engineer A-Life Medical, Inc. 6195 Lusk Blvd., Suite 120 * San Diego, California 92121 Direct: 858.795.1716 Toll-Free: 888.224.6300 x1716 Fax: 858.812.0951 E-mail: [EMAIL PROTECTED] Web: www.alifemedical.com Streamlining the Code to Collection Process with Computerized Practice Management and Medical Coding Products and Services This message is for the sole use of the intended recipient and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender and destroy all copies of the original message. -Original Message- From: Glen Mazza [mailto:[EMAIL PROTECTED] Sent: Friday, March 14, 2008 7:02 PM To: cxf-user@incubator.apache.org Subject: Re: Looking for example code Because they work heavily with Microsoft concering interoperability, Metro is generally better documented[1][2] for accessing .NET services. If you cannot get CXF working, you may want to try a Metro client. Outside of authorization, the two stacks are rather easily swappable.[3] Glen [1] https://jax-ws.dev.java.net/guide/ [2] http://forums.java.net/jive/thread.jspa?messageID=264025 [3] http://www.jroller.com/gmazza/date/20070929 Am Freitag, den 14.03.2008, 08:29 -0700 schrieb Blair Jennings: Does anyone have an example of a .NET WCF web service with a CXF client. I am having some trouble getting this to work right. It needs to be able to use the wsHttpBinding from WCF with a username and password provided via a secure token. Thanks, Blair Jennings Senior Software Engineer A-Life Medical, Inc. 6195 Lusk Blvd., Suite 120 * San Diego, California 92121 Direct: 858.795.1716 Toll-Free: 888.224.6300 x1716 Fax: 858.812.0951 E-mail: [EMAIL PROTECTED] Web: www.alifemedical.com http://www.alifemedical.com Streamlining the Code to Collection Process with Computerized Practice Management and Medical Coding Products and Services This message is for the sole use of the intended recipient and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender and destroy all copies of the original message. This message is for the sole use of the intended recipient and may contain confidential and priviledged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender and destroy all copies of the original message. This message is for the sole use of the intended recipient and may contain confidential and priviledged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender and destroy all copies of the original message.
Re: WebServiceContext not injected in endpoint
Hi,
Can someone please share a full cxf xml where the JaxWsServerFactoryBean is
configured with a PerRequestFactory. I want to migrate my xfire web service
to cxf because I want to use the PerRequestFactory support.
Thanks in advance.
leewill wrote:
As a matter of fact, it works for even 2.0.4. I tried it yesterday, this
context got injected and I could get request back indirectly from it.
Well, I used Spring bean for all my test.
On 2/28/08 3:07 AM, Davide Gesino [EMAIL PROTECTED] wrote:
Hi Dan,
I have used this CXF 2.1 snapshot.
apache-cxf-2.1-incubator-20080228.032802-34.zip 28-Feb-2008 04:16 24M
I have tried this code, and actually the context is not injected. maybe I
am
doing something wrong.
With the SingletonFactory it happens the same. Maybe the fault is the way
I
create the service.
Anyway the creation policy works fine, with the PerSessionFactory I have a
brand new instance created for each request I get.
Here is the code:
Object implementor = new GreeterImpl();
String address = http://localhost:9000/SoapContext/SoapPort;;
org.apache.cxf.service.invoker.Factory factory = new
org.apache.cxf.service.invoker.PerRequestFactory(GreeterImpl.class);
org.apache.cxf.service.invoker.Factory factory = new
org.apache.cxf.service.invoker.SingletonFactory(GreeterImpl.class);
JAXWSMethodInvoker invoker = new JAXWSMethodInvoker(factory);
JaxWsServerFactoryBean factoryBean = new JaxWsServerFactoryBean();
factoryBean.setAddress(address);
factoryBean.setServiceBean(implementor);
factoryBean.setInvoker(invoker);
factoryBean.create();
@javax.jws.WebService(name = Greeter, serviceName = SOAPService,
portName = SoapPort, targetNamespace =
http://apache.org/hello_world_soap_http;, wsdlLocation =
hello_world.wsdl, endpointInterface =
org.apache.hello_world_soap_http.Greeter)
public class GreeterImpl implements Greeter {
@Resource
private WebServiceContext context;
public java.lang.String greetMe(java.lang.String requestType) {
LOG.info(Executing operation greetMe);
System.out.println(requestType);
if (context != null) {
System.out.println(context properly
injected);
}
else System.out.println(context properly is
null!!);
return hello my dear;
}
--
View this message in context:
http://www.nabble.com/WebServiceContext-not-injected-in-endpoint-tp15708465p15732342.html
Sent from the cxf-user mailing list archive at Nabble.com.
--
View this message in context:
http://www.nabble.com/WebServiceContext-not-injected-in-endpoint-tp15708465p16102008.html
Sent from the cxf-user mailing list archive at Nabble.com.
RE: Looking for example code
Sorry, I don't work much with Microsoft products. I've been on Ubuntu at home for over a year now and simply love it. Glen Am Montag, den 17.03.2008, 08:32 -0700 schrieb Blair Jennings: Thanks Glen I will try Metro again. I was getting some interesting errors from it that I could not figure out what they meant so that is why I moved to CXF. It helped me clean up some issues with the wsdl so maybe Metro will work now. Though I hate to say it but I would have rather stayed with CXF (It seems to be better designed than Metro (SUN needs to work more on its software) and more robust. Can you guys work more on interop scenarios please? Thanks again, Blair Jennings Senior Software Engineer A-Life Medical, Inc. 6195 Lusk Blvd., Suite 120 * San Diego, California 92121 Direct: 858.795.1716 Toll-Free: 888.224.6300 x1716 Fax: 858.812.0951 E-mail: [EMAIL PROTECTED] Web: www.alifemedical.com Streamlining the Code to Collection Process with Computerized Practice Management and Medical Coding Products and Services This message is for the sole use of the intended recipient and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender and destroy all copies of the original message. -Original Message- From: Glen Mazza [mailto:[EMAIL PROTECTED] Sent: Friday, March 14, 2008 7:02 PM To: cxf-user@incubator.apache.org Subject: Re: Looking for example code Because they work heavily with Microsoft concering interoperability, Metro is generally better documented[1][2] for accessing .NET services. If you cannot get CXF working, you may want to try a Metro client. Outside of authorization, the two stacks are rather easily swappable.[3] Glen [1] https://jax-ws.dev.java.net/guide/ [2] http://forums.java.net/jive/thread.jspa?messageID=264025 [3] http://www.jroller.com/gmazza/date/20070929 Am Freitag, den 14.03.2008, 08:29 -0700 schrieb Blair Jennings: Does anyone have an example of a .NET WCF web service with a CXF client. I am having some trouble getting this to work right. It needs to be able to use the wsHttpBinding from WCF with a username and password provided via a secure token. Thanks, Blair Jennings Senior Software Engineer A-Life Medical, Inc. 6195 Lusk Blvd., Suite 120 * San Diego, California 92121 Direct: 858.795.1716 Toll-Free: 888.224.6300 x1716 Fax: 858.812.0951 E-mail: [EMAIL PROTECTED] Web: www.alifemedical.com http://www.alifemedical.com Streamlining the Code to Collection Process with Computerized Practice Management and Medical Coding Products and Services This message is for the sole use of the intended recipient and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender and destroy all copies of the original message. This message is for the sole use of the intended recipient and may contain confidential and priviledged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender and destroy all copies of the original message. This message is for the sole use of the intended recipient and may contain confidential and priviledged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender and destroy all copies of the original message.
JSR-311 and JAXB and JSON
Hi,
I am trying to set up a JSR-311 REST like service and POSTing a string
of JSON to my /service/init/{id} address. The server seems to recognise
the address because catalina.out reports:
Mar 18, 2008 11:11:37 AM org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor
handleMessage
INFO: Found operation: init
The problem is that my init service function is never actually called. I
figure that something is going wrong with the JAXB? interpretation of my JSON
data. Is there some way to switch on debugging of this process to see
what is or isn't going on?
After the above server message my client connection eventually
just times out.
I am just assuming that consuming application/json works ...?
@POST
@Path(init/{clientId})
@ProduceMime(text/plain)
@ConsumeMime(application/json)
public String init(@UriParam(clientId) String id, @HttpContext
UriInfo
info, CrystalParameters cp) {
System.out.println(---received the sucker!--);
MultivaluedMap params = info.getQueryParameters();
// nothing happening here yet ...
String url = /ReflnCover/ + id + /basic;
return url;
}
Thanks
Doug
P.S. I'm using apache-cxf-2.1-incubator-20080306.021818-37.zip under
apache-tomcat-5.5.20 on kubuntu.
