Hi Simon, unfortunatelly I am seeing the same problem on WAS 6.1.0.9.
Sebastien, do you still have the WAS environment? Could you try to deploy RC3 based example web service on it? Thanks a lot, Radim On 9/19/07, Radim Kolarik <[EMAIL PROTECTED]> wrote: > Hi Simon, > > thanks for your reply. We will test it now with 6.1.0.9 and I will let > you know the result of that. > > Thanks, > Radim > > On 9/19/07, Simon Nash <[EMAIL PROTECTED]> wrote: > > As it's night time in California, I'll answer this question. > > Sebastien told me that he had tested on 6.1.0.9. Can you use that > > level instead of 6.1.0.11? > > > > Simon > > > > Radim Kolarik wrote: > > > > > Hi Sebastien, > > > > > > I am having problems making the app work on Websphere 6.1.0.11. Did > > > you try that particular fixpack, or did you try 6.1.0.9? > > > > > > In the 6.1.0.11 WAS the service is not being picked up at all, nothing > > > at all is logged to the log file if I try to access the service URL. I > > > tried it with the release candidate RC3. > > > > > > Thanks, > > > Radim > > > > > > > > > On 9/14/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote: > > > > > >>Jean-Sebastien Delfino wrote: > > >> > > >>>Jean-Sebastien Delfino wrote: > > >>> > > >>>>Radim Kolarik wrote: > > >>>> > > >>>>>Hi Sebastian, > > >>>>> > > >>>>>I received the latest code from ant and I can confirm that the service > > >>>>>generates the WSDL file now. The <binding.ws/> element doesn't even > > >>>>>need uri attribute, it works without any attributes! > > >>>>> > > >>>>>However, there is still some problem, the generated WSDL contains > > >>>>> > > >>>>>Error 404: SRVE0190E: File not found: /ComponentName > > >>>>> > > >>>>>at it's end, right after the </wsdl:definitions>. I have created a > > >>>>>JIRA for this: https://issues.apache.org/jira/browse/TUSCANY-1702. > > >>>>> > > >>>>>Are you seeing the same problem? > > >>>>> > > >>>>>Best regards, > > >>>>>Radim > > >>>>> > > >>>>> > > >>>> > > >>>>I just checked and am seeing this issue too (I had just not noticed > > >>>>that additional line at the end of the WSDL). However, the Web > > >>>>Service binding actually works for me on both references and services > > >>>>so if you manage to workaround that additional line at the end of the > > >>>>generated WSDL it should work for you too. > > >>>> > > >>>>I think it's another of these small behavior differences. On > > >>>>WebSphere we probably need to force a close of the response > > >>>>outputStream before returning from the servlet filter. I'm > > >>>>experimenting with that right now and will give an update soon... > > >>>> > > >>> > > >>>Radim, after a fun debugging session and some digging around here's an > > >>>update: > > >>> > > >>>- The issue you're seeing is the same as [1]. > > >>> > > >>>- This is a WebSphere 6.1 bug, a fix is available at [2]. > > >>> > > >>>I'm going to try some of the workarounds suggested in [1] and see if > > >>>they work for Tuscany. It would be good if you could also try the > > >>>WebSphere fix [2] as well if possible. > > >>> > > >>>[1] https://issues.apache.org/struts/browse/WW-1839 > > >>>[2] http://www-1.ibm.com/support/docview.wss?uid=swg24014758 > > >>> > > >>>Hope this helps. > > >>> > > >> > > >>Radim, > > >> > > >>It doesn't look like I can workaround this WebSphere bug in the Tuscany > > >>code. Your best bet is to install the fix at [2]. > > >> > > >>Could you please let us know the results after you do that? Thanks. > > >> > > >>-- > > >>Jean-Sebastien > > >> > > >> > > >>--------------------------------------------------------------------- > > >>To unsubscribe, e-mail: [EMAIL PROTECTED] > > >>For additional commands, e-mail: [EMAIL PROTECTED] > > >> > > >> > > > > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
