Re: Page Url rewriting in tapestry

2013-05-30 Thread Boris Horvat
Hm...I see so it basically still uses the 'build' which in returns causes
my circular dependency

Thanks that is a good to know.

Cheers


On Thu, May 30, 2013 at 11:55 AM, Lance Java wrote:

> A "contribute" method builds up a Map, List or Collection prior to invoking
> the constructor of a service. The Map, List or Collection is then  passed
> to the constructor of a service. The service must be annotated with one of
> @UsesMappedConfiguration, @UsesOrderedConfiguration or @UsesConfiguration.
>
> http://tapestry.apache.org/tapestry-ioc-configuration.html
>



-- 
Sincerely
*Boris Horvat*


Re: Page Url rewriting in tapestry

2013-05-30 Thread Lance Java
A "contribute" method builds up a Map, List or Collection prior to invoking
the constructor of a service. The Map, List or Collection is then  passed
to the constructor of a service. The service must be annotated with one of
@UsesMappedConfiguration, @UsesOrderedConfiguration or @UsesConfiguration.

http://tapestry.apache.org/tapestry-ioc-configuration.html


Re: Page Url rewriting in tapestry

2013-05-29 Thread Boris Horvat
I understand the difference between decorator and builder method.
Actually i was using contribute as my weapon of choice and I guess I could
be lacking on the knowledge there. More specifically does contribution of
the method act more like decorator or builder.

Nonetheless I was able to make my decorator to work :)

Thanks for your example

Cheers


On Wed, May 29, 2013 at 3:12 PM, Lance Java wrote:

> Hi Boris, I'm not sure you have grasped the concept of an IOC decorator. A
> decorator method name is prefixed with "decorate" and gets passed the
> default implementation so that it can delegate through to it. It is
> different to a "builder" method (prefixed with "build") which I think you
> might be using which is most likely causing a circular reference /
> StackOverflow.
>
> http://tapestry.apache.org/tapestry-ioc-decorators.html
>
> I did this a while ago but from memory, the PageRenderLinkTransformer was
> not sufficient for what I was trying to do because I wanted to transform
> component events as well as page render events.
>



-- 
Sincerely
*Boris Horvat*


Re: Page Url rewriting in tapestry

2013-05-29 Thread Lance Java
Hi Boris, I'm not sure you have grasped the concept of an IOC decorator. A
decorator method name is prefixed with "decorate" and gets passed the
default implementation so that it can delegate through to it. It is
different to a "builder" method (prefixed with "build") which I think you
might be using which is most likely causing a circular reference /
StackOverflow.

http://tapestry.apache.org/tapestry-ioc-decorators.html

I did this a while ago but from memory, the PageRenderLinkTransformer was
not sufficient for what I was trying to do because I wanted to transform
component events as well as page render events.


Re: Page Url rewriting in tapestry

2013-05-28 Thread Boris Horvat
Hi Lance,

I hope you see this as I have a question regarding your code (if anyone
else can answer I will be happy with that as well :))

I have created the implementation of the PageRenderLinkTransformer. This is
a simple implementation that checks for a few condition and then adds the
appropriate prefix to the path and returns PageRenderRequestParameters.
However this prevents the processing of other transformers one of which is
in charge of properly parsing the page and the context of that page (build
in tapestry). So when ever I have something like /mypage/context it fails
to transforms it as it think that the context is the name of the page.

Any suggestion how I can inject the other transformers and process the
request?

I have tried to inject ComponentEventLinkEncoder using a constructor but
this failed with StackOverFlowException. What I think happens is
that ComponentEventLinkEncoder gives the request to my transformer which
then gives it back only to receives it again and so on. So I guess just
passing it to the encoder wont force the process to continue.

Any idea how to overcome this problem?

I have looked into your code and I have seen that you are using
ComponentEventLinkEncoder so I have tried to modify my code to match that.
Sadly this didnt really work. What happend is that none of my requests
where properly processed. When I would go to the page I could see the
folder structure with the .tml pages.

Any ideas?

Cheers and Thanks
Boris


On Tue, May 28, 2013 at 12:44 AM, Boris Horvat wrote:

