Migrating from one vendor to another is not an easy task.
There may exist number of reasons to migrate from
Jboss to Glassfish.
We are expert in both, Jboss and Glassfish.
If you are considering migration from Jboss to
glassfish application server, than consult us
to resolve migration issues. i.e Obviously classes from Jboss
proprietary API will not be supported in Glassfish and if
you have used any proprietary annotation from Jboss ,
than that ejb will not even compile from your favorite IDE.
|
Glassfish v3 is scheduled to be released in
this November. GFv3 is based on OSGi while
Jboss 5's kernel is based on JMX.
GFv3 supports JavaEE 6; Jboss 5 supports Java EE 5.
And important thing is that Glasfish is a reference
implementation of Java EE 5.
|
We are here to find and apply alternatives for these situations.
Because, it is possible that Some times you may not find one to
one correspondence between Jboss and Glassfish and you are
in trouble. There is a possibility of application architecture
conflicts. i.e. For desktop client based applications, ejb lookup
is different. The way the administration is performed is completely
different. Resolving this kind of issues is not as easy as getting
‘hello world’ sample application up and running on glassfish or Jboss.
For that you may need an expert to perform this task. Hire us to
perform this task for your project.
