Hello,
Your FAQ says that Lightstreamer is able to receive messages from Tibco RV and EMS and distribute them to end-users.
Do you have an example of a Lightstreamer RV data adapter?
Thanks much,
Eric
Printable View
Hello,
Your FAQ says that Lightstreamer is able to receive messages from Tibco RV and EMS and distribute them to end-users.
Do you have an example of a Lightstreamer RV data adapter?
Thanks much,
Eric
In fact, Lightstreamer is a natural extension to RV and EMS for the web, but coding custom Data Adapters, which are also clients for RV or EMS, is still needed.
The distribution package contains an example of a Data Adapter based on JMS, with two example configuration, one for JBoss Messaging (currently uncommented) and one for EMS (currently commented out).
On the other hand, there is currently no example based on RV. We hope that the EMS example is still insightful for that case.
I started the install for the JMS data adapter you mentioned above and followed the README.txt however the Lightstreamer server does not start. During the install I noticed that in step 4Quote:
Originally Posted by DarioCrivelli
"Copy the "jms.jar" and "customjmsjar.jar" files under "StockQuotesJMSAdapter/lib"
(or under "LightstreamerHome/shared/lib" if you think that those jars will be
used by other Adapters too)."
The two jar files (above) are not included in the zipped package and the server displays an error
17.Jun.08 16:08:09,506 < INFO> StockQuotesJMSAdapter ready.
17.Jun.08 16:08:09,559 <ERROR> NamingException: Cannot instantiate class: org.jnp.interfaces.NamingContextFactory
javax.naming.NoInitialContextException: Cannot instantiate class: org.jnp.interfaces.NamingContextFactory [Root exception is java.lang.ClassNot
FoundException: org.jnp.interfaces.NamingContextFactory]
Any help would be appreciated.
Thanks,
Eric
Eric,
Please refer to the README.TXT file under "Lightstreamer\DOCS-SDKs\sdk_adapter_java\examples\StockListDemo_JMS_D ataAdapter". You will find the instructions on where to look for these JAR files based on thr JMS product you are using. In particular, "customjmsjar.jar" is a placeholder that can refer to one or several files. For example, with JBossMQ, "customjmsjar.jar" means "jbossmq-client.jar".
Cheers