[jbossws-issues] [JBoss JIRA] Updated: (JBWS-1909) The native RequestHandler exposes implementation details

Heiko Braun (JIRA) jira-events at lists.jboss.org
Thu Nov 15 11:30:18 EST 2007


     [ http://jira.jboss.com/jira/browse/JBWS-1909?page=all ]

Heiko Braun updated JBWS-1909:
------------------------------

    Workaround Description: 
Instead of calling RequestHandler.handleWSDLRequest() to access the contract, you could get it through an URL input stream:

URL endpointUrl = spi.Endpoint.getAddress();
URL wsdlUrl = endpointUrl + "?wsdl";
InputStream in = wsdlUrl.openStream();


> The native RequestHandler exposes implementation details 
> ---------------------------------------------------------
>
>                 Key: JBWS-1909
>                 URL: http://jira.jboss.com/jira/browse/JBWS-1909
>             Project: JBoss Web Services
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: jbossws-jaxws, jbossws-jaxrpc
>            Reporter: Heiko Braun
>
> The RequestHandler implementation that's being used with native carries an implementation error:
> It does cast the InvocationContext to a concrete implementation instead of relying on the interface. This forces clients like the ESB to work with that particular implementation, ServletRequestHandler in this case.
> Here's the code:
> public class RequestHandlerImpl implements RequestHandler
> {
> [...]
> public void handleWSDLRequest(Endpoint endpoint, OutputStream outputStream, InvocationContext context)
>    {
> [...]
>       ServletRequestContext reqContext = (ServletRequestContext)context;
>       HttpServletRequest req = reqContext.getHttpServletRequest();
> [...]

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jbossws-issues mailing list