₦airaland Forum

tales by moonlight

very funny

^^

see applications

haha

who is 30

^^ hmm . so u got a call from a woman

sighs

me too

indeed

this thread still dey here

make we leave am there na

Pweety4me:
[color=#550077]Mannylex[/color]

shuo

Pweety4me:
[color=#550077]I 2 fine 2 serious abi wetin? [/color]

u are never serious . remember wetin u do kunbee last yr

pweety u know as much as i do that you are not serious

pweety the joker

looks like you didn't see my post

WackyJ1:
Season 2 is next year. This is a prequel telling the story before season 1

a teaser to wet our appetite for season 2

unfortunately i don't have any side projects right now but just continue learning and very soon you will land a job and become a very good developer

@webmonkey

Is it compulsory that you most deploy the app in a J2EE container and use MQ( i know some companies force these kinds of things down developer's throats ).

If you have more leeway on the architecture of the system. Start looking at Spring integration ASAP as suggested by logica.

You will be ready with a working application within a couple of hours combining the JDBC adapter with a JMS or Webservice Gateway

A couple of observations.

1. You shouldn't be establishing db connections for every request like the code in DatabaseCon .You need to use a db connection pool

2. Why don't you look into a framework like spring to better organise your application. You can use the JDBC interface provided there and this will even manage db connections for you

3. When you say you want to be able to connect to different branches and make blance enquiry etc. Will you be doing this within the organisation . i.e the bank or will you be accessing from outside say as a customer?

4. If you are doing webservice i will advice like logica to use CXF. Look into using CXF with Maven via the CXF plugin and all the boilerplate code, wsdl etc will be auto-generated for you.

5. What do you need the Trigger for. A trigger that fires on Insert of every record will seriously slow down the Flexcube banking app. you probably don't wanna do this

". . . making the critical assumption that every single consumer of the exposed queue should understand proprietary JMS communication protocol."

This is exactly the fundamental disadvantage of sending Objects in JMS when working in a multilanguage scenerio and why SOAP might probably be an option.

AMPQ on the other hand can interoperate with different languagues since it is a wire level protocol and relies on bytes of data

yea more people especially in the financial space are adopting AMPQ. its fast and efficent. Have a look at Apache Qpid and RabbitMQ ( reference implementation in java)

java will typically "automatically" serialise an object that is either getting persisted or that will be sent over the wire.

That is why it is mandatory to implement serialisable if you use Hibernate or ObjectMessage for example

JMS uses TCP/IP socket connections not IIOP

Sending objects over the wire is even not very efficient because of the cost incurred doing serialisation and stuff

Coming back to your previous point. While SOAP via JMS is a viable solution. All am saying is that SOAP is not really necessary in this scenario.

JMS Messages composed of  simple objects or better still bytes of data is more than enough.

No JMS uses Java's inbuilt serialisation it doesn't care about serialisation it just routes messages.