New Posts New Posts RSS Feed: Why only a single nested WsQuery per Entity?
  FAQ FAQ  Forum Search   Calendar   Register Register  Login Login

Why only a single nested WsQuery per Entity?
 Post Reply Post Reply
Author
  Share Topic Share Topic  Topic Search Topic Search  Topic Options Topic Options
Customer View Drop Down
Senior Member
Senior Member
Avatar
User Submitted Questions to Support

Joined: 30-May-2007
Location: United States
Posts: 260 		Post Options Post Options   Quote Customer Quote  Post ReplyReply Direct Link To This Post Topic: Why only a single nested WsQuery per Entity?
    Posted: 16-Jul-2007 at 2:29pm

My question is with the ObjectMapper tool mapped to a WSDL file (WebService).

 

 

Let's say forexample that we have an OrderService with methods:

 

findOrdersByCustomer(FindByCustomerRequest)

findOrdersBySalesRepresentative(FindBySalesRepresentativeRequest)

findCustomerByOrder(FindByOrderRequest)

 

With the "Add Unmapped Web Service Methods" tool I can select all methods, but only 1 method is allowed for each "Base" entity at the time?

 

That is, the tool generates

 

the Orders class has a WsQuery with a constructor for FindByCustomerRequest

the Customer class has a WsQuery with a constructor for FindByOrderRequest

 

I would expect the Orders class to also have a WsQuery for the second findOrdersBySalesRepresentative method. It seems that the tool always selects the FIRST checked method in the list, then discards all other selected methods with the equal return value.
Back to Top
IdeaBlade View Drop Down
Moderator Group
Moderator Group
Avatar

Joined: 30-May-2007
Location: United States
Posts: 353 		Post Options Post Options   Quote IdeaBlade Quote  Post ReplyReply Direct Link To This Post Posted: 16-Jul-2007 at 2:30pm

The problem is due to a known limitation.  We allow for only a single WsQuery nested class to be created within an Entity class, so the first checked method will be the only method created.  The use of only a single nested WsQuery per Entity was intentional, and follows our implementation of stored procedure backed entities.  The good news is that these nested classes are really just helper classes defined to make constructing a WsQuery easier, and are not required to be used.

 There are a couple workarounds to look at:

 1) Since the *DataRow classes are partial, you can write your own additional WsQueryX nested class, using the existing class as a template so that you only need to change the parameter and execute information.  You don’t need to make the class nested if you prefer not to, since the nesting is just a convenience not a requirement.

 2) Call the base IdeaBlade.Persistence.WS.WsQuery class directly.  Here again you can consult an existing nested class to see how it constructs the base WsQuery.  Getting the constructor right is the primary difficulty here.  You’ll want to use either:

public WsQuery(String pServiceName, String pMethodName, Type pEntityType, WsProxyType pProxyType) or

public WsQuery(Type pClientProxyType, String pMethodName, Type pEntityType)  - preferred

 

 
Back to Top
 Post Reply Post Reply

Forum Jump Forum Permissions View Drop Down