[JBoss JIRA] Created: (GTNWSRP-205) Nodetype not found wsrp:portletcontext when import portlet
by Michal Vanco (JIRA)
Nodetype not found wsrp:portletcontext when import portlet
----------------------------------------------------------
Key: GTNWSRP-205
URL: https://issues.jboss.org/browse/GTNWSRP-205
Project: GateIn WSRP
Issue Type: Bug
Environment: GateIn wsrp-extraction branch, wsrp 2.1.0-Alpha01-SNAPSHOT
Reporter: Michal Vanco
Assignee: Chris Laprun
Fix For: 2.0.1-GA
Attachments: wsrp-import.txt
There is an issue in wsrp-extraction branch when importing portlet.
Exact steps to reproduce:
(have 1 remotable portlet deployed - any)
- sign in, go to wsrp page
- export some portlet
- import exported portlet (select portlet, page, window), click on
Import button will reproduce the error (attached):
javax.jcr.nodetype.NoSuchNodeTypeException: Nodetype not
found wsrp:portletcontext
Actually the portlet is imported, but it cause other serious problem -
consumer can't be deleted:
javax.xml.ws.soap.SOAPFaultException: Cannot remove removed node
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 months
[JBoss JIRA] Created: (GTNWSRP-123) Seam portlet using portal authentication doesn't work over WSRP2
by Michal Vanco (JIRA)
Seam portlet using portal authentication doesn't work over WSRP2
----------------------------------------------------------------
Key: GTNWSRP-123
URL: https://jira.jboss.org/browse/GTNWSRP-123
Project: GateIn WSRP
Issue Type: Bug
Affects Versions: 2.0.0-Beta05
Environment: EPP5.1.0 ER03
seam booking demo (bundled in EPP: jboss-epp-5.1/portletbridge/examples/seamEAR.ear)
Reporter: Michal Vanco
Assignee: Chris Laprun
Fix For: 2.0.0-CR01
It seems like portlet over WSRP is not able to deal with portal authentication.
For example seam booking demo works only if you are logged in.
But this porltet over WSRP doesn't work and behaves like I'm not logged in all the time.
Result is that I'm not able to use this portlet at all because hotel searching isn't available.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 6 months