-
1. Re: Global JNDI for Remote EJB Clients
rodakr Nov 20, 2012 1:48 AM (in response to pedrokowalski)You can star to write specification :-)
You might consider take a look on application client
Pozdrawiam
Radek
-
2. Re: Global JNDI for Remote EJB Clients
pedrokowalski Nov 20, 2012 4:00 AM (in response to rodakr)Cześć Radek,
The application client container seems to be like one of those rare animals in Java EE menagerie that noone really uses. Nevertheless, it doesn't seem to be portable but it's rather aimed at particular server vendor, right? So the portabiliby is broken as well.
I am definitely not capable of writing the specification. I am rather curious why it is not standardized, as I don't believe I'm the first one to ask this question. The EG must have taken this under consideration and decided not to create any kind of standardization there, so I am curious: why?
All the best,
Piotr
-
3. Re: Global JNDI for Remote EJB Clients
rodakr Nov 20, 2012 1:03 PM (in response to pedrokowalski)Pozdawiam
You asked about specification:
http://download.oracle.com/otndocs/jcp/javaee-6.0-fr-oth-JSpec/ page 207
I'm surprised you don't like it... :-)
Mabe lot of peoples are just not up to date and they never tried it...
Radek
-
4. Re: Global JNDI for Remote EJB Clients
rodakr Nov 20, 2012 1:07 PM (in response to rodakr)It has one big advantage over all other methods.
You Client to Server code is same as server 2 server.
And should be same for different containers.
If you can live with it, having to change libs depends on container implementation.
-
5. Re: Global JNDI for Remote EJB Clients
pedrokowalski Nov 21, 2012 8:07 AM (in response to pedrokowalski)Hello Radek,
You asked about specification:
http://download.oracle.com/otndocs/jcp/javaee-6.0-fr-oth-JSpec/ page 207
I'm surprised you don't like it... :-)
Uhm, actually I don't recall saying I don't like it :-) I've just said that I am not capable of writing a specification - and this was answer to your "you can always start to write specification" and that the Application Client is rather not a first class citizen in Java EE world (this topic was also discussed in Java EE 7 Expert Group about 2 days ago).
I totally agree - changing the libs is much more comfortable than consulting each app server and changing the JNDI name.
Are you using the app client in real-life projects? Did you have any problem bootstraping it in already established production environment?
Thanks and all the best!
Piotr
-
6. Re: Global JNDI for Remote EJB Clients
rodakr Nov 21, 2012 12:36 PM (in response to pedrokowalski)Hello Piotr
I don't use it, because for my personal opinion any StandAlone/Fat Client has no future.
All Projects I was working / I'm working on, goes to web based solutions.
I used this one time and it worked fine. Instead to spend time how to code you spend time how to configure...
Every body use mobile davices, Ipads, Desktops and using Web solution fit best for this purpose.
Mabe you can take a look on quickstart examples, nice working examples.
Have fun
Radek
-
7. Re: Global JNDI for Remote EJB Clients
wolfc Nov 21, 2012 5:18 PM (in response to pedrokowalski)As to why this is or isn't standardized follow the recent thread on EJB EG users list: http://java.net/projects/ejb-spec/lists/users/archive/2012-11/message/13.
-
8. Re: Global JNDI for Remote EJB Clients
pedrokowalski Nov 22, 2012 3:22 AM (in response to rodakr)As much as I agree with the statement that we should go with web-based - it's not always an option.
For some industry or production use-cases, you can still be locked with thin, but standalone clients.
I will take a look at application client container in more details in the following weekend.
Thanks and best regards,
Piotr
-
9. Re: Global JNDI for Remote EJB Clients
pedrokowalski Nov 22, 2012 3:23 AM (in response to wolfc)Thanks Carlo,
I've just joined the discussion - I think John has the same issue as in this thread.
Best,
Piotr