Even though Jini doesn't help a lot it also doesn't get in the way. If you wanted to
ship documents around they don't have to be XML. They could be an optimised
form of DOM that is serialisable (e.g. Integration Objects from C24 www.c24.biz).
I know a lot of folks using Jini and JavaSpaces with IO from C24 in which they get
the best of all worlds.

Don't know if John Davies monitors this forum but maybe he will have a thing or
six to say.

Cheers

Steve T

On 2 Aug 2006, at 18:36, Gregg Wonderly wrote:

Anne Thomas Manes wrote:
> Spring is pretty confusing in its own right. Not quite as complex as Java
> EE, but still a lot more complex than .NET.
>
> What frameworks do other people like?

I prefer Jini because I can use mobile code to separate transport from
interface. Because Jini is not targeted at solving any particular type of
problem directly, a lot of people experience a pretty significant startup
barrier. There are, however, tools and libraries available in projects under
http://jini.dev.java.net that help with getting started with Jini and with
building specific types of applications. The http://www.jini.org site has
pointers to a wide array of educational information about Jini.

If all you want to do is ship XML around, you might wonder how Jini will make it
easier for you to do that. The answer is that Jini is not targeted at helping
you easily ship XML around. It enables you to easily choose to not ship XML
around. If you need to ship XML, then because Jini is a Java based platform,
you can use the Java tools available for shipping XML around. The JERI stack
provides a plugable endpoint and invocation layer so that you can make native
java code interface into arbitrary protocols, such as those that ship XML around.

Gregg Wonderly


__._,_.___


SPONSORED LINKS
Computer software Computer security software Computer software program
Computer fax software Computer virus software


YAHOO! GROUPS LINKS




__,_._,___

Reply via email to