Cross development aspects between different Java EE implementations (especially Glassfish and JBoss) -



Cross development aspects between different Java EE implementations (especially Glassfish and JBoss) -

i working on addon web application existing enterprise application deployed on jboss 4 instance. maintain easy using glassfish application server delivered in netbeans. theprototype, packing every library utilize war file want deploy, hibernate , basic libraries. in future want utilize server delivered libraries , features jndi database connection lookup, session , entity beans , on.

my questions:

are there aspects deploying simple web application in war file packed glassfish on jboss, can hard solve problem? are ejb interfaces accessed in similar way on both implementations? means, able access session bean on jboss when developed code doing on glassfish server? is jndi querying performed similar on both implementations? other aspects?

i have say, experienced in developing simple servlets. know theoretical stuff java ee , ejb , want deeper in this. know nil implementation specific details, question focused on.

if application relatively simple , stick core java ee standards, in theory should see no major issues. might have problems accessing ejbs since there differences in jndi naming.

that beingness said, jboss 4 old. it's j2ee 1.4 compliant, , implements ejb 2.1 specification. new jboss , glassfish servers java ee 6 compliant , implement ejb 3.1 specification. ejb3 much easier use, cannot deploy 3.x ejb 2.x container (the other way around possible). you'll have careful stick what's possible in ejb2 container. example, if want utilize ejb locally (i.e. ejb deployed on same server), under ejb2 have define , implement local interface. under ejb3 it's plenty annotate ejb class @localbean. , don't me started external descriptors required ejb2.

a general rule of thumb utilize same version of same both development , production. example, there might bug functionality in aplication server y version z, not appear in application server version b. application work in a, when deploy y, crash, , you'll have hard time debugging it. if utilize same (version of same) as, there's greater chance you'll find bug during development.

i 1 time had transfer complex application glassfish v2 glassfish v3, , process straightforward.

so, if have utilize jboss 4 target, development under jboss 4. save lot of problem later on. if can utilize latest jboss 7 target, can develop application under latest glassfish 3.x, , work, see no reason doing this.

java-ee jboss glassfish ejb

Comments

Popular posts from this blog

web services - java.lang.NoClassDefFoundError: Could not initialize class net.sf.cglib.proxy.Enhancer -

Accessing MATLAB's unicode strings from C -

javascript - mongodb won't find my schema method in nested container -