While preparing for Test 000-379: IBM WebSphere Integration Developer V6.2, Solution Development I run across an interesting finding – generating an interface in a Library (in Business Integration perspective) will *always* create a WSDL portType.
It turned out that every interface in a Library can only be a WSDL portType and no Java EE projects can be a dependency of a Library.
The following screenshot shows the interface’s properties.
It came out when I played with creating an Import of a EJB stateless session bean (SLSB). Instead of developing a SLSB first (in Java EE perspective), I did it other way round. Firstly, I created an interface in a library, dragged and dropped an Import onto the Assembly Diagram and assigned it the interface. That’s when I was stuck. It took me a while to figure out why Generate Binding… for the Import had Enterprise JavaBeans Binding disabled.
The solution? Create an SLSB as you’ve always done (in Java EE perspective) and add the EJB project as a dependency of the module and do the rest. Easy, isn’t it? I bet you concur.
I’m going to write a few more blog entries about other EJB binding surprises as it struck me a few times how it really worked. It looks as if I were uncovering the truth (yet I’ve been working with WID/WPS combo for almost 5 years now). Nonetheless, such findings will certainly pay off during the test. I bet you concur…again.