Renga,
You can invoke any ejb from a collabration if you know the jndi name of that ejb, so you may create an initial context and lookup that ejb and invoke any operations on it.
In 5.1.0, there is no direct way to invoke another collabration in 5.1.0, although collabration runtime is an ejb itself, but its local interface is internal, so even you can find the jndi name from sun-ejb-jar, it does not help you much, if you succeed in using internal interfaces, it might not be supported in the next release.
So, if possible, you may create an individual ejb in the place of the collabration you wish to invoke and invoke that ejb inside the calling collabration.
I think in next release we will have that feature, not sure it will be in 5.1.1, but we have it on the table.
Cheers,
Mei
Hi,
what you said is correct,but in our project we are going to implement through JCD only,when you implement the JCD the java class code would be created automatically,If I tried the way which you said how can I import or embed the ejb file with my project.Because each and everything is with in Sun SeeBeyond.probably I will not refer any outside resources.
Cheers,
Renga.
Renga,
Is there any chance that you can use eInsight ? eInsight business process can invoke JCD easily and hassle free, wherease JCD ihvoking JCD is unimplemented, syou have to put an eway connector in between, if performance is not that critical , you may use JMS connector to link the 2 JCSs. But the best is to use eInsight business process to do so, there will be no perfromance sacrifice and lots of flexibility.
Cheers
Mei
Hi Mei,
I am able to call the collabaration from BP successfully ,but there is requirement in my project to call collabaration from a collabaration.As you said there is performance issue calling collabaration from a collabaration and also one person has given reply that in the latest version of sun seebeyond there is no option to call the collabaration from a collabaration I will try to implement my requirement within this circle.(calling collabaration from BP).
Thanks for giving immediate response,
Renga
However, be aware that if you expose the JCD as webservice, you'd need to connect this JCD using webservice connector, there has to be a connector between the 2 JCDs, whether it is webservice eway or any other eways, there is a performance downside in doing that. Using eInsight to concert all parts of JCD and eways is the best so far for your problem
--Mei
Probably the most efficient of the supported methods would be to create the "called" collaboration oas a JMS responder and ivoke it from the "calling" collaboration using JMS requestReply() method of the JMS connector.
The next would be a web service invocation, which was already mentioned.
There are also a couple of unsupported methods which are rather cumbersome to use.