Thanks ! That was the answer :)
i just added this in my bookmark-document-project.xml and it's working.
<global>
<target>ForMainProject</target>
<context type="main">
<meta>docs/meta-projectProject-list.xml</meta>
</context>
<context type="action">
<doctype>doctype=projectProject</doctype>
<viewStyle>listWithILink</viewStyle>
<viewOption>rollover-dropdown</viewOption>
</context>
</global>
Now, how can i handle navigation between different doctypes ?
For example, i would like to display all tasks related to a certain project, or resources allocated to a certain task.
My idea would be to generate a link in the list view, for example, in the project list, i would like to have a 'tasks' link generated for each project document.
How could i do that ?
Marc
2006/4/19, Jean-Christophe Kermagoret <jck-qkEci4++Hf1AfugRpC6u6w@xxxxxxxxxxxxxxxx>:
Marc,
I think I solved your problem.
If it's always the main base query (in app_base.xml) that is played, it
means that there is no communication beetween your portlet menu and your
porlet result query.
When you click on a bookmark, the links sends a message to the portal to
tell him which portlet should receive the events.
With BlueXML framework, it is the target parameter that is used. You
will find it in
bookmark-agenda.xml that is inherited by
bookmark-agenda-project.xml. This parameter is passed to the cocoon
portal through the cocoon portal bookmark system.
So, to view the result of your query, you have to :
* define a bookmark in src/blocks/cms/resources/bookmark.xml (see below)
* define the target parameter (for example 'ForMainProject' if you write
the code below)
* restart cocoon because cocoon portal bookmarks are not always
dynamically updated
Once all this done, it should work. I hope ;-)
<!-- MainProject-->
<event type="jxpath" id="menuForMainProject">
<targettype>coplet</targettype>
<targetid>DocumentProject</targetid>
<path>attributes/src</path>
</event>
<event type="jxpath" id="srcForMainProject">
<targettype>coplet</targettype>
<targetid>MainProject</targetid>
<path>attributes/src</path>
</event>
<event type="jxpath" id="actionContextForMainProject">
<targettype>coplet</targettype>
<targetid>MainProject</targetid>
<path>attributes/actionContext</path>
</event>
<event type="jxpath" id="navigationContextForMainProject">
<targettype>coplet</targettype>
<targetid>MainProject</targetid>
<path>attributes/navigationContext</path>
</event>
<event type="jxpath" id="mainContextForMainProject">
<targettype>coplet</targettype>
<targetid>MainProject</targetid>
<path>attributes/mainContext</path>
</event>
I think it's always written in the bookmark.xml file. So just try
ForMainProject ;-)
JC
Marc Salvetti a écrit :
> Hello JC,
>
> i did created the project.xq
, and this request is already working.
> For all other doctypes, so far i tried only with the generic.xq, as in
> the second bookmark for resources
> From what i can see, it's always the query specified in the
> app-base.xml that is executed, regardless of what bookmark i clicked on.
>
> Marc
>
> 2006/4/19, Jean-Christophe Kermagoret <jck-qkEci4++Hf1AfugRpC6u6w@xxxxxxxxxxxxxxxx
> <mailto:
jck-qkEci4++Hf1AfugRpC6u6w@xxxxxxxxxxxxxxxx>>:
>
> Marc,
> I just created a new thread to help you to resolve your problems about
> bookmark.
>
> > <bookmark
> > metaShort="projectProject"
> > viewType="table"
> >
> query="project::/document[(meta/doctype='projectProject')]">
> > <title>Projets</title>
> > </bookmark>
> > <bookmark
> > metaShort="projectResource"
> > viewType="table"
> >
> query="generic::/document[(meta/doctype='projectResource')]">
> > <title>Resources</title>
> > </bookmark>
>
> For each item, the query attribute is splitted with '::' part (that
> is a
> bad idea because of the possible use of :: in Xquery for NS - it will be
> corrected later see
http://www.bluexml.org/bugzilla/show_bug.cgi?id=106)
>
> This means you have a Projets item, that calls a project.xq (first part
> of the query attribute) with /document[meta/doctype='projectProject']
> (second part of the query attribute)
>
> Does the project.xq exist ?
>
> If project.xq doesn't do anything except getting datas, you may use the
> generic.xq instead, and just try /document[meta/doctype='...']
>
> JC
>
> --
>
> BlueXML
> Jean-Christophe Kermagoret
> Directeur associé
> jck-qkEci4++Hf1AfugRpC6u6w@xxxxxxxxxxxxxxxx <mailto:
jck-qkEci4++Hf1AfugRpC6u6w@xxxxxxxxxxxxxxxx>
>
> _______________________________________________
> User mailing list
> User-E0IXfuzpajFHgg9j4ji3+w@xxxxxxxxxxxxxxxx <mailto:
User-E0IXfuzpajFHgg9j4ji3+w@xxxxxxxxxxxxxxxx>
> http://mlm.triglyphe.com/mailman/listinfo/user
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> User mailing list
> User-BhR0IzePIl4@xxxxxxxxxxxxxxxxxxxxxxxxx
>
http://mlm.triglyphe.com/mailman/listinfo/user
--
BlueXML
Jean-Christophe Kermagoret
Directeur associé
jck-qkEci4++Hf1AfugRpC6u6w@xxxxxxxxxxxxxxxx
_______________________________________________
User mailing list
User@xxxxxxxxxxxxxxx
http://mlm.triglyphe.com/mailman/listinfo/user
_______________________________________________
User mailing list
User-E0IXfuzpajFHgg9j4ji3+w@xxxxxxxxxxxxxxxx
http://mlm.triglyphe.com/mailman/listinfo/user
|
