Re: http://schemas.xmlsoap.org/soap/http

Hi Marc, For setup the CXF servlet in a junit test, you can get more details from trunk/systests/src/test/java/org/apache/cxf/systest/servlet/SpringServletTest.java and it's superclass trunk/systests/src/test/java/org/apache/cxf/systest/servlet/AbstractServletTest.java Best Regards Freeman Mar

Re: http://schemas.xmlsoap.org/soap/http

Hm, I have the Jetty Module (cxf-rt-transports-http-jetty) in my classpath and it doesn't work. How can I set up the CXF Servlet in a JUnit Test? I want to set up a web service in a "before test" method, test my service and shut the web service down. Marc Original-Nachricht ---

Re: Re:

How do I configure in my applicationContext.xml to use Aegis? Is there anywhere an example? Regards Marc Original-Nachricht Datum: Thu, 12 Jul 2007 13:35:58 -0600 Von: "Dan Diephouse" <[EMAIL PROTECTED]> An: cxf-user@incubator.apache.org Betreff: Re: > JAXB can't handle inter

Re: Exposing methods

Hi, I just dug the code, here is the code in the JaxWsServiceConfiguration to tell which method is the WebMethod. @Override public Boolean isOperation(Method method) { Method origMethod = method; method = getDeclaredMethod(method); if (method.getReturnType().equals(Fut

Re: Exposing methods

Yes . It's the normal behavior. The runtime will reflect every method in impl class and expose it unless the method is annotated with exclude WebMethod . CXF also can support publishing a service with a pojo class without implementing any interface : @WebService public class UserWebServiceImpl

Re: Unable to find resolve annotations

You can take the http-binding pom.xml as a example: http://willem.bokeland.com/svn.apache.org/repos/asf/incubator/cxf/trunk/rt/bindings/http/pom.xml Willem. Brad O'Hearne wrote: Willem, Thanks! I have one more question. If I am using REST ful annotations to create an HTTP service, and I don

RE: Exposing methods

Hi Julio, if exclude=true did work, this proved that your endpointInterface class didnt get loaded by CXF. The logic behind the scene is that CXF will try to load endpointInterface class using @WebService(endpointInterface ="") annotation, if it successfully gets the interface loaded, only metho

Re: Exposing methods

Hi Jim, Thanks I found that property for the @WebMethod annotation too and it works fine. But is this a normal behavior to expose everything in the implementor, I thought it would only expose the methods on my interface. On Jul 12, 2007, at 9:05 PM, Jim Ma wrote: Hi Julio, I think you ca

Re: Unable to find resolve annotations

Willem, Thanks! I have one more question. If I am using REST ful annotations to create an HTTP service, and I don't need to make use of SOAP or any wsdl support (i.e., I want XML over straight HTTP only), which dependencies do I need? Based upon the dependency names, I am suspecting that I do

Re: Unable to find resolve annotations

Hi Brad, You need to add the jra in you dependency org.codehaus.jra jra 1.0-alpha-3 Cheers, Willem Brad O'Hearne wrote: Hello -- I am trying to use RESTful annotations to create an HTTP service, and build using Maven 2. I have followed the inst

Unable to find resolve annotations

Hello -- I am trying to use RESTful annotations to create an HTTP service, and build using Maven 2. I have followed the instructions in the documentation for adding the appropriate dependencies, repositories, and plugin repositories. However, my service class that I'm trying to annotate using t

Re: Exposing methods

Hi Julio, I think you can add @WebMethod(exclude=true) for the setter method. @WebMethod (exclude=true) setUserManager(UserManager userManager) Cheers Jim Julio Arias wrote: The dependencies setters from my service impl are getting expose in the WSDL even though I'm specifying the e

RE: Exposing methods

Hi Julio, this should work. But sometimes it can happen if the CXF runtime can not load the endpoint class specified by endpointInterface = "com.rbx.test.webservices.UserWebService", in that case, CXF will use impl class (i.e., the UserWebServiceImpl ) to build a service model. And if this do

Re: Code generation on Eclipse 3.2 STP 0.6

Hi, I see the problem, the problem is caused by that you have a service named "Teste" and also you have a portType named "Teste" According to the jaxws spec, we have a way to solve the naming collision, in command line tools we support the naming collision, you will get the following artifact

Re: Exposing methods

Hi Julio, I am not sure that I get you point. Do you mean that you don't want to specify the endpoint interface in the implementor in the annotation ? Even the SEI ( Service Endpoint Interface) is generated by wsdl , you still need to specify it in the implementor class. Your Endpoint Sprin

Re: javascript clients?

Hi, Now it use "rhino lib" to call java JaxWS frontend. Thanks Jeff - Original Message - From: "Benson Margulies" <[EMAIL PROTECTED]> To: Sent: Friday, July 13, 2007 9:51 AM Subject: javascript clients? Reading the doc on Javascript service implementations, I'm led to wonder if you h

javascript clients?

Reading the doc on Javascript service implementations, I'm led to wonder if you have got a code generator to emit Javascript clients?

Re: Code generation on Eclipse 3.2 STP 0.6

Maybe this two links will help you. They tell you a traditional way that how to use CXF to build a wsdl first application. http://cwiki.apache.org/CXF20DOC/developing-a-consumer.html http://cwiki.apache.org/CXF20DOC/developing-a-service.html Cheers, Willem. Josir Gomes wrote: Thanks for rep

Re: Maven java2wsdl plugin error with jaxws

Looks like maven does not load the jaxws/simpl/soap jars from the classpath, you can turn on the flag to print the classpath maven used to load the jars. Another easiest way to load the jars, is build your own code-gen plugin by yourself, just add the dependencies(jaxws/simple/soap) in the

RE: CXF-781

Dan, I attached a repro to the issue. It's a set of files that drop into org.apache.cxf.aegis.test.java5. I didn't make use of the base class for the test, but if you keep this as a unit test I'm sure that won't be hard. My original code fails with the snapshot. I only tried the test case in the

RE: CXF-781

No joy in current snapshot. I will try to concoct a test case. > -Original Message- > From: Dan Diephouse [mailto:[EMAIL PROTECTED] > Sent: Thursday, July 12, 2007 3:45 PM > To: cxf-user@incubator.apache.org > Subject: Re: CXF-781 > > Would you be willing to try one of the latest snapshot

Exposing methods

The dependencies setters from my service impl are getting expose in the WSDL even though I'm specifying the endpoint interface in the implementor. How can I hide this methods? I have the following code and config: + UserWebService.java @WebService(name = "UserService") public interface User

Re: Trouble with creating RESTful Service deployed to Jetty - need help!

LOL, know just what you mean. ;-) Actually, while I was tinkering with it here I figured that out too. I realized that my URL should have had clients (plural) in it instead of client (singular). After I corrected that, I started getting a NullPointerException: INFO: URIParameterIntercepto

RE: CXF-781

Can do. > -Original Message- > From: Dan Diephouse [mailto:[EMAIL PROTECTED] > Sent: Thursday, July 12, 2007 3:45 PM > To: cxf-user@incubator.apache.org > Subject: Re: CXF-781 > > Would you be willing to try one of the latest snapshots? I think this was > fixed post 2.0... > > http://in

Re: CXF-781

Would you be willing to try one of the latest snapshots? I think this was fixed post 2.0... http://incubator.apache.org/cxf/download.html If it still doesn't work, report back and I can dive into it. I've been meaning to clean up that code this week anyway. :-) Thanks! - Dan On 7/12/07, Benson

Re: Generated client to connect to a https ws

Actually if you're using the client API, this is probably easier: YourService s = new YourService() ServiceInterface client = s.getYourServiceSoapHttpPort Client c = ClientProxy.getClient(client); HTTPConduit conduit = (HTTPConduit) c.getConduit() TLSClientParameters tlsParams = new TLSClientPar

Re:

JAXB can't handle interfaces. What you want to do is configure your service to use the Aegis databinding library from XFire instead: http://cwiki.apache.org/CXF20DOC/aegis-databinding.html Aegis will handle just about any datatypes you throw at it. Hope that helps, - Dan On 7/12/07, Marc Baumga

Re: http://schemas.xmlsoap.org/soap/http

That is a fine way to start Spring. What does your applicationContext.xmllook like? BTW, this tutorial may be helpful to you: http://cwiki.apache.org/CXF20DOC/writing-a-service-with-spring.html On 7/12/07, Marc Baumgartner <[EMAIL PROTECTED]> wrote: Hm, I get the exception when starting the

Re: Trouble with creating RESTful Service deployed to Jetty - need help!

Wow, I think I'm losing it - I forgot how my code works. It turns out (as the logs suggest) that the correct URL is: http://localhost:8080/iat-services/ws/clients/10 (clientS not client) Cheers, - Dan On 7/12/07, Jason Mihalick <[EMAIL PROTECTED

Re: Code generation on Eclipse 3.2 STP 0.6

Thanks for replying Dan. I didn't want to bother the developers before I am sure that this is really a bug. I've already looked into the jira database and didn't find any similar issue. Could you list what are the steps did you take to generate the source code from the WSDL? I put the gene

Re: Trouble with creating RESTful Service deployed to Jetty - need help!

I just realized that I missed this in my output previously. The Mapping messages you mentioned are below. [INFO] Starting jetty 6.1H.4-beta ... 2007-07-12 12:31:19.634::INFO: jetty-6.1H.4-beta 2007-07-12 12:31:19.840::INFO: No Transaction manager found - if your webapp requires one, please c

RE: Endpoints: JAX-WS vs. WCF

Sounds like to me the basic benefit is the ability to add attributes to your POJO and change the behavior. That's it. Adding it to the WSDL is yet another real version of the WSDL? Where slipping an impl in with new underlying behavior specified by attributes would have merit I would think.

AW: http://schemas.xmlsoap.org/soap/http

Hm, I get the exception when starting the server context: String serverContextFile = "applicationContext.xml" ; ClassPathXmlApplicationContext serverContext = new ClassPathXmlApplicationContext( new String[] { serverContextFile}); How did you star

Re: Trouble with creating RESTful Service deployed to Jetty - need help!

Thanks for the quick response. HEre is the stack trace. I don't see a "Mapping method" statement. [INFO] Started Jetty Server Jul 12, 2007 12:33:32 PM org.apache.cxf.interceptor.AttachmentInInterceptor handleMessage INFO: AttachmentInInterceptor skipped in HTTP GET method Jul 12, 2007 12:33:

[no subject]

Hi, in Xfire it is possible to define a complex result object from a web service as an interface like this: public interface Greeting { public abstract void setMessage(String msg); public abstract String getMessage(); } @WebService public interface HelloWorldService {

Re: Code generation on Eclipse 3.2 STP 0.6

Hmmm I tried out your wsdl with our tooling and didn't have any issues. I don't have STP installed right now, so I could not be triggering the problem. Can you send along the classes that were generated? I think the mailing list strips attachments, so you may have to open a jira issue: http://iss

Re: http://schemas.xmlsoap.org/soap/http

This typically happens if you're trying to create an HTTP webservice and haven't either: a) Included the Jetty module on your classpath OR b) set up the CXFServlet. Have you done either of those? What does your config look like? Thanks, - Dan On 7/12/07, Marc Baumgartner <[EMAIL PROTECTED]> wrot

Re: Could not find destination factory for transport

Hi Rchard, This could or could not be related, but I'm pretty sure you need to specify the full address when creating a proxy: http://localhost/testService"/> BTW, you can use this improved syntax if you want too: You shouldn't need jetty on your classpath for the client, so I'm hoping that

Re: Trouble with creating RESTful Service deployed to Jetty - need help!

Hi Jason, Everything looks roughly correct. Can you paste the log output? You should some output from this line of code: LOG.info("Mapping method " + name + " to resource " + resource + " and verb " + verb); Which should help clarify whats going on... - Dan On 7/12/07, Jason Mihalick <[EMAIL

Trouble with creating RESTful Service deployed to Jetty - need help!

Hello, For the life of me I can't seem to get a simple RESTful webservice to work when I deploy it to Jetty (I haven't tried any other containers). I assume that I am correct in using the CFXServlet to handle requests and route them to the service implementation? iat-services is the name of

AW: Could not find destination factory for transport

I think you shouls set the 'bus' property of your 'clientFactory' bean. You can achive this using new SpringBusFactory().createBus(). For usage in Spring you need to define the SpringBusFactory and the Bus itself as separate beans and then inject the bus property into the client factory. Someth

Could not find destination factory for transport

I am getting the following error when trying to call a client using spring with CXF: 16:26:12,499 ERROR DispatcherUtils:245 - Could not execute action javax.xml.ws.soap.SOAPFaultException: Could not find destination factory for transport http://schemas.xmlsoap.org/soap/http at org.apache

AW: http://schemas.xmlsoap.org/soap/http

I experienced this problem when creating a client for my services. For me the schema itself did not help it was more likely a bug in the client setup. I had to call setBus( ... ) on the client factory then the error had gone. Example: NOT WORKING: JaxWsProxyFactoryBean factory = new JaxWsProxyFa

http://schemas.xmlsoap.org/soap/http

Hi all, I get an org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'helloWorldWS': Invocation of init method failed; nested exception is java.lang.RuntimeException: Could not find destination factory for transport http://schemas.xmlsoap.org/soap/http Where

Code generation on Eclipse 3.2 STP 0.6

Hi folks, I'm a experienced Delphi user and the IndySOAP library contributor (on sourceforge). Now I am trying to change to Java using Eclipse and STP. I'm using CTX 2.0 thru Eclipse STP 0.6 plugin. I built a very simple test WSDL and then I generated the java source code using the Java-WS t

Re: More javadoc

On Thursday 12 July 2007 09:37, Benson Margulies wrote: > Is there a mvn recipe for building all the javadoc? Preferably as one > giant lump that Eclipse can associate with the one giant jar of code? I think you can do a "mvn javadoc:javadoc -Daggregate=true" in the top level directory and it sho

More javadoc

Is there a mvn recipe for building all the javadoc? Preferably as one giant lump that Eclipse can associate with the one giant jar of code?

RE: Java out of memory building 2.0 from source with maven?!

That did fix it. > -Original Message- > From: Jiang, Ning (Willem) [mailto:[EMAIL PROTECTED] > Sent: Thursday, July 12, 2007 9:28 AM > To: cxf-user@incubator.apache.org > Subject: RE: Java out of memory building 2.0 from source with maven?! > > This is a common issue of the wsdl2java ma

RE: Java out of memory building 2.0 from source with maven?!

This is a common issue of the wsdl2java maven plugin, if you wsdl is very large , the out of memory exception will be thrown. Please try this export MAVEN_OPTS=-Xmx512M Cheers, Willem. -Original Message- From: Benson Margulies [mailto:[EMAIL PROTECTED] Sent: Thu 7/12/2007 20:49 To:

Re: Java out of memory building 2.0 from source with maven?!

One other note: If you're on a 64bit platform, you'll probably also need to set the MaxPermSize option. My MAVEN_OPTS setting is: MAVEN_OPTS=-XX:MaxPermSize=128m -Xmx512M Dan On Thursday 12 July 2007 08:54, Mosur Ravi, Balaji wrote: > Hi benson, > > You would have to set MAVEN_OPTS=-Xmx256m

RE: Generated client to connect to a https ws

Please have a look at the hello_world_https example and [1]. You need to pass the cxf configuration to bus. You can rename the configuration file to cxf.xml in you classpath or just set the system properity cxf.config.file to the config file name just as the example does. [1] http://cwiki.apac

RE: Java out of memory building 2.0 from source with maven?!

Hi benson, You would have to set MAVEN_OPTS=-Xmx256m to get the java compiler to compile that many source files. I don't know if this is documented but it needs to be... - Balaji -Original Message- From: Benson Margulies [mailto:[EMAIL PROTECTED] Sent: Thursday, July 12, 2007 8:50 AM To

Java out of memory building 2.0 from source with maven?!

This belongs on the devo list, I guess, but I'm really just a user running a build to get the rest of the javadoc. Any hints on how to get around this? I have the current 1.5 JDK. [INFO] Compiling 1313 source files to C:\x\s\apache-cxf-2.0-incubator-src\testutils\target\classes [INFO] -

CXF-781

I went ahead and dropped an issue report for a problem I encountered with type management of a service that combines JSR181 with Aegis. This is the only apparent impediment to moving this codebase from xfire 1.2.5 to CXF 2.0. I would be most grateful for any assistance here. I can play test-case b

RE: Generated client to connect to a https ws

Hi Willem, I tried your solution, but I still receive the same error :( I have debugged with cxf source, and the problem is in "HttpURLConnectionFactoryImpl": /** * This call creates an URLConnection for an HTTP url. * @throws IOException if the url protocol is not "http". */ p

Re: Endpoints: JAX-WS vs. WCF

Hi Ted CXF has a pretty good support for RESTful services for people preferring to deal with the data only and I'm sure it'll do even better in the future. But there's still a contract out there, albeit a generic one. And the interaction model is more close to the factory-instance CORBA-esque s

Re: Maven java2wsdl plugin error with jaxws

I tried explicitly adding those dependencies to the plugin, however still getting the error: 12-Jul-2007 10:00:57 org.apache.cxf.tools.java2wsdl.processor.JavaToProcessor process INFO: Classpath during Java2Wsdl: C:\Documents and Settings\joncam\My Documents\Workspace\slice\sandbox\sandbox-web\ta

RE: Endpoints: JAX-WS vs. WCF

But you can add that attribute in a variety of ways and get that same goodness; add it to the contract itself in WSDL (WS-Policy), add it to the interface (forcing implementations to recognize and support it, either through AOP or through hand-woven support), or on the class (where it is picked up