By the way, I will describe more in the wiki page later, but just for
clarification, the main purpose of using spring framework is only to leverage
its IoC and component weaving features and so simplify the implementation code.
In the past, someone asked me if it's possible to configure reverse
On Friday, January 17, 2014 5:07 PM, David Taylor
wrote:
> improvements in configurability/extensibility of the reverse proxy
>servlet module by using spring framework and spring bean assembling
>configuration as well. It's a perfect time to gather contirubtions. Let us
>know if you want to he
> improvements in configurability/extensibility of the reverse proxy
servlet module by using spring framework and spring bean assembling
configuration as well. It's a perfect time to gather contirubtions. Let us
know if you want to help. :-)
Definitely. One of the tasks in the Roadmap is to look
Hi David,
Thanks for the quick response!
On Thursday, January 16, 2014 9:58 PM, David S Taylor
wrote:
> Do you have any objections or different ideas?
>
>No objections at all. Makes sense to separate the webapp vs portlet app
>usage. Hopefully we can get these new improvements included in the
> Do you have any objections or different ideas?
No objections at all. Makes sense to separate the webapp vs portlet app
usage. Hopefully we can get these new improvements included in the next
Jetspeed release.
> new, more intuitive transformation rules abstracting something like
htmlcleaner's Ta
Hi,
I'd like to restructure the modules of apa-webcontent and refactor the html
content rewriting modules.
Some people including me use only reverse-proxy servlet in non-portlet
applications in some situations, and the current html content rewriter feature
seems to be tightly coupled with portl
