Now, the only thing missing for it to be perfect, in my book,
is that it doesn't use maven to build... :)
I'm not a maven expert. There's a pom that currently does not work
Par for the course. ;-) As long as it builds with Ant, people should be
happy.
--- Noel (reknowned Maven
Scott Comer (sccomer) wrote:
Have you looked at apache etch?
Yes, I now have looked at it. It's great.
It seems that Etch has a much broader scope than Jaffre ever will have.
If I understood it right, Etch comes with it's own interface description
language, and let's users the freedom to
On Thu, Mar 19, 2009 at 12:03 AM, Alexander Veit alexander.v...@gmx.net wrote:
Sounds like RMI is probably not the best comparison point. How does
Jaffre differ from XML-RPC? Are there potential synergies with
projects like http://ws.apache.org/xmlrpc/?
I'm not familiar with XML-RPC. The
This really looks cool and I surely would have evluated it for my
project, if available stable before two years.
Would hessian as a binary format be an option for Jaffre btw?
See: http://hessian.caucho.com/
its also released under ASL
I think Commons would benefit from this component and I would
Hi Alexander,
could you provide some more technical background information
+) how does it compare to RMI, JSON or Hessian (http://hessian.caucho.com/)
Siegfried Goeschl
Alexander Veit wrote:
Dear all,
I would like to start an incubator project at the Apache Software Foundation
with a Java
Siegfried Goeschl wrote:
could you provide some more technical background information
The idea is quite simple and certainly not new in the Java world: method
calls and return values are considered as data structures that are being
serialized for transport.
The data structures are
Outside the WS-*, JAX-WS and JAX-RS there are at least Etch and Thrift
projects in a similar space. Those two projects are both
high-performant, light-weight and more importantly language/platform
inter-operable. Is there any particular advantage over these two
projects that you can see for
Jaffre does not need skeletons/stubs. The endpoints are pojos, parameters
and return values are java.io.Serializable objects.
No registry is required.
Jaffre Connectors listen well-defined ports that can easily be bound to a
specific address. They are firewall friendly.
An experienced
Hi,
Sounds interesting. Is the code already available online?
Sounds like RMI is probably not the best comparison point. How does
Jaffre differ from XML-RPC? Are there potential synergies with
projects like http://ws.apache.org/xmlrpc/?
BR,
Jukka Zitting
Hi,
On Wed, Mar 18, 2009 at 2:16 PM, Santiago Gala santiago.g...@gmail.com wrote:
El mié, 18-03-2009 a las 11:40 +0100, Jukka Zitting escribió:
Sounds like RMI is probably not the best comparison point. How does
Jaffre differ from XML-RPC? Are there potential synergies with
projects like
Santiago Gala wrote:
I think it would be more appropriate as a commons component
than in any other place. I liked the stress on not having any
dependence beyond the JRE and not being XML. Both play quite
badly with WS-*, where the norm is using XML and having lots of
(inter)dependencies.
Alexander Veit wrote:
Dear all,
I would like to start an incubator project at the Apache Software Foundation
with a Java library (let's call it Jaffre) I've written.
Jaffre is a lightweight RPC library for the Java platform.
It is designed to be simple, extensible, robust, and efficient
Hi Thilo,
Thank you very much for your answer.
Thilo Goetz wrote:
there are two things I'd advise you to do.
One, put up a project proposal in the incubator wiki:
http://wiki.apache.org/incubator/
You can also look at older proposals there. There is
no need to do this all at once, you
On Mar 17, 2009, at 22:54 , Alexander Veit wrote:
Two, it sounds like your project is related to the
web services world. So check out the projects under
the Apache WS umbrella (http://ws.apache.org/), and
also Apache CXF.
Yes, there are similarities to web services.
However, Jaffre neither
Marcel Offermans wrote:
Out of interest, if it's a simplified kind of RMI, what are
the tradeoffs for using RMI vs using Jaffre?
Jaffre does not need skeletons/stubs. The endpoints are pojos, parameters
and return values are java.io.Serializable objects.
No registry is required.
Jaffre
Dear all,
I would like to start an incubator project at the Apache Software Foundation
with a Java library (let's call it Jaffre) I've written.
Jaffre is a lightweight RPC library for the Java platform.
It is designed to be simple, extensible, robust, and efficient with
no required dependencies
16 matches
Mail list logo
