Hi Martin,
Did you create a Jira for this issue of camelcase namespaces in CXF? I
didn't see any reference to this elsewhere. What went wrong?
Thanks,
- Dennis
On 07/08/2012 01:10 AM, Martin Gainty wrote:
Good Morning Dan
we had a serious issue with CXF handling of camelcase namespaces
On Sat, Jul 7, 2012 at 10:04 AM, Maria Din wrote:
> Hello,
> Please, I have this error ,
>
> import org.apache.axis.enum.Style;
> gives me this Error:
> Syntax error on token "enum", Identifier expected
>
> String nsOp = call.getOperationStyle().equals(Style.RPC) ? "u" : "";
> gives me this Error:
Good Morning Dan
we had a serious issue with CXF handling of camelcase namespaces which caused
generation of CXF service and CXF client to fail..we refactored the service and
client to Axis
Do you know if the CXF committers fixed CXF wsdl2code handling of camelcase
namespace so CXF based WSDLS
Hello,Please, I have this error ,
import org.apache.axis.enum.Style;gives me this Error:Syntax error on token
"enum", Identifier expected
String nsOp = call.getOperationStyle().equals(Style.RPC) ? "u" : "";gives me
this Error:The type org.apache.axis.enum.Style cannot be resolved. It is
indire