I use Hessian protocol.
Also, consider OSGi (Eclipse) for breaking up a war into modules.
.V
Leon Rosenberg wrote:
On 3/29/06, Emmanouil Batsis <[EMAIL PROTECTED]> wrote:
Leon Rosenberg wrote:
But I think that CORBA can compete very well here!
Or do you have other impressions?
Nope, just w
Hi,
Our existing application already used hibernate, so switching to ejb3 was
really simple.
As for spring, no we don't use this but we do use jboss' own aop implementation.
As for performance, we've had no issues here, hibernate certainly helps as a lot of the requests to
the database are hit
On 3/29/06, Emmanouil Batsis <[EMAIL PROTECTED]> wrote:
> Leon Rosenberg wrote:
>
> >But I think that CORBA can compete very well here!
> >Or do you have other impressions?
> >
>
> Nope, just wanted to point out that, where i come from, the analogy of
> CORBA and EJB devs is 1 to 10 at best.
Same
Leon Rosenberg wrote:
But I think that CORBA can compete very well here!
Or do you have other impressions?
Nope, just wanted to point out that, where i come from, the analogy of
CORBA and EJB devs is 1 to 10 at best.
Cheers,
Manos
-
Tom Ziemer wrote:
@Gareth: What do you think about the performance of ejb3? Did you
integrate it with other frameworks such as Spring and/or Hibernate?
Hibernate 3 can be used as an EJB3 implementation. See EJB 3.0
EntityManager:
[1] http://www.hibernate.org/299.html
hth,
Manos
Hi,
@Leon: I am really grateful for your input. So basically, RMI is 10
times slower than corba. This is bad! I just found out, that I
expose/access CORBA via Spring (and RMI) but that doesn't really help,
since I simply cannot switch to Corba (lack of time) right now.
@Gareth: What do you think
On 3/29/06, Tom Ziemer <[EMAIL PROTECTED]> wrote:
> Hi Leon,
>
> Spring: Well, our app started as a single jvm version and I used Spring
> (and will continue to do so) because it's an incredibly powerful, easy
> to use yet unobtrusive framework. You get transaction support, aop,
> hibernate/ibatis
Hi Leon,
Spring: Well, our app started as a single jvm version and I used Spring
(and will continue to do so) because it's an incredibly powerful, easy
to use yet unobtrusive framework. You get transaction support, aop,
hibernate/ibatis and support and DI by simply declaring it in your
config file
On 3/29/06, Emmanouil Batsis <[EMAIL PROTECTED]> wrote:
>
> Hello Leon,
>
> Just wanted to mention that another decision factor is the available
> pool of human resources ;-)
Of Course!!!
But I think that CORBA can compete very well here!
Or do you have other impressions?
>
> Manos
Leon
--
Hi,
I've been using ejb3 in development for the past couple of months, we've also got a small number of
production systems using ejb3.
We use the ejb3 layer as the "communications" bit for the current project we are working on and so
far has worked extremely well.
As for the human resources
Hello Leon,
Just wanted to mention that another decision factor is the available
pool of human resources ;-)
Manos
Leon Rosenberg wrote:
On 3/29/06, Tom Ziemer <[EMAIL PROTECTED]> wrote:
Hi Leon,
Hi,
I've been doing a bit of reading and I guess I'll be using Spring's
remoti
On 3/29/06, Tom Ziemer <[EMAIL PROTECTED]> wrote:
> Hi Leon,
Hi,
>
> I've been doing a bit of reading and I guess I'll be using Spring's
> remoting support in conjunction with RMI. Seems like the easiest way to
> do this.
If performance is not an issue, got for it. It's quite a pity that
people
Hi Leon,
I've been doing a bit of reading and I guess I'll be using Spring's
remoting support in conjunction with RMI. Seems like the easiest way to
do this.
Just out of curiosity, why did you rate EJB with a -10, yet RMI with a
0? AFAIK, EJB use RMI - so why do you consider plain RMI to be that
JMS as far as I now is comparable with the notification service in
corba. Therefore it offers you about 5% of the functionality corba
offers you.
regards
leon
Btw, JMS doesn't fit in ANY application, you should have the special
type of application to use it.
On 3/28/06, Tom Ziemer <[EMAIL PROTEC
Hi Leon,
thanks for the input. May I ask how you would rate JMS and if this would
also be a suitable solution for decoupling applications? I am a bit
reluctant to switch to CORBA since I have absolutely no experience in
this area.
Regards,
Tom
Leon Rosenberg wrote:
> If you want performance go f
If you want performance go for CORBA
if you want interface stability go for CORBA
If you want simplicity go for RMI
If you want use 3rd party products go for EJB (CORBA would do also).
In my personal opinion, EJB would be a -10, SOAP -5, RMI 0, CORBA +1.
If you are looking for a good (or best) c
Hi Tom!
On 3/28/06, Tom Ziemer <[EMAIL PROTECTED]> wrote:
>
> Hi Tamas!
>
> Unfortunately, I cannot include my base-jar in both projects, because I
> am using Hibernate, which heavily uses caching. Therefore, updates that
> are performed by web services are not visible on the web. Having two
> ve
Hi,
thanks for the input - so I'll add EJBs to the list of possible
solutions :o). I agree with you, that SOAP is not really the method of
choice for this kind of problem - although in some instances it might be.
Tom
Emmanouil Batsis wrote:
>
> Hello Tom,
>
> In short, there is no panacea or g
Hello Tom,
In short, there is no panacea or golden formula. I usually go for EJBs
for my business logic (so, RMI & JMS). You can bypass RMI when on the
same JVM by using local interfaces and in some servers AFAIK you dont
even have to explicitly do that.
Personally, i try to avoid web servi
Hi Tamas!
Unfortunately, I cannot include my base-jar in both projects, because I
am using Hibernate, which heavily uses caching. Therefore, updates that
are performed by web services are not visible on the web. Having two
versions of a hibernate app accessing the same db is not a good thing to
do
Hi Tom,
Is there a reason you can't have all the business service layer in a Common
project and include it as a jar in both the web gui an the web services app?
I usually use this approach if possible...
I'm interested in what others say about this but I wouldn't go on the path
you want to go if
Hi Tamas,
thanks for your reply. Modularity is not my only concern. I am pretty
sure that performance considerations will soon force me to separate the
app, since the web services will do lots of number crunching, which in
turn, will slow down the entire app. Apart from that, I figured it's a
bett
HI,
Do I understand it correctly?
Do you want to break it up just to ensure that is modular?
If it isn't a requirement then I wouldn't add some communication layer
between the modules.
Be happy that you have everything in one JVM and you don't have to deal with
the complexity resulting from ANY o
Hi,
I am a developer, currently working working on a medium scale app. There
is a base module, which is Spring managed, that handles data access - a
web tier and now a couple of web services. Up until now, we deployed
everything as one application, so communication between the modules was
API-base
24 matches
Mail list logo
