SAP Netweaver Gateway Java Library and Property Set_As_Title

Hi Nir

I came across FC_KeepInContent="false" when setting up the OData Channel - Subscription and Push Flow http://bit.ly/skVFJ0. I think this is a good use case. Users subscribe to entity changes on their devices. The notification I create in my mobile app uses the atom:title and looks like  "X changes to entity Y", this value doesn't add value if it was to be also included in the content, in fact it would be an unwanted overhead.

If it helps my findings FC_KeepInContent="false" is supported in most OData browsers and libraries, currently datajs was the only method not supporting it and this is probably more to do with how this library is used.

If you are looking for more things, last night I found an anomaly with the way the generated proxy handles associations.

In my service the entity Supplier has a 0:N association with Product, the code generated in the proxy is trying to return a Supplier

 // Supplier navigation properties
  
 /**
  * Navigation to Products
  * @return Supplier
  * @throws ProxyException
  */
 public Supplier Products() throws ProxyException
 {
  Supplier result = null;
  
  String url = this.atomEntry.getAtomId() + "/" + "Products";
  String response = ZNWGWSAMPService.getInstance().getResponseString(url);
  try {
      AtomEntry atomEntry =  SDPHelper.fromXmlToAtomEntry(response);
      result = new Supplier (atomEntry);
  } catch (ParserException e) {
   throw new ProxyException("ParserException thrown in Products", e);
  } 
        return result;
 }
.

when it should be returning a list of Products, something like

 public List<Product> Products() throws ProxyException 
 {
  List<Product> list  = new LinkedList<Product>();
  
  String url = this.atomEntry.getAtomId() + "/" + "Products";
  String response = ZNWGWSAMPService.getInstance().getResponseString(url);
  try {
   AtomFeed feed = SDPHelper.fromXmlToAtomFeed(response);
   
   for (AtomEntry atomEntry : feed.getEntries())
   {
    list.add(new Product(atomEntry));
   }
         
  } catch (ParserException e) {
   throw new ProxyException("ParserException thrown in Products", e);
  } 
        return list;
 }

I hope you don't mind me highlighting my findings, I really like the generated proxies and think they show a lot of promise.

Cheers

JSP