Hi Everyone,
Is it just me or is the Java Web Services implementation in the Eclipse Designer full of bugs?
I’ve been working with those for the last two weeks, and I keep finding bugs… and major one! I’m not able to work with them at all!
The current count is now 8 bugs!
I’m using a 8.5.1FP3 Notes client (on Windows XP 32bit) and a 8.5.1FP3 Domino server (on Windows 2008 64bit).
I opened some calls at Lotus support, but no solutions were offered yet.
We were told by everyone to switch to the new Designer and to learn Java, but I’m running into problems I didn’t have when I was using my old Notes 8.02 client with LotusScript. If It was 8.5.0, I would understand… but 8.5.1!
Are Java Web Services (8.5.1) actually used by someone?
Are there people who did work with Java Web Services in 8.5.1?
If so, could you share your experience please?
Thanks
Subject: more detail please
are the problems happening with writing the web services, or when running them, or both?
Subject: here’s more details
Hi Maureen,
It happens mainly when writing them, but also when running them.
Luckily I found that at least two of my bugs are gonna get taken care of in 8.5.2:
doc/literal bug:
http://www-10.lotus.com/ldd/r5fixlist.nsf/8ed1b46cfdba8957852570c90054623b/d4fa19e660b051908525775b006de8c7?OpenDocument
Java script library bug:
http://www-10.lotus.com/ldd/r5fixlist.nsf/8ed1b46cfdba8957852570c90054623b/e58b857a75f462bf85257737006df414?OpenDocument
I have also an issue when method parameters are always named “n0”, “n1” in the WSDL, etc… instead of their actual name. This is similar to this, but I’m not sure that’s the same issue:
http://www-10.lotus.com/ldd/r5fixlist.nsf/8ed1b46cfdba8957852570c90054623b/22f9c04ff1dc3abd85257737006df408?OpenDocument
Another one is when I type “\u” in the Java Editor and then I save, those characters are then removed (and some more).
When I call a Web Service in SSL, on some servers, I receive the error “SSL invalid certificate, may need to cross-certify” even though I did add that SSL certificate.
I’m having a hard time displaying the “Java Debug Console”… I managed to display it once, and now, I can’t.
And some more issues…
I’m not even talking about crashes, which now happen at least 3-4 four times a day.
Thanks
Subject: I’ll forward the runtime issues to the web service team, but
the designer issues look good to me in 8.5.2 so far… When I type “\u” the Java editor shows an error and tells me that it is invalid unicode. If I properly escape the character as “\u” all is well, and I can save and reopen the web service and it remains as it should. I can’t remember if this is something we fixed in 8.5.2 or not (I am running a daily build of 8.5.2) - but is what I typed/tried different from what you’re trying to do?
The java debug console is also behaving for me in my 8.5.2 build, but I would have to follow your exact steps to be 1000% sure. Were you displaying it from a client or designer menu item (both work for me, but trying to narrow).
Subject: even more details
Thanks Maureen for the follow-up.
I try to type this line in the Java editor of my Eclipse Designer 8.5.1:
sb.append(“\u” + t.substring(t.length() - 4));
When I hit save, I get no error, but when I try to open the Script Library again, the line has changed for this:
sb.append("\t.substring(t.length() - 4));
As for the Java Console, I’m trying to display it from the Designer. When I select it from the menu, nothing happens. Do I have something special to do? In 8.02, I just had to select it from the menu.
Thanks
Subject: Re: method parameters and SSL certificates
Re: method parameters are always named “n0”, “n1” in the WSDL
Try selecting the “Compile Java code with debugging information” option in the Web server properties panel, and then resaving the Web service. This should inject the method parameter names into the generated WSDL.
Re: SSL invalid certificate
Web services runs within the Domino HTTP security context (and is unaware of that context). If the same certificate is working on some servers but not others, it may be worth trying to verify the certificate with those servers in some other way besides a Web service call. The Domino Administrator help topics on SSL may be of some guidance there.
Subject: Thanks!
"Re: method parameters are always named “n0”, “n1” in the WSDL
Try selecting the “Compile Java code with debugging information” option in the Web server properties panel, and then resaving the Web service. This should inject the method parameter names into the generated WSDL."
Woah, that did it!
Is this a bug?
As soon as I uncheck that box (and save the web service), the parameters are named “n0”, “n1” again.
If it’s a bug, will it be solved in 8.5.2?
Is it the same issue:
http://www-10.lotus.com/ldd/r5fixlist.nsf/8ed1b46cfdba8957852570c90054623b/22f9c04ff1dc3abd85257737006df408?OpenDocument
Is it OK to leave the “Compile Java code with debugging information” option always checked (even on a production server)?
Thanks!
Subject: Re: injecting Java method parameters into generated WSDL
Actually, no, we don’t consider this a bug, rather it’s a feature of the code-generation architecture. The WSDL generator uses Java introspection to examine the compiled code in order to generate WSDL content, and without that setting, the full method parameter names aren’t compiled into the Java objects.
We know of no reported problems using that setting in production code.
Subject: Thanks again!
One last question, could you tell me what exactly does the “Compile Java code with debugging information” option?
Thanks again!
Subject: Re: “Compile Java code with debugging information”
Setting this option adds more symbol information to the compiled Java objects. It’s a feature inherited from the Domino agent programming model (upon which Domino Web services are based), originally intended to support Java Agent remote debugging.
Subject: If you haven’t already done so
Can you log a customer report against the SPRs you mention. With the customer reports against certain issues, it allows development to prioritize.
With 8 PMRs open (at the same time?) I would recommend if you have not already done so explain the impact to the engineer of all PMRs (assuming there is more then one engineer).
I don’t have any details regarding your PMRs here so I can’t follow up. 
Lastly if you feel you are not getting the support you expect from Lotus Support, you can ask to speak to a manager at any time.
Subject: that’s what I’ll do
Thanks Simon for the follow-up.
I opened many PMRs last week and fortunately, some of them seem to be solved in 8.5.2.
I’ll continue to report them to Lotus Support cause I understand that If they don’t know about them, they can’t correct them.
My question was that those bugs are about very basic functionalities in the Java Web Service/Script Library area and I was wondering if some people actually used those in Eclipse Designer 8.5.1 of If I was the only one with those issues.
Based on the SPRs I found, It seems I was not the only one. I can’t wait for 8.5.2! 
Thanks
Subject: 8.5.2 solved many bugs (client and server)
Actually, 5 out of 9 bugs were solved in the 8.5.2 release, including these:
- Java Web Service Consumer doc/literal bug:
http://www-10.lotus.com/ldd/r5fixlist.nsf/8ed1b46cfdba8957852570c90054623b/d4fa19e660b051908525775b006de8c7?OpenDocument
- Java Web Service Provider Vs Script Library bug:
http://www-10.lotus.com/ldd/r5fixlist.nsf/8ed1b46cfdba8957852570c90054623b/e58b857a75f462bf85257737006df414?OpenDocument
- Java Web Service Provider parameters bug (no need to select “Compile Java code with debugging information” anymore):
http://www-10.lotus.com/ldd/r5fixlist.nsf/8ed1b46cfdba8957852570c90054623b/22f9c04ff1dc3abd85257737006df408?OpenDocument
I still have the Web Service Consumer Vs SSL bug (I opened a PMR and IBM are able to reproduce the issue) and I still have problems displaying the Java console in my Eclipse Designer (sometimes it works, other time it doesn’t).
The other two bugs are minor and they might not even be Notes/Domino issues.
So far, my Eclipse Designer hasn’t crashed (in two days) and it looks a little big faster.
So… good job on 8.5.2!