I understand why a lot of companies like an all in one solution. It is
easy, convenient, and usually makes integration smoother. Like others have
mentioned, it usually means better support. However, in my experience,
I've seen CTO's, architects and whatnot steer towards the all in one
solution
The app server has been tested against the database. If you are using
WebSphere with DB2, you can get support. If you use WebSphere with Oracle,
then you are on your own. It is not about having the best technical
solution. It is all about maintenance. How quickly can the problem be
solved. Many com
Most of those online banking solutions are still backed by COBOL
code
I know that the college that I went to was still teaching COBOL 5
years ago
On May 4, 1:09 pm, Robert Casto wrote:
> I would rather go with an ALL solution than try and piece everything
> together if that were the cho
What is the technical benefit of have an app server and database from the
same vendor?
Lloyd
On Mon, May 4, 2009 at 1:09 PM, Robert Casto wrote:
> I would rather go with an ALL solution than try and piece everything
> together if that were the choice. If you use SOA, you can get around some of
I would rather go with an ALL solution than try and piece everything
together if that were the choice. If you use SOA, you can get around some of
these problems but then you run into islands of technology and need more
resources to deal with it. Having a system that is all similar lets you use
your
On May 4, 11:29 am, Jess Holle wrote:
> Having all eggs in one basket is a double-edged sword...
True and so is piecing everything together from separate vendors.
There are no cure alls - we can only make optimum choices based upon
where we are at and what we believe the future needs and holds.
Having all eggs in one basket is a double-edged sword...
--
Jess Holle
Donald Bell wrote:
> On May 2, 7:19 am, IngoF wrote:
>
>> In the end they have a chain starting with the IBM mainframe right
>> down to the individual developer workplace running Rational
>> Application Developer.
>> And t
On May 2, 7:19 am, IngoF wrote:
> In the end they have a chain starting with the IBM mainframe right
> down to the individual developer workplace running Rational
> Application Developer.
> And that's the part that starts bothering me, haha ;)
What bothers you with having an end to end solution?
Is there anything wrong with mvn dependency:tree?
--
Marcelo Morales
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "The
Java Posse" group.
To post to this group, send email to javaposse@googlegroups.com
To unsubs
I once wrote a maven plugin which represents the dependencies as a UML
diagram, exported to http://en.wikipedia.org/wiki/
XML_Metadata_Interchange">XMI. XMI was nice for me because I could
then analyze the dependencies in UML tools that can read XMI (I used
magic draw).
Don't know if this plugin
Nice when an OSS work is appreciated :)
http://www.softwaresecretweapons.com/jspwiki/maven-pom-dependencies-in-graphml
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "The
Java Posse" group.
To post to this group, se
11 matches
Mail list logo
