I'm not quite sure I'm following you as to which has the extra fields, your input map or the interface.
I'm thinking your input map has the extra fields otherwise the extra fields in the interface would be optional, or you would likely end up with inconsistent result from the interface. So, assuming it's your input map and you would only be coming across this situation in simple-method because the screens->service picks the fields from context and java->service has you specify the map specifically. So, if you're running this from simple-methods...you're solution, I believe, is the following <set-service-fields map-name="myInputMap" service-name="myService" to-map-name="inputMap"/> <call-service service-name="myService" in-map-name="inputMap"/> Does that help? --- Jonathon -- Improov <[EMAIL PROTECTED]> wrote: > I can't find any usage of ContextAccessor.remove(MethodContext) in > Minilang's source codes at > src/org/ofbiz/minilang/method/envops . > > Shall I add an option to <clear-field> that will trigger a > ContextAccessor.remove() rather than a > ContextAccessor.put() that merely replaces a field with null? > > I'm doing a custom service that <implements> an existing service in > OFBiz, and I need to trim away > the extra input fields before putting them to the existing service. > > Jonathon >