> I guess I am a bit tiered as I just manage to move the code from one
> implementation to the other and it worked. So now PageRenderLinkTransformer
> implementation can handle this transformation.
>
> Thanks for the help everyone
>
>
> On Tue, May 28, 2013 at 12:41 AM, Boris Horvat 
> wrote:
>
>> At first glance (and small try) this look like something I can use. So
>> here is my idea.
>>
>> I can use this interface "ComponentEventLinkEncoder" to contribute my own
>> logic that will strip the prefixed path from the link. However I am not
>> sure what should I return if dont want any transformation. Should I return
>> null or should I return the link that I received as parameter?
>>
>> I see that in your class you have inserted the same interface that you
>> are overriding is that because that way you will get access to all of the
>> other enocoder and you can make sure that your implementation is part of
>> the chain?
>>
>> When those links are process they will be directed to correct place
>> thanks to the PageRenderLinkTransformer. This interface has two methods.
>> The first one decodePageRenderRequest will be used to figure out to which
>> folder should the request go to. where as the second one
>> transformPageRenderLink can be used to transform one link to the other.
>> However this transformation will fail if the link doesnt point to the
>> correct place so I cant use this for my needs.
>>
>> My question is in javasoc for the decodePageRenderRequest it says *@return
>> decoded parameters, or null to proceed normally*. Does this also applies
>> for transformPageRenderLink since javadocs is not cleared. Should I return
>> null or *defaultLink *for
>> *
>> *
>> *Link transformPageRenderLink(Link defaultLink,
>> PageRenderRequestParameters parameters);
>> *
>>
>> This will allow me to keep the original urls and to forward the request
>> to the correct folder. I think :)
>>
>> Also I am confused why I cant do this in PageRenderLinkTransformer, I got
>> the impression from documentation that this should be possible but my links
>> dont look correct :)
>>
>>
>>
>> On Mon, May 27, 2013 at 8:38 PM, Lance Java wrote:
>>
>>> Not sure if this will help but thought it might be of interest. I've
>>> written a ComponentEventLinkEncoder which looks for "special" URL
>>> prefixes.
>>> If a "special" folder is found on the URL, it is removed from the URL and
>>> passed on to the normal tapestry component rendering. The "special"
>>> folder
>>> (which I call a Mode) is pushed onto the Environment where it can be used
>>> by pages and components. This allows pages and components to render in
>>> different modes based on the URL prefix.
>>>
>>>
>>> https://github.com/uklance/tapestry-sandbox/blob/master/src/main/java/com/github/uklance/services/AppModule.java#L40
>>>
>>> https://github.com/uklance/tapestry-sandbox/blob/master/src/main/java/com/github/uklance/mode/ModeComponentEventLinkEncoder.java
>>>
>>
>>
>>
>> --
>> Sincerely
>> *Boris Horvat*
>>
>
>
>
> --
> Sincerely
> *Boris Horvat*
>



-- 
Sincerely
*Boris Horvat*


Re: Page Url rewriting in tapestry

2013-05-27 Thread Boris Horvat
I guess I am a bit tiered as I just manage to move the code from one
implementation to the other and it worked. So now PageRenderLinkTransformer
implementation can handle this transformation.

Thanks for the help everyone


On Tue, May 28, 2013 at 12:41 AM, Boris Horvat wrote:

> At first glance (and small try) this look like something I can use. So
> here is my idea.
>
> I can use this interface "ComponentEventLinkEncoder" to contribute my own
> logic that will strip the prefixed path from the link. However I am not
> sure what should I return if dont want any transformation. Should I return
> null or should I return the link that I received as parameter?
>
> I see that in your class you have inserted the same interface that you are
> overriding is that because that way you will get access to all of the other
> enocoder and you can make sure that your implementation is part of the
> chain?
>
> When those links are process they will be directed to correct place thanks
> to the PageRenderLinkTransformer. This interface has two methods. The first
> one decodePageRenderRequest will be used to figure out to which folder
> should the request go to. where as the second one transformPageRenderLink
> can be used to transform one link to the other. However
> this transformation will fail if the link doesnt point to the correct place
> so I cant use this for my needs.
>
> My question is in javasoc for the decodePageRenderRequest it says *@return
> decoded parameters, or null to proceed normally*. Does this also applies
> for transformPageRenderLink since javadocs is not cleared. Should I return
> null or *defaultLink *for
> *
> *
> *Link transformPageRenderLink(Link defaultLink,
> PageRenderRequestParameters parameters);
> *
>
> This will allow me to keep the original urls and to forward the request to
> the correct folder. I think :)
>
> Also I am confused why I cant do this in PageRenderLinkTransformer, I got
> the impression from documentation that this should be possible but my links
> dont look correct :)
>
>
>
> On Mon, May 27, 2013 at 8:38 PM, Lance Java wrote:
>
>> Not sure if this will help but thought it might be of interest. I've
>> written a ComponentEventLinkEncoder which looks for "special" URL
>> prefixes.
>> If a "special" folder is found on the URL, it is removed from the URL and
>> passed on to the normal tapestry component rendering. The "special" folder
>> (which I call a Mode) is pushed onto the Environment where it can be used
>> by pages and components. This allows pages and components to render in
>> different modes based on the URL prefix.
>>
>>
>> https://github.com/uklance/tapestry-sandbox/blob/master/src/main/java/com/github/uklance/services/AppModule.java#L40
>>
>> https://github.com/uklance/tapestry-sandbox/blob/master/src/main/java/com/github/uklance/mode/ModeComponentEventLinkEncoder.java
>>
>
>
>
> --
> Sincerely
> *Boris Horvat*
>



