Hi Jan,
Since Authentication is an interface, so your real message response
should have an object(let's say it's instance of AuthenticationImpl)
which implement Authentication, right?
You need add AuthenticationImpl(which is an extra class for jaxb since
we cann't get this class when build service model and init jaxb context
from SEI) into jaxb context for mashalling.
Days ago, we have a similiar issue
https://issues.apache.org/jira/browse/CXF-340
All conversation and solution is on this link, I believe it's helpful.
Thanks very much
Freeman
Jan Kriesten wrote:
hi freeman,
Would you please append your whole testcase?
Is Authentication class defined as para or return type for your SEI?
the interface is defined as follows:
import javax.jws.WebMethod;
import javax.jws.WebParam;
import javax.jws.WebResult;
import javax.jws.WebService;
import org.acegisecurity.Authentication;
public interface IAuthService
{
@WebMethod
@WebResult( name="authenticated" )
public boolean authenticate( @WebParam(name="sid") String sid,
@WebParam(name="uid") String username, @WebParam(name="pwd") String password );
@WebMethod
@WebResult( name="authentication" )
public Authentication getAuthentication( @WebParam(name="sid") String sid );
@WebMethod
@WebResult( name="roles" )
public Set<String> getRoles( @WebParam(name="sid") String sid );
}
Authentication is an interface which extends Principal and Serializable.
I'm using the CXFServlet, so it might be that I have to configure AegisBinding
on the Servlet-side (client is set to Aegis), but the documentation doesn't say
how.
Best regards, --- Jan.
