[#GALAXY-111] Add more Policies for Mule 1 configurations

Galaxy

Add more Policies for Mule 1 configurations

Created: 16/Feb/08 03:42 PM Updated: 17/Feb/08 05:17 PM

Component/s:

Integration: Mule 1

Affects Version/s:

1.0-beta-1

Fix Version/s:

1.0-beta-2

Time Tracking:

Not Specified

Labels:
User impact:	Medium

Description

« Hide

Right now we only have RequireSslPolicy. I can think ome others such as JMX enforcement, disabling Client Remote dispatching, using only JNDI datasources and Connection Factories.

All

Comments

Work Log

Change History

Transitions

FishEye

Sort Order:

[ Permlink | « Hide ]

Dan Diephouse added a comment - 16/Feb/08 07:07 PM

I've been thinking and I think these need to really be applied at the runtime level. One can always hack around the config policies with the Mule API, then people are back to square one.

[ Permlink | « Hide ]

Ross Mason added a comment - 17/Feb/08 09:52 AM

Yeah, I remember saying the same thing. In Mule 2, it would be pretty easy to lock out the API so you you can only configure from Xml. Also, applying policies at run time will be much harder for frameworks that we do not have so much control over. I think it's fine to offer esign time policies even as configuration guidelines

[ Permlink | « Hide ]

Ross Mason added a comment - 17/Feb/08 05:16 PM

Added some more policies and fixed the autogenerated docs: r420