-- 
Sincerely
*Boris Horvat*


Re: Page Url rewriting in tapestry

2013-05-27 Thread Boris Horvat
At first glance (and small try) this look like something I can use. So here
is my idea.

I can use this interface "ComponentEventLinkEncoder" to contribute my own
logic that will strip the prefixed path from the link. However I am not
sure what should I return if dont want any transformation. Should I return
null or should I return the link that I received as parameter?

I see that in your class you have inserted the same interface that you are
overriding is that because that way you will get access to all of the other
enocoder and you can make sure that your implementation is part of the
chain?

When those links are process they will be directed to correct place thanks
to the PageRenderLinkTransformer. This interface has two methods. The first
one decodePageRenderRequest will be used to figure out to which folder
should the request go to. where as the second one transformPageRenderLink
can be used to transform one link to the other. However
this transformation will fail if the link doesnt point to the correct place
so I cant use this for my needs.

My question is in javasoc for the decodePageRenderRequest it says *@return
decoded parameters, or null to proceed normally*. Does this also applies
for transformPageRenderLink since javadocs is not cleared. Should I return
null or *defaultLink *for
*
*
*Link transformPageRenderLink(Link defaultLink, PageRenderRequestParameters
parameters);
*

This will allow me to keep the original urls and to forward the request to
the correct folder. I think :)

Also I am confused why I cant do this in PageRenderLinkTransformer, I got
the impression from documentation that this should be possible but my links
dont look correct :)



On Mon, May 27, 2013 at 8:38 PM, Lance Java wrote:

> Not sure if this will help but thought it might be of interest. I've
> written a ComponentEventLinkEncoder which looks for "special" URL prefixes.
> If a "special" folder is found on the URL, it is removed from the URL and
> passed on to the normal tapestry component rendering. The "special" folder
> (which I call a Mode) is pushed onto the Environment where it can be used
> by pages and components. This allows pages and components to render in
> different modes based on the URL prefix.
>
>
> https://github.com/uklance/tapestry-sandbox/blob/master/src/main/java/com/github/uklance/services/AppModule.java#L40
>
> https://github.com/uklance/tapestry-sandbox/blob/master/src/main/java/com/github/uklance/mode/ModeComponentEventLinkEncoder.java
>



-- 
Sincerely
*Boris Horvat*


Re: Page Url rewriting in tapestry

2013-05-27 Thread Lance Java
Not sure if this will help but thought it might be of interest. I've
written a ComponentEventLinkEncoder which looks for "special" URL prefixes.
If a "special" folder is found on the URL, it is removed from the URL and
passed on to the normal tapestry component rendering. The "special" folder
(which I call a Mode) is pushed onto the Environment where it can be used
by pages and components. This allows pages and components to render in
different modes based on the URL prefix.

https://github.com/uklance/tapestry-sandbox/blob/master/src/main/java/com/github/uklance/services/AppModule.java#L40
https://github.com/uklance/tapestry-sandbox/blob/master/src/main/java/com/github/uklance/mode/ModeComponentEventLinkEncoder.java


Re: Page Url rewriting in tapestry

2013-05-27 Thread Boris Horvat
I was thinking about that but I dont see it will fit in what I need.

Right now what I need is to somehow generate a link to the page that
"doesnt exist' since decodePageRenderRequest will make sure that that link
is processable.

