[
https://issues.apache.org/jira/browse/CXF-1448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572150#action_12572150
]
Ben McCann commented on CXF-1448:
---------------------------------
I got this up and running on JBoss. It's better than WebLogic in that I don't
get the "The uri may not be theempty string." error, but doesn't work
completely yet. I get back my employee, but when I call employee.getLastName()
in my jUnit test it returns null. Works okay on both JBoss and WebLogic
without Aegis.
You said you suggested not using the AegisServiceConfiguration. If I take that
out I can still use the Aegis databinding without any problems, correct? (I
tried taking it out and it didn't affect either JBoss or WebLogic) I'm afraid
I don't know much about Aegis, and just took this from the CXF docs.
> 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.
