You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@bloodhound.apache.org by Apache Bloodhound <bl...@incubator.apache.org> on 2012/04/03 19:42:26 UTC
[Apache Bloodhound] #24: Product namespace and product handling
#24: Product namespace and product handling
--------------------------+-------------------------------------
Reporter: gjm | Owner: gjm
Type: task | Status: new
Priority: critical | Milestone: RC1 for initial release
Component: multiproduct | Version:
Keywords: |
--------------------------+-------------------------------------
We should be dealing with products in such a way that we don't need
plugins to understand the product system to work properly.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/24>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #24: Product namespace and product handling
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#24: Product namespace and product handling
---------------------------+-------------------------------------
Reporter: gjm | Owner: gjm
Type: task | Status: closed
Priority: critical | Milestone: RC1 for initial release
Component: multiproduct | Version:
Resolution: fixed | Keywords:
---------------------------+-------------------------------------
Changes (by gjm):
* status: accepted => closed
* resolution: => fixed
Comment:
r1327544 should provide the generic handling of the product urls described
above.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/24#comment:3>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #24: Product namespace and product handling
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#24: Product namespace and product handling
---------------------------+-------------------------------------
Reporter: gjm | Owner: gjm
Type: task | Status: new
Priority: critical | Milestone: RC1 for initial release
Component: multiproduct | Version:
Resolution: | Keywords:
---------------------------+-------------------------------------
Comment (by olemis):
About URL mapping my initial suggestion is
`http://domain.tld/path/to/env/p/<product_short_name>/<path_info>` (e.g.
http://issues.apache.org/bloodhound/p/bloodhound/wiki/Ui ) . This is
similar to ''Google Code'' projects URL mapping .
In that case I suggest multi-product system should implement
`IRequestFilter` interface so as to include product context in a global
data structure (e.g. `Request` ) so that each request handler / filter
(e.g. `WikiModule`, `TicketModule` , ...) will be able to handle it
appropriately.
... my initial $0.02 ...
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/24#comment:1>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #24: Product namespace and product handling
Posted by Gary <ga...@wandisco.com>.
On 04/03/2012 06:42 PM, Apache Bloodhound wrote:
> #24: Product namespace and product handling
> --------------------------+-------------------------------------
> Reporter: gjm | Owner: gjm
> Type: task | Status: new
> Priority: critical | Milestone: RC1 for initial release
> Component: multiproduct | Version:
> Keywords: |
> --------------------------+-------------------------------------
> We should be dealing with products in such a way that we don't need
> plugins to understand the product system to work properly.
>
So, I raised a few more tickets last night for bits and pieces. Making
sure that plugins play nicely with any product urlspace is of particular
interest to me at the moment but if anyone else is interested in helping
with this area, that would be good.
Cheers,
Gary
Re: [Apache Bloodhound] #24: Product namespace and product handling
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#24: Product namespace and product handling
---------------------------+-------------------------------------
Reporter: gjm | Owner: gjm
Type: task | Status: accepted
Priority: critical | Milestone: RC1 for initial release
Component: multiproduct | Version:
Resolution: | Keywords:
---------------------------+-------------------------------------
Changes (by gjm):
* status: new => accepted
Comment:
Interestingly, the IRequestFilters kick in after an IRequestHandler has
been chosen (although they can change the handler itself). With any kind
of url mapping we will still have to re-check the handlers with a modified
path_info.
I guess that is a reasonable way of going about things so I will create
something.
I think it might be better to work with the
/products/<product_short_name>/<path_info> scheme as there is no
particular reason to use a very short url there.. or if there is then my
decision can be overridden.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/24#comment:2>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker