Giorgio Zoppi wrote:
2007/11/29, Simon Nash <[EMAIL PROTECTED]>:
Giorgio Zoppi wrote:
2007/11/28, Jean-Sebastien Delfino <[EMAIL PROTECTED]>:
Giorgio Zoppi wrote:
One of the first problem that i had, when I started using Tuscany, was that
I was serialize something without a mapping, because I wanted that a
job was something
more generics possible, i couldn't.
I'm not sure I understand what you mean by "serialize something without
a mapping"? Isn't there always a mapping like:
- Java serialization -> mapping between Java Objects that implement
Serializable and bytes, as specified in the Java Object Serialization
specification at
http://java.sun.com/j2se/1.5.0/docs/guide/serialization/spec/serialTOC.html
or
- XML serialization -> mapping between Java Objects that follow
specified patterns and XML, as specified (for example) in the JAXB
specification at http://java.sun.com/xml/downloads/jaxb.html
or
- Java support for Externalizables -> mapping between Java Objects and
whatever protocol the implementor of the read/writeExternal methods
decides to implement, again here somebody needs to describe and publish
that mapping if he wants a chance to talk to other components, or at
least publish the mapping between the bytes read/written and a known
type system.
Can you say a little more about what you were trying to do and the
specific issues that you ran into?
Thanks
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Java Serialization ala Serializable, for mapping I wanted to say: xml
mapping ala JAXB. At that time, I thought that a simple POJO, was
serialized by the SCA's runtime, over web services. In our dept.
we've a java tool (muskel, see
www.di.unipi.it/~marcod/Papers/Parco05.ppt) that serializes Jobs via
RMI, and I wanted to do something similar, without any XML mapping.
Thanks,
Giorgio.
Tucsany SCA Java includes an RMI binding. This should do what you
want. Can you use that instead of the Web Service binding?
Yes, but my requirement was doing something over ws, in order to test
its scalability.
And I'm planning scalability testing with Apache JMeter for end of
the next week, when my workpool application will be ready. It's a
workpool that sampling the load on each jvm adds or remove workers
component.
Cheers,
Giorgio.
I looked at the slides you pointed to, interesting stuff!
I have a few questions.
You mentioned serializing Jobs. Looking at this example from slide 25:
Compute mainProgram = new Farm(new doSweep());
ParDegree parDegree =
new ParDegree(Integer.parseInt(args[0]));
ApplicationManager manager = new
ApplicationManager(mainProgram);
manager.setContract(parDegree);
manager.inputStream(args[1]);
manager.evalToFile(args[2]);
In that example, what is the object representing the Job that's going to
be serialized over the network (and I guess sent to a Worker)? Farm?
DoSweep? or ParDegree?
What are the main characteristics of the Job objects?
Do they have a static structure defined by an application developer
(like for example a Customer info, an Account info, or StockQuote info
object?)?
Or are they references to files containing parameter data for programs
that will execute on your Grid?
Or are they more like dynamic structures not formally defined by the
application developer, like "An instance of an anonymous class
implementing java.lang.Runnable plus all the final local variables in
its scope"?
Now a different category of questions:
What are you flowing through your Web Service right now? Are you
serializing Java objects into bytes and then tunneling the bytes in a
Web Service call?
Have you defined a WSDL portType for your Web Service?
Why are you using Web Services? Is your environment just Java or are you
integrating with other languages? I'm asking because slide 23 mentions
WS and "any OS with Java together" and slide 29 mentions C, C++ etc.
Thanks.
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
