Encountering error while following Apigee tutorial

Google Cloud Apigee
1

Hi,

I am following the tutorial

http://apigee.com/docs/api-services/tutorials/part-1-create-your-api-xml.

When I get to step 4.9, I encounter the following error:

Server Error.

Error occurred while validation of bean default.xml. Reason: - Schema 
validation failed. Cause : unexpected element (uri:"", local:"ProxyEndPoint"). Expected elements are <{}APIProxy>,<{}APIProxyRevisions>,<{}AccessControl>,<{}AccessEntity>,<{}Admin>,<{}Alert>,<{}Allow>,....

Here is my proxies\default.xml

<ProxyEndPoint name="default">
    <Flows>
        <Flow name="forecast">
            <Condition>
             (proxy.pathsuffix MatchesPath "/forecastrss") and 
                  (request.verb = "GET")
            </Condition>
        </Flow>
    </Flows>
    <HTTPProxyConnection>
        <VirtualHost>default</VirtualHost>
        <BasePath>/v1/weatherxml</BasePath>
    </HTTPProxyConnection>
    <RouteRule name="default">
        <TargetEndpoint>default</TargetEndpoint>
    </RouteRule>
</ProxyEndPoint>

Here is my targets\default.xml

<TargetEndpoint name="default">
    <HTTPTargetConnection>
        <URL>http://weather.yahooapis.com</URL>
    </HTTPTargetConnection>
</TargetEndpoint>

Please help.

Regards,

Ritwik

2

Hi @ritwik_chatterjee

You are getting this error because of case sensitivity. Change “ProxyEndPoint” to “ProxyEndpoint”, i.e. change the “P” of Point to a “p” in your first and last lines of your proxies\default.xml and you should be able to save and deploy.

3

Thanks. I knew I was making a silly mistake, but was not able to figure it out myself.

4

You’re very welcome and thank you for using the tutorial and asking your question. I’m sure others will benefit from this as well.

5

hey, i just want to share my fixed case ,i had the same error when deployment a proxy with Monitization Limit Check policy, in the logs i found this “Marshal failure javax.xml.bind.UnmarshalException: unexpected element (uri:”“, local:“MonetizationLimitsCheck”)”

we have 6 message processers so i found out that not all of them has monetization installed, so i installed the monetization on all missing message processors and issue fixed and the deployment worked.

1 Like
6

Thanks, this will be helpful!