Agree. Please make sure to explain this in jira so that it will help everyone if others also come across similar error.
On Wed, Jul 25, 2012 at 10:01 AM, Amila Maha Arachchi <ami...@wso2.com>wrote: > What I am saying is theres no bug here. Once we enable message-relay for > all the content types we cannot even log in to ESB. If we want to use the > management console of ESB, then we need to engage the relay module > globally. Once it is done, you can access the ESB management console as > normal. Once this is done all the admin services messages are built AFAIU. > So, if we need to do the same for hidden services we need to set > <includeHiddenServices> to true. > > In this jira, PackageInfoService is not an admin service, but a hidden > service. Once you set the above property to true, there is no issue. > > So, I am going to resolve this issue. > > Regards, > AmilaM. > > On Wed, Jul 25, 2012 at 7:51 AM, Charitha Kankanamge <chari...@wso2.com>wrote: > >> You may find this useful - >> http://wso2.org/project/esb/java/4.0.0/docs/message_relay.html >> >> >> On Wednesday, July 25, 2012, Pradeep Fernando wrote: >> >>> >>> >>> On Wed, Jul 25, 2012 at 6:57 AM, Amila Maha Arachchi <ami...@wso2.com>wrote: >>> >>>> Thanks Supun for the info. >>>> >>>> BTW, I got to know that this kind of a configuration is practical. And >>>> we can skip hidden services from message-relay by engaging the relay module >>>> and setting the <includeHiddenService> >>> >>> >>> So it builds the message using a Handler after the initial wrap during >>> the message builder (?) >>> >>> --Pradeep >>> >>> >> >> -- >> Charitha Kankanamge >> cell: +94 718 359 265 >> blog: http://charithaka.blogspot.com <http://wso2.com> >> >> > > > -- > *Amila Maharachchi* > Technical Lead > Member, Management Committee - Cloud & Platform TG > WSO2, Inc.; http://wso2.com > > Blog: http://maharachchi.blogspot.com > Mobile: +94719371446 > > >
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
