The drawback of such services with engine="entity-auto" is that you expose the users to crude error messages, when some of the required parameters aren't incorporated in the POST action.
Pierre Smits *ORRTIZ.COM <http://www.orrtiz.com>* Services & Solutions for Cloud- Based Manufacturing, Professional Services and Retail & Trade http://www.orrtiz.com On Wed, Oct 1, 2014 at 3:50 PM, Jacopo Cappellato < [email protected]> wrote: > > On Oct 1, 2014, at 3:37 PM, [email protected] wrote: > > > I am just guessing, but maybe this does the actual work? > > engine="entity-auto" invoke="create" > > default-entity-name="UserLoginSecurityGroup" > > This can actually look mysterious! When you see a service with > engine="entity-auto" then it means that there is no implementation for it > because it is handled by the framework as a CRUD service. > In the above example: > > engine="entity-auto" > invoke="create" > default-entity-name="UserLoginSecurityGroup" > > means that a "create" operation is performed on the UserLoginSecurityGroup > entity. > > I hope it helps, > > Jacopo > > > > > > As I said I am still new and learning, so if this does add the record I > am > > sorry for asking a dumb question. > > I know the whole XML auto stuff confuses me. I see screens using it to > get > > field data (or more precicly screens created using it). It seems very > clean > > and simple, but not completely understanding it it seems mystical. i > usually > > end up adding the fields and saying hidden etc to get the screen the way > I > > want. SO far I have not ran into an actual service in the xml in service > > def, so I guess maybe that threw me off. In any case the java I create > does > > the job. I was just more curious than anything. > > > > > > > > ----- > > Joel Fradkin > > -- > > View this message in context: > http://ofbiz.135035.n4.nabble.com/adding-a-user-login-to-a-security-group-tp4656265p4656324.html > > Sent from the OFBiz - User mailing list archive at Nabble.com. > >
