|
FAQ has been edited by Benson Margulies (Dec 04, 2007). Content:Frequently Asked QuestionsGeneralApache Incubator and Graduation - When is CXF going to graduate? Is the code "production ready?" Etc....The Apache Incubator is the entity designed to get projects up to speed with the "Apache" way of doing things. A project being in the incubator in no way reflects the quality of the code. There is some very good code in the incubator projects. Incubation status just means that the incubator PMC (or the project itself) doesn't feel that the project is quite ready to be a full Apache project. Some of the reasons:
Being in the incubator is not a "bad" thing. If the project is active, its members are most likely trying to "graduate" out of the incubator and are working on it. It just takes time. I think the average project spends about 1.5 years in the incubator. The project just needs to perform in such a way that the Apache Incubator PMC/mentors feel that the project is operating in the appropriate "Apache" way, has learned and demonstrated the proper Apache processes, etc... That said, a project in the incubator isn't guaranteed to graduate. There have been several projects that have "died" in the incubator. They were a good idea when they were started, but couldn't really generate a community around the code or the main company starting it withdrew the support, etc... The questions you need to ask yourself are: Do you feel comfortable with the level of support from the current CXF community? Do you feel we will still be here in 6 months? 1 year? Better yet, ask yourself, 'Could I join the community, contribute to the code, and become a committer?' The larger and more diverse our community of committers, the sooner (certis paribus) we will graduate. Can CXF run on JDK 1.4?No. Many of the technologies that CXF is based on require JDK 1.5. JAX-WS, JAXB, &cetra all require JDK 1.5 feastures such as generics and annotations. JAX-WS RelatedThe parts in my generated wsdl have names of the form "arg0", "arg1", ... Why don't the parts (and Java generated from them) use the nice parameter names I typed into the interface definition?Official answer: The JAX-WS spec (specifically section 3.6.1) mandates that it be generated this way. To customize the name, you have to use an @WebParam(name = "blah") annotation to specify better names. (You can use @WebResult for the return value, but you'll only see the results if you look at the XML.) Reason: One of the mysteries of java is that abstract methods (and thus interface methods) do NOT get their parameter names compiled into them even with debug info. Thus, when the service model is built from an interface, there is no way to determine the names that were using in the original code. If the service is built from a concrete class (instead of an interface) AND the class was compiled with debug info, we can get the parameter names. The simple frontend does this. However, this could cause potential problems. For example, when you go from developement to production, you may turn off debug information (remove -g from javac flags) and suddenly the application may break since the generated wsdl (and thus expect soap messages) would change. Thus, the JAX-WS spec writers went the safe route and mandate that you have to use the @WebParam annotations to specify the more descriptive names. Spring RelatedWhen using Spring AOP to enable things like transactions and security, the generated WSDL is very messed up with wrong namespaces, part names, etc...Reason: When using Spring AOP, spring injects a proxy to the bean into CXF instead of the actual bean. The Proxy does not have the annotations on it (like the @WebService annotation) so we cannot query the information directly from the object like we can in the non-AOP case. The "fix" is to also specify the actual serviceClass of the object in the spring config: <jaxws:server
id="myService"
serviceClass="my.package.MyServiceImpl"
serviceBean="#myServiceImpl"
address="/MyService" />
or: <jaxws:endpoint
id="myService"
implementorClass="my.package.MyServiceImpl"
implementor="#myServiceImpl"
address="/MyService" />
|
Unsubscribe or edit your notifications preferences
