|
Home > Archive > WebSphere Application Server > December 2005 > Re: WSAD 5.1 : Calling a Web Service from an EJB with SSL, And on<br> Portlet?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Re: WSAD 5.1 : Calling a Web Service from an EJB with SSL, And on<br> Portlet?
|
|
|
| > I think the problem is that you should be using[vbcol=seagreen]
> webservices.xml instead
> of webservicesclient.xml.
>
> Your service-ref-name stanza below looks OK to
> me...that "should" be
> causing a "service" context to get created under
> java:comp/env, with a
> "ProcesoSeleccion" entry bound in that context.
>
> A portlet should (I think) have the characteristics
> of a servlet running
> in a web container at some level. I'm not sure about
> portlets
> specifically, but for a classic servlet application
> this needs to be in
> a file called webservices.xml (*not*
> webservicesclient.xml) in the
> WEB-INF directory within the .war file that's acting
> as the webservice
> client.
>
> webservicesclient.xml is only for clients running in
> the J2EE client
> container.
>
> bascard@yahoo.com wrote:
> Portlets to install on Portal Server 5.0. I have WSAD
> 5.1.2, and this doesn't provide tools to create a
> portlet that access to Web Service, and I have to do
> the same than you, generate client on a WebService
> Application, and then copy the files to Portlet
> Progect, but when I execute on POrtal Server I
> receive this error:
> comp/env/service not found in context "java:".
>
> ctx.lookup("java:comp/env/service/ProcesoSeleccion")
No, no, I have to use webservicesclient.xml because the portlet application is a client consumer of webservice. Moreover, before of that, I've created a Web Service Client project, I've tested and runs OK, with the same wsdl file. I've been searching a
lot from portlets that consumes web services, and in all places I find that you can create a portlet project and then import wsdl file and generate proxy client classes to consume that service. I've not changed nothing about classes generated from WSAD,
but when I deploy and test this project on Portal Server, I get that error. WSAD generate weserviceclient.xml to. Think about this " I've created a Web Service Client project with the same wsdl file ( proxy classes generated include webserviceclient.xml f
ile ) and When I test runs OK! But the same on Portlet Project no." Why?
|
|
|
|
|