Just a simple approach to what you are doing that has worked for me in the
past - define the APIs for the various services you require on the client
and obtain a reference to the implementation via a service factory. I used
this technique some time ago when EJBs emerged as 1.0 and were *the* talk
Hello, here goes my problem
ejb.jar generation fails if the relation is one -
sidei.e. there are only abstract accessors to the local interface of the
related bean in one side.
I receive message 'must have attribute "right-ejb"
for ejb:relation'I see these attribute documented nowhere
I
Ara Abrahamian wrote:
> that reduces remote calls and starts a local transaction. You really
> can't forget about client specific needs, I've once tried to abstract
> away client differences for html and wap clients and it really doesn't
> work. So I do think a client-friendly layer is needed. Th
> > - We created stateless session beans for each sub-system or major
> > functionality (goods specification, filing, warehouse and
sub-subsystems
> > like access points to specsheets and things like that).
>
>
> Good. But these are not mapped to client-side use-cases right? I mean,
> they expos
[EMAIL PROTECTED] wrote:
> Hi,
>
> We have done something very similar using Struts where the web sends
> an Action (a Command and a Data) to the EJB Tier. Here we have a
> Command Pattern EJB that analyse this action, do some fine grained
> security check and then call a set of session b
Hi,
We have done something very similar using Struts where the web sends an Action (a
Command and a Data) to the EJB Tier. Here we have a Command Pattern EJB that analyse
this action, do some fine grained security check and then call a set of session beans.
These one talk to entity beans usi
Ara Abrahamian wrote:
> I'm also involved in a project that has a huge swing client. What we've
> done is:
>
> - We created stateless session beans for each sub-system or major
> functionality (goods specification, filing, warehouse and sub-subsystems
> like access points to specsheets and thing
I'm also involved in a project that has a huge swing client. What we've
done is:
- We created stateless session beans for each sub-system or major
functionality (goods specification, filing, warehouse and sub-subsystems
like access points to specsheets and things like that).
- We wrapped these se