To me at least this looks like a bug, why would a component throw an
exception when my implementation of PageRenderLinkTransformer would be able
to process the url?


On Mon, May 27, 2013 at 10:59 AM, Alejandro Scandroli <
alejandroscandr...@gmail.com> wrote:

> Hi Boris,
>
> Have you consider using tapestry.application-folder?
>
> http://tapestry.apache.org/configuration.html#Configuration-tapestry.applicationfolder
>
> If you are using two instances of the same application using
> tapestry.application-folder would be your best option.
> Is that the case? or you want to allow access from both domains to the
> same instance?
>
> Alejandro.
>
>
> On Mon, May 27, 2013 at 9:10 AM, Boris Horvat 
> wrote:
> > So my idea was that in my class that contributes to the tapestry url I
> > would have 2 methods
> >
> > decodePageRenderRequest - that looks for the page under given subfolder
> >
> > and transformPageRenderLink - that strips the actual folder (since i need
> > to put it or pagelink component would fail)
> >
> > My assumption is that they would work together to generate false link
> > (transformPageRenderLink ) that would know how to find the right page
> > (decodePageRenderRequest). However I am still getting "Unable to resolve
> to
> > a page name". Any ideas?
> >
> > Cheers
> >
> >
> > On Mon, May 27, 2013 at 1:38 AM, Boris Horvat  >wrote:
> >
> >> I do have one more question if anyone has an idea how to solve it.
> >>
> >> My Index page is ok as nothing is pointing to it. However all of the
> other
> >> pages are now at problem since they reside inside of a folder so when I
> use
> >>
> >> t:pagelink t:page="MyPageThatIsNowInFolder1"
> >>
> >> it complains that it cant find this page and if I add
> >>
> >> t:pagelink t:page="folder1/MyPageThatIsNowInFolder1"
> >>
> >> then it link is broken since it will try to go to
> >>
> >> folder1/folder1/MyPageThatIsNowInFolder1
> >>
> >> Any ideas how I can save the old links (ie t:pagelink
> >> t:page="MyPageThatIsNowInFolder1") and still use pagelink component?
> >>
> >> Cheers
> >>
> >>
> >>
> >> On Mon, May 27, 2013 at 1:18 AM, Boris Horvat  >wrote:
> >>
> >>> I spoke too soon. A bit of testing got me the answer that I can just
> >>> insert the folder as a string.
> >>>
> >>> Cheers
> >>>
> >>>
> >>> On Mon, May 27, 2013 at 1:05 AM, Boris Horvat <
> horvat.z.bo...@gmail.com>wrote:
> >>>
>  Hi all,
> 
>  I was looking into this example here
>  http://blog.tapestry5.de/index.php/2010/09/06/new-url-rewriting-api/however
>  I am not sure if what I want is possible as I am not really sure how
> to do
>  it.
> 
>  What I want to do is separate my application into 2 folders but I need
>  to keep my urls as they are. The example of my mapping should be
> 
>  www.my-website.com = www.my-website.com/folder1/
>  www.my-website.com/mypage = www.my-website.com/folder1//mypage
> 
>  custom.my-website.com=custom.my-website.com/folder2
>  custom.my-website.com/mypage=custom.my-website.com/folder2/mypage
> 
>  What i am puzzled by is is it possible to somehow insert the path into
>  the url or should I try to return the actual page when I see some
> path?
> 
>  So how would you implement this?
> 
>  Cheers
>  --
>  Sincerely
>  *Boris Horvat*
> 
> >>>
> >>>
> >>>
> >>> --
> >>> Sincerely
> >>> *Boris Horvat*
> >>>
> >>
> >>
> >>
> >> --
> >> Sincerely
> >> *Boris Horvat*
> >>
> >
> >
> >
> > --
> > Sincerely
> > *Boris Horvat*
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>


-- 
Sincerely
*Boris Horvat*


Re: Page Url rewriting in tapestry

2013-05-27 Thread Alejandro Scandroli
Hi Boris,

Have you consider using tapestry.application-folder?
http://tapestry.apache.org/configuration.html#Configuration-tapestry.applicationfolder

If you are using two instances of the same application using
tapestry.application-folder would be your best option.
Is that the case? or you want to allow access from both domains to the
same instance?

Alejandro.


