Won't this violate the FE-BE separation architecture? Azeez
On Fri, Sep 24, 2010 at 8:23 AM, Milinda Pathirage <[email protected]> wrote: > Hi Sameera, > > We discussed this on IRC yesterday.Plan is to come up with a proxy bundle > which holds all the JSPs deployed with Human Task archives. This proxy > bundle will be a UI bundle which expose a seperate child context under > carbon context (for example: carbon/foo). Once you deploy a human task > archive we modify that bundle programetically and put the JSP files in HT > archive to that bundle and refresh the bundle. > > Is this a good solution? > > Otherwise we'll have to write custom registry handler which makes JSP > available under 'carbon' context. > > Please feel free to comment on this. > > Thanks > Milinda > > > On Thu, Sep 23, 2010 at 10:31 PM, Sameera Jayasoma <[email protected]>wrote: > >> Hi Sanjaya >> >> On Thu, Sep 23, 2010 at 2:53 PM, Sanjaya Vithanagama >> <[email protected]>wrote: >> >>> Hi All, >>> >>> In the human-task implementation, we need to allow the user to include a >>> custom jsp page with the human task package which is uploaded. We add the >>> uploaded human-task (zip)package to the registry. >>> >>> Once the task instances are created for the uploaded task definition, in >>> the task view page we need to include the user uploaded jsp page. [The >>> purpose of this is to render the task creation request message which has >>> the data required for task operator to perform the task] >>> >>> Is there a way to add the user uploaded jsp page (which resides in the >>> zip package added to the registry) to the application context of the >>> human-task ui bundle? Then we can include the custom jsp in the task view >>> page using a <jsp:include>. >>> >> >> With the current implementation of the Carbon UI framework we cannot do >> this. All the UI resources belongs to a Component should reside in its UI >> bundle's classpath. >> >> If you want to load UI resources reside in the registry, we need to >> improve the Carbon-UI framework to support this feature. >> >> Thanks >> Sameera. >> >>> >>> Regards, >>> SanjayaV. >>> >>> _______________________________________________ >>> Carbon-dev mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>> >> >> >> -- >> Sameera Jayasoma >> Technical Lead and Product Manager, WSO2 Carbon >> >> WSO2, Inc. (http://wso2.com) >> email: [email protected] >> blog: http://tech.jayasoma.org >> >> Lean . Enterprise . Middleware >> >> _______________________________________________ >> Carbon-dev mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > > > -- > Milinda Pathirage > Technical Lead and Product Manager, Business Process Server - WSO2 Inc; > http://wso2.com > Blog: http://blog.mpathirage.com > > Lean Enterprise Middleware > > _______________________________________________ > Carbon-dev mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- *Afkham Azeez* Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com, * * *Member; Apache Software Foundation; **http://www.apache.org/*<http://www.apache.org/> * email: **[email protected]* <[email protected]>* cell: +94 77 3320919 blog: **http://blog.afkham.org* <http://blog.afkham.org>* twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware*
_______________________________________________ Carbon-dev mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
