Java Connector Architecture and TCP/IP -


so basic question here is: how build tcp interfaces java ee applications? instead of interacting legacy eis, need interact block of tcp/ip ports. ideally, i'd message-driven bean have it's onmessage method invoked incoming tcp request , able respond on same connection.

jca seems general enough capable of within java ee environment. developing custom connector appropriate technique integrating inbound/outbound tcp interfaces in java enterprise ecosystem?


as far i've tried far: we're utilizing lifecycle module starts kicking off number of tcp listeners; invokes message-driven bean calls business method, , returns on same tcp stream. working alright, lifecycle support in application server (glassfish) feels has been added afterthought. so, jca seems first-class solution sort of problem , seems enable communicate on tcp.

however, initial research we've conducted, seem connector architecture 'targeted' towards legacy information systems, not generalized tcp communication. so, question rendered: people using custom jca's integrate tcp/ip java ee applications -- or there better technique accepting tcp connections ejbs?

mxbeans , jca (mxbeans easier, have implemented both) need 2 things start/stop , possibly rely on other mxbeans/jca/jndi carry out services w/ appserver generating needed proxies you.

real application: hacked tomcat w/ nio acceptor can trap connections on 80+443ports , still use web-server normally. followed full platform (incl. own (re)deployer) manage sessions/messages , jazz.


Comments

Popular posts from this blog

java - SNMP4J General Variable Binding Error -

windows - Python Service Installation - "Could not find PythonClass entry" -

Determine if a XmlNode is empty or null in C#? -