Now that we are satisfied that the test runs OK, may I enquire as to the particular use case that you are trying to achieve?
From what I have understood so far you already have existing XATMI services written in C/C++ that you would like to access from Java. If this is the case, I think it is possible that JAB may be the best tool for you.
The EJB connector is really intended to allow the creation of new Java services which can take input from existing XATMI C/C++ clients (e.g. it can respond to an existing tpcall invocation) - kind of the converse of the JAB API.
looking EJB code and with your last reply I clarify me about EJB case.
Now I'm sure that there is not an equivalent Jolt tool, but thanks to JAB is possible to call directly xatmi server from Java code.
I've one more question, there is in the future of Blacktie a deployable Web Service tool (for Jboss) to make possible to call xatmi service? or something similar?
thanks a lot
If you are asking "will a client be able to access Blacktie XATMI services via a Web Service proxy" in the future then I can tell you that that is currently on our roadmap.
If you already have a webservice written in Java and deployed onto JBoss then you can use JAB client library to access Blacktie XATMI servers running natively.
Hope this is clear,
I use this topic to continue my converstion, I've tryed three sample (xatmi, JAB, EJB) now I'm going to make further test, in particular I would to deploy an xatmi sever including my business logic and call it from another side (not local host). What changes I have to do this?
For example when I build client or to jacorb configuration ns to bind an address ... and so on.
Second question I have for you is about blacktie documentation, although I've read some document concerning JavaTS, Jacorb and few page of BlackTie, there is no specific documentation about architecture and configuration of this young boy...have you something to deploy at the moment??
In order to access a remote server you need to:
1. For C clients and servers edit the Environment.xml file and alter the ORB_OPT setting that usually says "-ORBOnitRef NameService=corbaloc::localhost:3528/NameService" to be the name of the machine where you are running the name service.
2. For the JAB client you change the same parameter (in the same way) but this is done on the command line. In future versions of JAB we hope to introduce support for parsing the same configuration files in Java as in C.
3. For the EJB example. the CORBA Name Service is configured in the blacktie.properties, in the example this file is under BLACKTIE/examples/ejb/ejb-connector/example/src/main/resources, again, potentially the EJB connector will support parsing of the same files as the C side in the future
By means of an FYI, the name service is launched when you execute the "./start_all.sh|bat" command.
In regards question 2, the documentation is indeed currently "light" and will be so for a while. We are fleshing out the wiki pages and I hope to be able to create a digest of those for the manual so if there is anything missing that you would like to know, ask it on the forum and I will try to create a wiki article on it.
I have created Jiras for the two specifics you mentioned "configuration" and "architecture" which I have marked them as to be delivered as part of Milesone 4 - hopefully this will be OK for you!