Skip to Content
author's profile photo Former Member
Former Member

ApplicationService SDM deploy-warning about unknown endpoint method

Hello,

i`m just deploying an Application Service and the SDM issues a warning that it cannot find an endpoint method.

Caused by: com.sap.engine.services.ejb3.container.ActionException: Cannot find endpoint method 'checkAntragCreation' with args [long] in class ....ManageAntragInBeanImpl for component ...

for test-purposes i commented out the method and regenerated the stub from scratch like so:

@com.sap.caf.dt.CAFOperation(name = "checkAntragCreation")

@javax.jws.WebMethod(exclude = false, operationName = "checkAntragCreation")

@javax.jws.WebResult(name = "AntragCreateCheckResponse", targetNamespace = "http://....")

public java.lang.Boolean checkAntragCreation(

@javax.jws.WebParam(name = "AntragCreateCheckQuery", targetNamespace = "http://...")

java.lang.Long AntragCreateCheckQuery) {

return (true == false);

}

this didnt help either... any hint?

thanks,

kai

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on May 29, 2008 at 11:01 AM

    public java.lang.Boolean checkAntragCreation(long foo) {

    _location.warningT("checkAntragCreationDUMMY", "foo="+foo);

    return false;

    }

    adding a dummy-method with the non-object core-type long, it deploys successfully.

    do i have to manually box the arguments???

    the arguments are being generated from the ESR, defined by the enterprise services builder.

    thanks,

    kai

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      It seems there are severe problems with autoboxing or generally speaking with core-types vs. object-types.

      simple xsd-types like integer and long used in the enterprise services builder and published into the esr,

      are imported into netweaver developer studio as java-object-types. e.g. java.math.BigInteger and java.lang.Long respectively.

      However the Application Server denies deployment with java.lang.Long method-signatures as it is looking for signatures using the core-type "long".

      furthermore, any service-call on methos using one of those types fails and null-arguments are passed.

      anyone having the same problems or willing to elaborate on this?

      thanks,

      kai

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.