You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Thilina Gunarathne (JIRA)" <ji...@apache.org> on 2006/08/10 08:19:14 UTC
[jira] Commented: (AXIS2-996) Constants.Configuration.FORCE_MIME
does not exist
[ http://issues.apache.org/jira/browse/AXIS2-996?page=comments#action_12427113 ]
Thilina Gunarathne commented on AXIS2-996:
------------------------------------------
Yes.. That constant was removed prior to the 1.0 release. Now we by defualt FORCE_MIME if MTOM is enabled.
We need to remove that from the MTOM Guide.
> Constants.Configuration.FORCE_MIME does not exist
> -------------------------------------------------
>
> Key: AXIS2-996
> URL: http://issues.apache.org/jira/browse/AXIS2-996
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Bug
> Affects Versions: 1.0
> Environment: java 5 , linux
> Reporter: robert lazarski
>
> The mtom guide states:
> But due considering the policy assertions, there may be a policy saying, all the request should be optimized eventhough there are any optimized contents. To support this phenomenon there is an entry called "forced mime" which has to be set as
> ...
> options.setProperty(Constants.Configuration.FORCE_MIME, Constants.VALUE_TRUE);
> However, there is no such constant in the latest svn .
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org