[
https://issues.apache.org/jira/browse/CXF-1448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572582#action_12572582
]
Daniel Kulp commented on CXF-1448:
----------------------------------
Ben,
>From those soap messages, this looks like a qualification issue.
>JAX-WS+JAXB, by default, generates unqualified schemas. Thus, the elements
>in the messages are not namespace qualified.
Aegis, on the other hand ALWAYS expects and generates QUALIFIED schemas.
Thus, for the Aegis version, there are namespaces there.
For Aegis, it will always only deal with qualified. There isn't a way to
control that right now. For jaxb, the easiest way to flip it to using
qualified is to add package-info.java files in all the packages that have jaxb
beans that contains something like:
@javax.xml.bind.annotation.XmlSchema(
namespace = "http://annuaire.ciss.lu",
elementFormDefault = javax.xml.bind.annotation.XmlNsForm.QUALIFIED)
package lu.ciss.annuaire;
> Aegis DataBinding Problem - "Error initializing parameters for operation"
> -------------------------------------------------------------------------
>
> Key: CXF-1448
> URL: https://issues.apache.org/jira/browse/CXF-1448
> Project: CXF
> Issue Type: Bug
> Components: Aegis Databinding
> Affects Versions: 2.0.4
> Environment: I am running WebLogic 9.2.2 on Windows XP
> Reporter: Ben McCann
> Assignee: Benson Margulies
> Fix For: 2.0.5
>
> Attachments: AuthService.java, AuthServiceImpl.java,
> AuthServiceImpl.java, cxf.xml, Employee.java, Employee.java, stackTrace.log,
> stackTraceWithSetCommentedOut.log
>
>
> Hi,
> I am getting "Error initializing parameters for operation" from Aegis. I set
> it up through Spring. My classes mostly just use String, so I'm not sure
> what the problem is.
> Thanks,
> Ben
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.