On Mon, May 27, 2013 at 9:10 AM, Boris Horvat  wrote:
> So my idea was that in my class that contributes to the tapestry url I
> would have 2 methods
>
> decodePageRenderRequest - that looks for the page under given subfolder
>
> and transformPageRenderLink - that strips the actual folder (since i need
> to put it or pagelink component would fail)
>
> My assumption is that they would work together to generate false link
> (transformPageRenderLink ) that would know how to find the right page
> (decodePageRenderRequest). However I am still getting "Unable to resolve to
> a page name". Any ideas?
>
> Cheers
>
>
> On Mon, May 27, 2013 at 1:38 AM, Boris Horvat wrote:
>
>> I do have one more question if anyone has an idea how to solve it.
>>
>> My Index page is ok as nothing is pointing to it. However all of the other
>> pages are now at problem since they reside inside of a folder so when I use
>>
>> t:pagelink t:page="MyPageThatIsNowInFolder1"
>>
>> it complains that it cant find this page and if I add
>>
>> t:pagelink t:page="folder1/MyPageThatIsNowInFolder1"
>>
>> then it link is broken since it will try to go to
>>
>> folder1/folder1/MyPageThatIsNowInFolder1
>>
>> Any ideas how I can save the old links (ie t:pagelink
>> t:page="MyPageThatIsNowInFolder1") and still use pagelink component?
>>
>> Cheers
>>
>>
>>
>> On Mon, May 27, 2013 at 1:18 AM, Boris Horvat 
>> wrote:
>>
>>> I spoke too soon. A bit of testing got me the answer that I can just
>>> insert the folder as a string.
>>>
>>> Cheers
>>>
>>>
>>> On Mon, May 27, 2013 at 1:05 AM, Boris Horvat 
>>> wrote:
>>>
 Hi all,

 I was looking into this example here
 http://blog.tapestry5.de/index.php/2010/09/06/new-url-rewriting-api/ 
 however
 I am not sure if what I want is possible as I am not really sure how to do
 it.

 What I want to do is separate my application into 2 folders but I need
 to keep my urls as they are. The example of my mapping should be

 www.my-website.com = www.my-website.com/folder1/
 www.my-website.com/mypage = www.my-website.com/folder1//mypage

 custom.my-website.com=custom.my-website.com/folder2
 custom.my-website.com/mypage=custom.my-website.com/folder2/mypage

 What i am puzzled by is is it possible to somehow insert the path into
 the url or should I try to return the actual page when I see some path?

 So how would you implement this?

 Cheers
 --
 Sincerely
 *Boris Horvat*

>>>
>>>
>>>
>>> --
>>> Sincerely
>>> *Boris Horvat*
>>>
>>
>>
>>
>> --
>> Sincerely
>> *Boris Horvat*
>>
>
>
>
> --
> Sincerely
> *Boris Horvat*

-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org



Re: Page Url rewriting in tapestry

2013-05-27 Thread Boris Horvat
So my idea was that in my class that contributes to the tapestry url I
would have 2 methods

decodePageRenderRequest - that looks for the page under given subfolder

and transformPageRenderLink - that strips the actual folder (since i need
to put it or pagelink component would fail)

My assumption is that they would work together to generate false link
(transformPageRenderLink ) that would know how to find the right page
(decodePageRenderRequest). However I am still getting "Unable to resolve to
a page name". Any ideas?

Cheers


On Mon, May 27, 2013 at 1:38 AM, Boris Horvat wrote:

