Re: Jahia - Jira Portlet integration
ktlili <[email protected]> Mon, 17 Nov 2008 11:52:38 +0100
| Newsgroups | gmane.comp.cms.jahia.devel |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format.
--===============1961042403==
Content-Type: multipart/alternative;
boundary="------------030409010108080006080403"
This is a multi-part message in MIME format.
--------------030409010108080006080403
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Hi,
IFRAME
-------------
This solution allows integrating easily JIRA in a JAHIA portal. It can
be implemented and maintained quite quickly. The processing time of a
JIRA request (example: display current user issues) does not affect the
display time of a JAHIA page.
In addition to the SSO, you should implement a consistent look-and-feel
between JIRA and Jahia. Thus, the end-user feels that JIRA an JAHIA is a
global same application.
However, this solution has all the disadvantages of an iframe based
solution:
· scroll possible (but can be avoided thanks to JavaScript)
· no "state management" (ie. Back button of the browser is not
supported)
· no inter-communication between JIRA and JAHIA
· JIRA page header and navigation information are included,
· ...
PORTLET
------------
It is a much more flexible solution and allows better integration. I
suppose that with the JIRA provide good web services, which respond
quickly. The display time of a JAHIA page depends strongly on the
response time of the JIRA portlet and the JIRA web services. For more
information about JIRA web services:
http://confluence.atlassian.com/display/JIRA/JIRA + + Services
Currently, there are portlets that extract some JIRA reports:
http://confluence.atlassian.com/display/JIRAEXT/Kosmos.
Finally, if the customer needs only to have en access point of JIRA a
page from JAHIA page, the first solution is sufficient. If the needs are
stronger, the second solution is more appropriate.
Regards
KT
1- SSO between Jahia and Jira. User logs in to Jahia and can use the
same context when using Jira hosted portlet in (Jahia) or Iframe (???).
Advantage:
* Fast to implement and to maintain
* All JIRA features can we accessed
Bad point:
* It's a poor integration: layout (CSS) of the your Jahia Portal and
JIRA is po
Lars Hagrot a écrit :
> Hi!
>
> I have a question about the best way to integrate Jahia and Jira. We
> have a customer which needs both a powerful issue management tool and
> a powerful portal&CMS platform.
>
> 1 SSO between Jahia and Jira. User logs in to Jahia and can use the
> same context when using Jira hosted portlet in (Jahia) or Iframe (???).
>
> 2 Access to customized views exposed by web services (Jira). Probably
> we will develop a couple of portlets (one or two) for this or maybe a
> template.
>
> I this done before in any way? Otherwise I will of course invent a
> solution. I would for sure be pleased if I got an useful hint in any
> direction.....
>
>
> Regards
> /Lars Hagrot
>
>
>
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> dev_list mailing list
> [email protected]
> http://lists.jahia.org/cgi-bin/mailman/listinfo/dev_list
>
> ------------------------------------------------------------------------
>
> No virus found in this incoming message.
> Checked by AVG.
> Version: 7.5.549 / Virus Database: 270.9.0/1770 - Release Date: 05.11.2008 17:36
>
--------------030409010108080006080403
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Hi,<br>
<br>
<p class="MsoNormal" style="text-align: justify;"><span style=""
lang="EN-US">IFRAME<o:p></o:p></span></p>
<p class="MsoNormal" style="text-align: justify;"><span style=""
lang="EN-US">-------------<o:p></o:p></span></p>
<p class="MsoNormal" style="text-align: justify;"><span style=""
lang="EN-US">This solution allows integrating easily JIRA in
a JAHIA portal. It can be implemented and maintained quite quickly. The
processing
time of a JIRA request (example: display current user issues) does not
affect
the display time of <span style=""> </span>a JAHIA page. <o:p></o:p></span></p>
<p class="MsoNormal" style="text-align: justify;"><span style=""
lang="EN-US">In addition to the SSO, you should implement a consistent
look-and-feel between JIRA and Jahia. Thus, the end-user feels that
JIRA an
JAHIA is a global same application.<o:p></o:p></span></p>
<p class="MsoNormal" style="text-align: justify;"><span style=""
lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-align: justify;"><span style=""
lang="EN-US">However, this solution has all the
disadvantages of an iframe based solution:<o:p></o:p></span></p>
<p class="MsoNormal"
style="margin-left: 39.35pt; text-align: justify; text-indent: -18pt;"><!--[if !supportLists]--><span
style="font-family: Symbol;" lang="EN-US"><span style="">·<span
style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;">
</span></span></span><!--[endif]--><span style="" lang="EN-US">scroll
possible (but can be avoided thanks to JavaScript)<o:p></o:p></span></p>
<p class="MsoNormal"
style="margin-left: 39.35pt; text-align: justify; text-indent: -18pt;"><!--[if !supportLists]--><span
style="font-family: Symbol;" lang="EN-US"><span style="">·<span
style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;">
</span></span></span><!--[endif]--><span style="" lang="EN-US">no<span
style=""> </span>“state management” (ie. Back button of the
browser is not supported)<o:p></o:p></span></p>
<p class="MsoNormal"
style="margin-left: 39.35pt; text-align: justify; text-indent: -18pt;"><!--[if !supportLists]--><span
style="font-family: Symbol;" lang="EN-US"><span style="">·<span
style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;">
</span></span></span><!--[endif]--><span style="" lang="EN-US">no
inter-communication between JIRA and JAHIA<o:p></o:p></span></p>
<p class="MsoNormal"
style="margin-left: 39.35pt; text-align: justify; text-indent: -18pt;"><!--[if !supportLists]--><span
style="font-family: Symbol;" lang="EN-US"><span style="">·<span
style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;">
</span></span></span><!--[endif]--><span style="" lang="EN-US">JIRA
page header and navigation information are included,<o:p></o:p></span></p>
<p class="MsoNormal"
style="margin-left: 39.35pt; text-align: justify; text-indent: -18pt;"><!--[if !supportLists]--><span
style="font-family: Symbol;" lang="EN-US"><span style="">·<span
style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;">
</span></span></span><!--[endif]--><span style="" lang="EN-US"><span
style=""> </span>...<o:p></o:p></span></p>
<p class="MsoNormal"><span style="" lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="" lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-align: justify;"><span style=""
lang="EN-US">PORTLET<o:p></o:p></span></p>
<p class="MsoNormal" style="text-align: justify;"><span style=""
lang="EN-US">------------<o:p></o:p></span></p>
<p class="MsoNormal" style="text-align: justify;"><span style=""
lang="EN-US">It is a much more flexible solution and allows
better integration. I suppose that with the <span style=""> </span>JIRA
provide good web services, which respond
quickly. The display time of a JAHIA page depends strongly on the
response time
of the JIRA portlet and the JIRA web services. For more information
about JIRA
web services:<o:p></o:p></span></p>
<p class="MsoNormal" style="text-align: justify;"><span style=""
lang="EN-US"><a class="moz-txt-link-freetext" href="http://confluence.atlassian.com/display/JIRA/JIRA">http://confluence.atlassian.com/display/JIRA/JIRA</a>
+ + Services<o:p></o:p></span></p>
<p class="MsoNormal" style="text-align: justify;"><span style=""
lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-align: justify;"><span style=""
lang="EN-US">Currently, there are portlets that extract some
JIRA reports:<o:p></o:p></span></p>
<p class="MsoNormal" style="text-align: justify;"><span style=""
lang="EN-US"><span style=""> </span><a
href="http://confluence.atlassian.com/display/JIRAEXT/Kosmos">http://confluence.atlassian.com/display/JIRAEXT/Kosmos</a>.<o:p></o:p></span></p>
<p class="MsoNormal" style="text-align: justify;"><span style=""
lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-align: justify;"><span style=""
lang="EN-US">Finally, if the customer needs only to have en
access point of JIRA a page from JAHIA page, the first solution is
sufficient. If
the needs are stronger, the second solution is more appropriate.<br>
</span></p>
<p class="MsoNormal" style="text-align: justify;"><br>
Regards<br>
KT<br>
<span style="" lang="EN-US"><o:p></o:p></span></p>
<br>
<font face="tahoma" size="2"><br>
1- SSO between Jahia and Jira. User logs in
to Jahia and can use the same context when using Jira hosted portlet in
(Jahia) or Iframe (???).<br>
Advantage:<br>
</font>
<ul>
<li>Fast to implement and to maintain<br>
</li>
<li>All JIRA features can we accessed</li>
</ul>
Bad point:<br>
<ul>
<li>It's a poor integration: layout (CSS) of the your Jahia Portal
and JIRA is po<br>
</li>
</ul>
<font face="tahoma" size="2"><br>
</font><br>
<br>
Lars Hagrot a écrit :
<blockquote
cite="mid:E1ADAB5B00010242B2AB5C7AF70FBC9F01F9D06E0066@STOEXMBX01.domain01.net"
type="cite">
<meta http-equiv="Content-Type" content="text/html; ">
<style title="owaParaStyle">P {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</style>
<div dir="ltr"><font color="#000000" face="Tahoma" size="2">Hi!</font></div>
<div dir="ltr"> </div>
<div dir="ltr"><font color="#000000" face="Tahoma" size="2">I have a
question about the best way to integrate Jahia and Jira. We have a
customer which needs both a powerful issue management tool and a
powerful portal&CMS platform.</font></div>
<div dir="ltr"> </div>
<div dir="ltr"><font face="tahoma" size="2">1 SSO between Jahia and
Jira. User logs in to Jahia and can use the same context when using
Jira hosted portlet in (Jahia) or Iframe (???).
</font></div>
<div dir="ltr"> </div>
<div dir="ltr"><font face="tahoma" size="2">2 Access to customized
views exposed by web services
</font> (Jira). Probably we will develop a couple of portlets (one or
two) for this or maybe a template.</div>
<div dir="ltr"> </div>
<div dir="ltr"><font face="times new roman">I this done before in any
way? Otherwise I will of course invent a solution. I would for sure be
pleased if I got an useful hint in any direction.....
</font></div>
<div dir="ltr"> </div>
<div dir="ltr"> </div>
<div dir="ltr"><font face="times new roman">Regards</font></div>
<div dir="ltr"><font face="times new roman">/Lars Hagrot</font></div>
<div dir="ltr"> </div>
<div dir="ltr"> </div>
<div dir="ltr"> </div>
<div dir="ltr"> </div>
<div dir="ltr"> </div>
<div dir="ltr"> </div>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
dev_list mailing list
<a class="moz-txt-link-abbreviated" href="mailto:[email protected]">[email protected]</a>
<a class="moz-txt-link-freetext" href="http://lists.jahia.org/cgi-bin/mailman/listinfo/dev_list">http://lists.jahia.org/cgi-bin/mailman/listinfo/dev_list</a>
</pre>
<pre wrap="">
<hr size="4" width="90%">
No virus found in this incoming message.
Checked by AVG.
Version: 7.5.549 / Virus Database: 270.9.0/1770 - Release Date: 05.11.2008 17:36
</pre>
</blockquote>
<br>
</body>
</html>
--------------030409010108080006080403--
--===============1961042403==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
dev_list mailing list
[email protected]
http://lists.jahia.org/cgi-bin/mailman/listinfo/dev_list
--===============1961042403==--