Hi,
yes, it could be. Look at this tutorial to learn how to write a plugin adapter. Let us know if you are successful to interface JOpera with JME. http://www.jopera.org/docs/help/jop_12.html
Thank u for your response. But before going and creating plug in for JME . I noticed that to compose JAVA methods and constructor it should implement serializable . Is it the same for JME because JME for CLDC does not support serialization.
serialization is only needed to exchange Java Objects through the data flow of a JOpera process. The objects that flow through the process need to be serializable.
However, you do not need to worry about it when you implement an adapter, because you can always exchange data with JOpera using basic String objects (which are serializable anyway). Also, none of the classes that implement your plugin adapter have to be serializable.
I hope this helps. Let us know if you have any trouble developing your JME adapter plugin.
I followed the steps for creating service invokation plug in but I did not know how to proceed in defining the resource of the model extension, Some resource is created by default "TestPlugin.model2" Shall I keepit ?or create an OML file before creating service invokation plug in ? How to define parameters for JME?
Thanks
At run-time you will need to pass some information to JME in order to run it. You can break down this information into multiple system input parameters associated with the JME component type. The actual set of parameters depends on JME. Look at the other JOpera Adapters for some examples on how different service invocation technologies have been implemented as a JOpera component type.
You will find an example of an OML component type definition if you download the hello world adapter. You can start from it and modify it to suit your needs in invoking JME.
So the steps are:
1. Create a new plugin with the content of the hello world adapter
3. Open the data/demo.oml file and edit the component type definition by entering all the input parameters you need to invoke JME
4. Edit the code of the DemoSubSystem to read the JME parameters out of the job sent by JOpera
5. Start a new Eclipse/JOpera instance to test your plugin
Thanks for your reply.
I followed the above steps but when creating a new JOpera OML file and adding an Adapter to it .My created adapter was not on the list.
Another observation is the integer input parameters give an error in the following command
Integer IN1 = validateInput(job, IN1);
Integer IN2 = validateInput(job, "IN2");
Could you please help me in solving the above issues?
Netbeans
There is no version for Netbeans?
Only Eclipse
JOpera for Eclipse only runs on Eclipse. We do not plan to support NetBeans at this stage
Add an adapter plugin
Hi,
yes, it could be. Look at this tutorial to learn how to write a plugin adapter. Let us know if you are successful to interface JOpera with JME.
http://www.jopera.org/docs/help/jop_12.html
Serialization
Thank u for your response. But before going and creating plug in for JME . I noticed that to compose JAVA methods and constructor it should implement serializable . Is it the same for JME because JME for CLDC does not support serialization.
Serialization clarification
Hi,
serialization is only needed to exchange Java Objects through the data flow of a JOpera process. The objects that flow through the process need to be serializable.
However, you do not need to worry about it when you implement an adapter, because you can always exchange data with JOpera using basic String objects (which are serializable anyway). Also, none of the classes that implement your plugin adapter have to be serializable.
I hope this helps. Let us know if you have any trouble developing your JME adapter plugin.
Best Regards,
JOpera Team
I followed the steps for
I followed the steps for creating service invokation plug in but I did not know how to proceed in defining the resource of the model extension, Some resource is created by default "TestPlugin.model2" Shall I keepit ?or create an OML file before creating service invokation plug in ? How to define parameters for JME?
Thanks
JME Parameters and getting started help
At run-time you will need to pass some information to JME in order to run it. You can break down this information into multiple system input parameters associated with the JME component type. The actual set of parameters depends on JME. Look at the other JOpera Adapters for some examples on how different service invocation technologies have been implemented as a JOpera component type.
You will find an example of an OML component type definition if you download the hello world adapter. You can start from it and modify it to suit your needs in invoking JME.
So the steps are:
1. Create a new plugin with the content of the hello world adapter
3. Open the data/demo.oml file and edit the component type definition by entering all the input parameters you need to invoke JME
4. Edit the code of the DemoSubSystem to read the JME parameters out of the job sent by JOpera
5. Start a new Eclipse/JOpera instance to test your plugin
Start up
Thanks for your reply.
I followed the above steps but when creating a new JOpera OML file and adding an Adapter to it .My created adapter was not on the list.
Another observation is the integer input parameters give an error in the following command
Integer IN1 = validateInput(job, IN1);
Integer IN2 = validateInput(job, "IN2");
Could you please help me in solving the above issues?