Hi Lahiru, Thank you for the reply. I understand what you say. But I have some questions.
What do you suggest, is it fine to keep the current implementation of above method which returns the first child always or should it be changed? Why isn't there a method to get deployment description by name, which is more obvious and clear than current implementation? Thank you. -- Bhathiya On Tue, Jun 26, 2012 at 7:37 PM, Lahiru Gunathilake <[email protected]>wrote: > Hi Bhathiya, > > There could be usecases, but very likely rare.. If users wants to change > something we recommend them not to create an application descriptor for > each and every configuratin change in its application descriptor. So the > recommended way is it have one application descriptor and change the > configuration dynamically by putting required value in the request > header(WorkflowExectutionContextHeader). > > So we give high precedence to incoming request scheduling configuration, so > if you change any value there in the request we simply ignore the value you > have in the registry and use the header configuration for that particular > request. > > Hope this helps ! > > Lahiru > On Tue, Jun 26, 2012 at 9:26 AM, Bhathiya Jayasekara > <[email protected]>wrote: > > > Hi devs, > > > > I have a confusion about "*getDeploymentDescription(String serviceId, > > String hostId)" *method in AiravataJCRRegistry.java. In this method, > giving > > a Service_Id and a Host_Id we can get a Application Description. (It > > returns the first child if there are multiples) > > > > My question is aren't there any use cases where a particular Service and > a > > Host can have multiple Application Descriptions? If the answer is No, > > everything is fine, otherwise it is confusing. > > > > Thank you. > > > > -- Bhathiya > > > > > > -- > System Analyst Programmer > PTI Lab > Indiana University > -- -Bhathiya Jayasekara- http://www.google.com/profiles/tobhathiyaj http://www.facebook.com/#!/bhathiyaj1
