IBM SG24-6320-00 Manuel D’Utilisation
6320ch_DEV_post_migration.fm
Draft Document for Review July 28, 2004 7:33 pm
130
Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide
In WebSphere Commerce Suite V5.1, fine-grained resource control was
implemented programatically using the following methods:
implemented programatically using the following methods:
public Long[] getResourceOwners() throws ECException
public boolean checkPermission() throws ECException
public boolean checkPermission() throws ECException
These methods became deprecated in WebSphere Commerce Suite V5.4.
Instead the fine-grained resource control has become policy based, combined
with the use of the following methods:
Instead the fine-grained resource control has become policy based, combined
with the use of the following methods:
public AccessVector getResources() throws ECException
public void checkResourcePermission() throws ECException
public void checkResourcePermission() throws ECException
Figure 8-1 on page 131 shows the method call sequence for invoking commands
in the WebSphere Commerce V5.6 command framework.
in the WebSphere Commerce V5.6 command framework.
8.2.2 Command parameter validation
The following method was used in controller, view and task commands in
WebSphere Commerce Suite V5.1 to perform server side validation of the
parameters passed to a command:
WebSphere Commerce Suite V5.1 to perform server side validation of the
parameters passed to a command:
protected void checkParameters() throws ECException
This method was replaced in WebSphere Commerce Suite V5.4 with the
following method, deprecating the use of the
following method, deprecating the use of the
checkParameters
method:
public void validateParameters() throws ECException
The method is used for the same purpose with the only difference that where
WebSphere Commerce Suite V5.1, the
WebSphere Commerce Suite V5.1, the
checkParameters
method was called
from within the
performExecute
method, the
validateParameters
method is
called from the command framework.
Since
validateParameters
is called from the command framework, you should
not replace calls in the
performExecute
method to the
checkParameters
method
with calls to
validateParameters
. The custom code should thus not contain any
references to its own
validateParameters
method.
Figure 8-1 on page 131 shows the method call sequence for invoking commands
in the WebSphere Commerce V5.6 command framework.
in the WebSphere Commerce V5.6 command framework.
Note: Refer to the WebSphere Commerce InfoCenter for more details at the
following URL:
following URL: