1 of 1 people found this helpful
My suggestion would be to use application composition leveraging SCA bindings.
I would create different front applications (depending on the security considerations) and then delegate to a common application where all the logic further from authentication/authorization would be handled.
In this example, I would have User A consuming a secure endpoint/binding and User B consuming an unsecure binding. Both apps would call for common logic a third app. The good thing about SCA binding is that the cost of the call is very small (it is a local java call unless clustered is selected in pre SY 2.0).
I hope it helps,
A good suggestion, thank you :-)
Does it have to be three separate applications? Would it work if all these components are implemented within the same composite?
Yes, definitely if will work the same. As long as the lemme is the same, they can be implemented in the same application.
Yes, definitely it will work the same. As long as the lifecycle is the same, they can be implemented in the same application. And even the lifecycle constraint depends also on the packaging, whether is as multiple .jar deployment units or everything in an .ear deployment unit.