I recommend that you use the Web Service Provider design element, that what it is for right?

In addition you get the WSDL generated automatically to your service consumers.

Moi Rami. Yes, that's what I've been using in the past. It just looks like everything else in Domino is in maintenance mode except XPages and that's why I'm always thinking if things can be done with XPages. I would think Eclipse would also generate WSDL (or how do people create web service providers in pure Java world?).

 

Also, it would be nice to use the new Java design elements in new Java development but those are only available for XPages.  

Moro :)

 

What come to the pure Java world, it depends. There are way too many+1 Web Service projects. Eclipse contains some tools as well, but I've neve used them. Instead of Eclipse tools, I've used more or less Open Source software, mainly Apache Axis and Spring Web Services, but that's J2EE world.

 

The good news is that Domino's Web Service engine is based on the same AXIS WS engine. And actually it is quite good and easy to use. Just create one Java Interface class (or implementation class I think)  and you are good to go to publish the WSDL. Standards rules :)

 

What did you mean by the Java tools available only in XPages?

OK thanks, looks like I'll stick to Web Service design element at this point. 

 

With Java Design Element I mean the new 8.5.3 feature which is an easy way to create shared Java classes (Code -> Java). I hope those can be used in agents and web services in the future.

Ok Never actually tried to create a "code ==> Java" element and see where you can use it. I knew it was xpages related but some how I thought that they could be used in Java agents aswell.

Have you tested this?Just asked because these Java files goes to project's build path automatically when you create one Java file.

Looks like you are right! If I refer to my Java design element classes in an agent the editor shows an error. But Eclipse suggests to fix project setup (add db to Java Build Path), fixes it for me and after that the Editor does not show an error so I believe it will work. At least in my case the Java elements did not end up to the build path automatically.

 

Earlier I had tried to add these Java classes in the same place you add Script Libraries in an agent. I also asked about this in the IBM "non Xpage" forum and got a reply they are for XPages only. 

 

This is good news, now I don't have to maintain two versions (Script Library ja Java element) of my shared Java classes.