On Feb 7, 3:01 pm, marlow.and...@[EMAIL PROTECTED]
wrote:
> On 17 Dec 2007, 21:41, ap...@[EMAIL PROTECTED]
wrote:
>
> > On 17 Dec, 15:44, Mark Woyna <wo...@[EMAIL PROTECTED]
> wrote:
> > > I guess I'm beating a dead horse here, but I have to question the
> > > sanity of an organization that continues to suffer with an ancient,
> > > buggy piece of software, rather than upgrade to something current.
The
> > > number of issues you've encountered are roughly the same number I
> > > experienced nearly a decade ago. It's time to move on.
>
> > Indeed. I never argued that the choices were sane. Allowing the sw to
> > become so out of date wih the maintenance issues it has IMO is, ahem,
> > sub-optimal. But I have to make it work until they can migrate away
> > from CORBA completely.
>
> Not any more I don't. The system is reverting to the old C++ servers,
> java is being removed from the equation.
>
> > > How is wasting your time
>
> Well, I have been paid, at least.
>
> > > saving your organization any money,
> > > especially when there are plenty of free orbs out there?
>
> > It's not my organisation - I'm a contractor. And I did use jacorb to
> > do most of the development, which was painless by comparison. I did
> > argue for using jacorb but lost that argument. I also lost the
> > argument to change to a much more recent version of Orbix even though
> > we got a VERY reasonable quote from IONA.
>
> And now I've lost the case for CORBA servers in java.
>
> > > As a general
> > > rule of thumb, many organizations take the 'if it isn't broke, don't
> > > fix it' route.
>
> > But it was broken (bugs and lack of robustness in the C++ app code).
> > And using such as ancient unsup****ted buggy mix of technologies they
> > brought me in the migrate them away from all that. Now the servers
> > have been rewritten in java and I am in the process of moving them off
> > CORBA.
>
> It's all off now. If java is ever reintroduced it will be with JMS
> instead of CORBA.
>
> > > They're not going to throw out working software just
> > > for the sake of running the latest and greatest. However, it's
quite
> > > clear here that it *is* broken, and it can't be fixed.
>
> > Yes it was broken but now the servers are rewritten in java things are
> > alot better.
>
> There were a few incidents of Orbix connectivity problems after this
> move. The two events were connected. The conclusion was to remove the
> java work.
>
> > Now theres just the task of moving away from the CORBA. I
> > am in the intermediate stage where we have brand new java code and
> > people need to get that warm comfortable feeling that all the new code
> > is ok.
>
> They never got that warm comfortable feeling.It was running for 22
> days.
>
> > > I know it's not your choice. I hope you're learning something
valuable
> > > as you struggle through this.
>
> > I'm having a great time.
>
> Not any more.
>
> > My java has really improved and I am learning
> > it in the context of java enterprise technologies including JMS.
>
> Well, that's something I gained.
>
> > Also, I think that CORBA is a good technology for the problem at hand,
> > it's the ancient version that is the problem. I did recommend that
> > they stay with CORBA but was overruled.
>
> This was a great pity, IMO.
>
> > The fact is that CORBA skills
> > are rare and expensive something cheaper and more maintainable is
> > needed in terms of finding the people to look after it. It took them
> > ages to find me :-)
>
> > > I wouldn't be that patient. If my
> > > organization saddled me with a crappy piece of code like OW, I'd
have
> > > resigned ages ago.
>
> > I'm a contractor and will be saying goodbye in February :-)
>
> Only 7 working days left to go.
Thanks for the update. I share your pain. You certainly can't be
faulted for not trying.
Since this is a CORBA newsgroup, I'll add this. I've been using Java/
CORBA successfully for over 10 years. We run the worlds largest
options exchange on a CORBA platform, written in Java. We process over
2 billion quotes a day.
I have to imagine that many within your company will point to this
fiasco as a failure of CORBA. I would say it's simply a failure of
management, not technology. The decision to stick with a old,
unsup****ted, buggy product when there are viable alternatives is a
100% management decision. It'll be interesting to see what they do in
the future when they have to integrate with a non-Java application.
Mark
|
