Sumit,
Sorry for the delay, I was not nuch available these last days. I would suggest
to
1. Introduce a service interface definition same than createCommunicationEventRole but without the permission check, description
would be "Create a Communication Event Role with or w/o permission check."
2. To use it in createCommunicationEventRole adding the permission check.
3. To create a new service definition (say createCommunicationEventRoleWithoutPermissionCheck) with same interface, same
implementation (location="org/ofbiz/party/communication/CommunicationEventServices.xml" invoke="createCommunicationEventRole") but
without permission check
4. Then to use this new services in Contact Us and everywhere the same need
appears.
Jacques
From: "Sumit Pandit" <[EMAIL PROTECTED]>
Hello Jacques, Hans
I have checked it by remove the permission check line from the service
definition. Here i found it works well.
Here i requested that it is require to remove the line from the service,
if not remove following code will block :
1) Contact us (as already known)
2) In new implementation of profile when we add the code for send email notification on create profile then it causes the same
error
and some more ...
What is the best possible solution of it, It is needed to fix urgently since
my customized application is blocked due to it.
--
Thanks and Regards
Sumit Pandit.
HotWaxMedia, Inc
http://www.hotwaxmedia.com
On Aug 26, 2008, at 2:45 PM, Jacques Le Roux wrote:
There is a contradiction between definition where
partyCommunicationEventPermissionCheck" main-action="UPDATE"/> is used
<service name="createCommunicationEventRole" engine="simple"
location="org/ofbiz/party/communication/ CommunicationEventServices.xml" invoke="createCommunicationEventRole"
auth="true">
<description>Create a Communication Event Role</description>
<permission-service service- name="partyCommunicationEventPermissionCheck"
main-action="UPDATE"/>
<auto-attributes entity-name="CommunicationEventRole" include="pk" mode="IN"
optional="false"/>
<auto-attributes entity-name="CommunicationEventRole" include="nonpk" mode="IN"
optional="true"/>
</service>
And a change done (r685581) in implemtation to allow everybody to use it
<entity-one entity-name="UserLogin" value-name="sysUserLogin">
<field-map field-name="userLoginId" value="system"/>
</entity-one>
I guess we should change the definition...
Jacques
From: "Sneha Chaturvedi" <[EMAIL PROTECTED]>
Hello all,
I visited http://demo.hotwaxmedia.com/ecommerce/
Created a new profile
Went to contact us
but when i send the content I am getting error for permission.
so i think no permission is set for the user profile created through ecommerce. I think some implementation is missing in
create profile section.
It shows me the error :
Security Error: To run createCommunicationEventRole you must have the one of the following permissions: PARTYMGR_UPDATE,
PARTYMGR_ADMIN, PARTYMGR_CME_UPDATE, PARTYMGR_CME_ADMIN]
What should be done in this case.
Thanks in advance
--
Sneha
