Friday May 11, 2007 Update: My JavaONE session TS-3559 about JPA, EJB3 and RIAs is still full, but...
there should be no problem to attend. In general you have only to wait for the already enrolled attendees.My session's abstract:
- Loose coupling and interactivity
- Data synchronization
- Transactional approaches
- Rich Domain Objects and Databinding (BeansBinding)
- Using WebBeans/GlassfishV3 for desktop components
- Hybrid Components (which can be deployed to clients as well as into an container)
- Architectural Patterns and approaches
Enjoy the remaining JavaONE :-) Gesendet von admin [JavaONE 2007] ( May 11, 2007 05:04 PM ) Permalink | Kommentare [2]
Senden Sie einen Kommentar:
Hi!
I've just read your TS-3559 but I have some concerns and doubts about this architecture proposal and its compatibility with SOA. For example,
1) How can I develop a fat client if my business model is only available through webservices?
2) What is the role of the gateways (implemented as SFSB)?
3) What about the size of the domain objects if they also contain behaviour?
4) What is the difference between a service (implemented with a web service) and a business façade/gateway?
In any case, your presentation is very interesting and I'm sure we'll use (in my company) some of the ideas you expose to improve the architecture we are currently designing.
Thanks for your help,
JMB
Gesendet von jmbeas am June 09, 2007 at 01:39 AM CEST #
Hi JMB :-),
I would try to answer your questions as comment - but it's hard:
1) How can I develop a fat client if my business model is only available
through webservices?
I did it in one project. I had Domain Objects with local store. WebServices were coarse grained and provided domain object unrelated services.
You can use the local store as a cache, or connect with central database. But data replication could be a challenge. I always try to solve the problems from the business/use case perspective.
2) What is the role of the gateways (implemented as SFSB)?
They implement instance-independent logic (update, delete all, copy etc.) and expose directly JPA-domain entities.
3) What about the size of the domain objects if they also contain behaviour?
Never was a problem. In one of my projects we had about 300 Domain Objects with deep inheritance - and it is faster than classic Java EE architecture.
4) What is the difference between a service (implemented with a web service)
and a business façade/gateway?
Facade hides domain objects, a gateway exposes them. So a facade would transform domain objects into value objects...
You were in my session? We had a long discussion after the session.
In any case, your presentation is very interesting and I'm sure we'll
use (in my company) some of the ideas you expose to improve the architecture we
are currently designing.
Thank you very much. I like it - because it is lean and almost no additional libraries, frameworks etc. are needed.
regards,
adam
Gesendet von Adam Bien am June 09, 2007 at 12:58 PM CEST #