> I do have one more question if anyone has an idea how to solve it.
>
> My Index page is ok as nothing is pointing to it. However all of the other
> pages are now at problem since they reside inside of a folder so when I use
>
> t:pagelink t:page="MyPageThatIsNowInFolder1"
>
> it complains that it cant find this page and if I add
>
> t:pagelink t:page="folder1/MyPageThatIsNowInFolder1"
>
> then it link is broken since it will try to go to
>
> folder1/folder1/MyPageThatIsNowInFolder1
>
> Any ideas how I can save the old links (ie t:pagelink
> t:page="MyPageThatIsNowInFolder1") and still use pagelink component?
>
> Cheers
>
>
>
> On Mon, May 27, 2013 at 1:18 AM, Boris Horvat wrote:
>
>> I spoke too soon. A bit of testing got me the answer that I can just
>> insert the folder as a string.
>>
>> Cheers
>>
>>
>> On Mon, May 27, 2013 at 1:05 AM, Boris Horvat 
>> wrote:
>>
>>> Hi all,
>>>
>>> I was looking into this example here
>>> http://blog.tapestry5.de/index.php/2010/09/06/new-url-rewriting-api/ however
>>> I am not sure if what I want is possible as I am not really sure how to do
>>> it.
>>>
>>> What I want to do is separate my application into 2 folders but I need
>>> to keep my urls as they are. The example of my mapping should be
>>>
>>> www.my-website.com = www.my-website.com/folder1/
>>> www.my-website.com/mypage = www.my-website.com/folder1//mypage
>>>
>>> custom.my-website.com=custom.my-website.com/folder2
>>> custom.my-website.com/mypage=custom.my-website.com/folder2/mypage
>>>
>>> What i am puzzled by is is it possible to somehow insert the path into
>>> the url or should I try to return the actual page when I see some path?
>>>
>>> So how would you implement this?
>>>
>>> Cheers
>>> --
>>> Sincerely
>>> *Boris Horvat*
>>>
>>
>>
>>
>> --
>> Sincerely
>> *Boris Horvat*
>>
>
>
>
> --
> Sincerely
> *Boris Horvat*
>



-- 
Sincerely
*Boris Horvat*


Re: Page Url rewriting in tapestry

2013-05-26 Thread Boris Horvat
I do have one more question if anyone has an idea how to solve it.

My Index page is ok as nothing is pointing to it. However all of the other
pages are now at problem since they reside inside of a folder so when I use

t:pagelink t:page="MyPageThatIsNowInFolder1"

it complains that it cant find this page and if I add

t:pagelink t:page="folder1/MyPageThatIsNowInFolder1"

then it link is broken since it will try to go to

folder1/folder1/MyPageThatIsNowInFolder1

Any ideas how I can save the old links (ie t:pagelink
t:page="MyPageThatIsNowInFolder1") and still use pagelink component?

Cheers



On Mon, May 27, 2013 at 1:18 AM, Boris Horvat wrote:

> I spoke too soon. A bit of testing got me the answer that I can just
> insert the folder as a string.
>
> Cheers
>
>
> On Mon, May 27, 2013 at 1:05 AM, Boris Horvat wrote:
>
>> Hi all,
>>
>> I was looking into this example here
>> http://blog.tapestry5.de/index.php/2010/09/06/new-url-rewriting-api/ however
>> I am not sure if what I want is possible as I am not really sure how to do
>> it.
>>
>> What I want to do is separate my application into 2 folders but I need to
>> keep my urls as they are. The example of my mapping should be
>>
>> www.my-website.com = www.my-website.com/folder1/
>> www.my-website.com/mypage = www.my-website.com/folder1//mypage
>>
>> custom.my-website.com=custom.my-website.com/folder2
>> custom.my-website.com/mypage=custom.my-website.com/folder2/mypage
>>
>> What i am puzzled by is is it possible to somehow insert the path into
>> the url or should I try to return the actual page when I see some path?
>>
>> So how would you implement this?
>>
>> Cheers
>> --
>> Sincerely
>> *Boris Horvat*
>>
>
>
>
> --
> Sincerely
> *Boris Horvat*
>



-- 
Sincerely
*Boris Horvat*


Re: Page Url rewriting in tapestry

2013-05-26 Thread Boris Horvat
I spoke too soon. A bit of testing got me the answer that I can just insert
the folder as a string.

Cheers


On Mon, May 27, 2013 at 1:05 AM, Boris Horvat wrote:

> Hi all,
>
> I was looking into this example here
> http://blog.tapestry5.de/index.php/2010/09/06/new-url-rewriting-api/ however
> I am not sure if what I want is possible as I am not really sure how to do
> it.
>
> What I want to do is separate my application into 2 folders but I need to
> keep my urls as they are. The example of my mapping should be
>
> www.my-website.com = www.my-website.com/folder1/
> www.my-website.com/mypage = www.my-website.com/folder1//mypage
>
> custom.my-website.com=custom.my-website.com/folder2
> custom.my-website.com/mypage=custom.my-website.com/folder2/mypage
>
> What i am puzzled by is is it possible to somehow insert the path into the
> url or should I try to return the actual page when I see some path?
>
> So how would you implement this?
>
> Cheers
> --
> Sincerely
> *Boris Horvat*
>



-- 
Sincerely
*Boris Horvat*