All that class foes is change namespace URIs. You can, in 2.1, either change
to the new class (and keep using xfire-compatible) uri's, or you can inherit
from its base class.
On Sat, Mar 1, 2008 at 7:34 PM, tog <[EMAIL PROTECTED]> wrote:
> On Sun, Mar 2, 2008 at 1:02 AM, Benson Margulies <[EMAIL PROTECTED]>
> wrote:
> > XFireCompatibilityServiceConfiguration. The javadoc claims to say so,
> did it
> > not come through?
>
> humm, no there is nothing about aegis in the javadoc ;-) I could not
> find it for 2.0.3 either (btw I am looking in docs/api)
>
> >
> > Also, I don't see how that has anything to do with operation tuning.
> All
> > it's ever done is to change namespace URIs.
> >
> Here is what I am doing with it (and still expect from 2.1 :-))
>
> public class GroovyConfiguration extends AegisServiceConfiguration {
> public Boolean isOperation(Method m) {
>
> try {
> Method method =
> GroovyObject.class.getMethod(m.getName(),
> m.getParameterTypes());
> return false;
> } catch (SecurityException e) {
> // TODO Auto-generated catch block
> e.printStackTrace();
> return false;
> } catch (NoSuchMethodException e) {
> // TODO Auto-generated catch block
> return super.isOperation(m);
> }
> }
>
> public String getAction(OperationInfo op, Method m){
> return op.getName().getLocalPart();
> }
>
> }
>
> >
>
