No Sir. I am not asking to modify the success message.

What I am saying is ... the blue success message alert which appears and
gets displayed on "return success" goes off all on its own after a few
seconds by default. This is not vanishing on its own. It is staying
displayed. Even if 'X' is clicked, it's still not closing. In other cases
it's working fine. But in the above case it is not working. I am unable to
send you the screenshot in this mail because its text only mail format.

Even I have a java process where I am inserting rows in many entities one
after the other. In that case too ... It is stucking.

My question is why it is staying stuck and not closing on its own. I am not
asking for a customized success message.

regards
Avijit

On Sat, Jul 30, 2022 at 10:26 PM Nicolas Malin <[email protected]>
wrote:

> This is normal process when you use entity-auto.
>
> If you want a dedicate message or no message, override you service by an
> other
>
>
> <service name="createBookForUser" engine="groovy"...>
>   <implement service="createBook"/>
>
> BookServices.groovy:
>
> def createBookForUser() {
>    run service: 'createBook', with: parameters
>    return success("My message")
> //or
> //   return success()
> }
>
> Nicolas
>
> On 30/07/2022 05:21, Avijit Bose wrote:
>
> Hello,
>
> 1. After completion of a db row creation, the blue success message (alert)
> is showing but gets stuck. It does not 'goes off' of its own. Clicking the
> close (X) button does not work. I am using a simple create service method
> to create a single row in db.
>
> *****************
> <service name="createBook" default-entity-name="smsBookMaster"
> engine="entity-auto" invoke="create" auth="true">
> <description>Create New Book</description>
> <auto-attributes include="pk" mode="OUT" optional="false"/>
> <auto-attributes include="nonpk" mode="IN" optional="true"/>
>     </service>
> *****************
>
> 2. It also happens when creating many rows in many database consecutively
> in a single process.
>
> No error message etc.
>
> Pls let me know why this happens?
>
>
>
>

Reply via email to