6:16 a.m.
Problem with PRPs and WebSphere interoperability
------------------------------------------------
Key: GTNWSRP-178
URL: https://jira.jboss.org/browse/GTNWSRP-178
Project: GateIn WSRP
Issue Type: Bug
Components: Producer
Affects Versions: 2.0.0-CR03
Reporter: Chris Laprun
Assignee: Chris Laprun
Fix For: 2.0.0-GA
We got two portlets on a single page. The first one sets a public render parameter, the
second one prints it out. This works well locally and between two jboss instances.
Then we created a page with two remote portlets on websphere, while running both portlets
in the same jboss instance.
Websphere gets the parameter from the action response and send this back to jboss, but in
a different block, using wsrp extras. So the second portlet actually don't see that
value.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:18 a.m.
New subject: [JBoss JIRA] Updated: (GTNWSRP-178) Problem with PRPs and WebSphere interoperability
[
https://jira.jboss.org/browse/GTNWSRP-178?page=com.atlassian.jira.plugin....
]
Chris Laprun updated GTNWSRP-178:
---------------------------------
Attachment: websphere-to-jboss-2ndRenderRequest.log
jboss-only-2ndRenderRequest.log
Different render requests between WebSphere consumer and GateIn consumer to a GateIn
producer.
Problem with PRPs and WebSphere interoperability
------------------------------------------------
Key: GTNWSRP-178
URL: https://jira.jboss.org/browse/GTNWSRP-178
Project: GateIn WSRP
Issue Type: Bug
Components: Producer
Affects Versions: 2.0.0-CR03
Reporter: Chris Laprun
Assignee: Chris Laprun
Labels: BetaProgram
Fix For: 2.0.0-GA
Attachments: jboss-only-2ndRenderRequest.log,
websphere-to-jboss-2ndRenderRequest.log
We got two portlets on a single page. The first one sets a public render parameter, the
second one prints it out. This works well locally and between two jboss instances.
Then we created a page with two remote portlets on websphere, while running both portlets
in the same jboss instance.
Websphere gets the parameter from the action response and send this back to jboss, but in
a different block, using wsrp extras. So the second portlet actually don't see that
value.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:29 a.m.
New subject: [JBoss JIRA] Work started: (GTNWSRP-178) Problem with PRPs and WebSphere interoperability
[
https://jira.jboss.org/browse/GTNWSRP-178?page=com.atlassian.jira.plugin....
]
Work on GTNWSRP-178 started by Chris Laprun.
Problem with PRPs and WebSphere interoperability
------------------------------------------------
Key: GTNWSRP-178
URL: https://jira.jboss.org/browse/GTNWSRP-178
Project: GateIn WSRP
Issue Type: Bug
Components: Producer
Affects Versions: 2.0.0-CR03
Reporter: Chris Laprun
Assignee: Chris Laprun
Labels: BetaProgram
Fix For: 2.0.0-GA
Attachments: jboss-only-2ndRenderRequest.log,
websphere-to-jboss-2ndRenderRequest.log
We got two portlets on a single page. The first one sets a public render parameter, the
second one prints it out. This works well locally and between two jboss instances.
Then we created a page with two remote portlets on websphere, while running both portlets
in the same jboss instance.
Websphere gets the parameter from the action response and send this back to jboss, but in
a different block, using wsrp extras. So the second portlet actually don't see that
value.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:15 a.m.
New subject: [JBoss JIRA] Commented: (GTNWSRP-178) Problem with PRPs and WebSphere interoperability
[
https://jira.jboss.org/browse/GTNWSRP-178?page=com.atlassian.jira.plugin....
]
Chris Laprun commented on GTNWSRP-178:
--------------------------------------
I've checked that the producer properly passes the PRPs using
NavigationalContext.publicValues as expected, so it does really seem to me that the
problem lies on the WebSphere side.
Problem with PRPs and WebSphere interoperability
------------------------------------------------
Key: GTNWSRP-178
URL: https://jira.jboss.org/browse/GTNWSRP-178
Project: GateIn WSRP
Issue Type: Bug
Components: Producer
Affects Versions: 2.0.0-CR03
Reporter: Chris Laprun
Assignee: Chris Laprun
Labels: BetaProgram
Fix For: 2.0.0-GA
Attachments: jboss-only-2ndRenderRequest.log,
websphere-to-jboss-2ndRenderRequest.log
We got two portlets on a single page. The first one sets a public render parameter, the
second one prints it out. This works well locally and between two jboss instances.
Then we created a page with two remote portlets on websphere, while running both portlets
in the same jboss instance.
Websphere gets the parameter from the action response and send this back to jboss, but in
a different block, using wsrp extras. So the second portlet actually don't see that
value.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:10 a.m.
New subject: [JBoss JIRA] Commented: (GTNWSRP-178) Problem with PRPs and WebSphere interoperability
[
https://jira.jboss.org/browse/GTNWSRP-178?page=com.atlassian.jira.plugin....
]
Chris Laprun commented on GTNWSRP-178:
--------------------------------------
Apparently, this was a configuration error in portlet.xml. To be confirmed, though.
Problem with PRPs and WebSphere interoperability
------------------------------------------------
Key: GTNWSRP-178
URL: https://jira.jboss.org/browse/GTNWSRP-178
Project: GateIn WSRP
Issue Type: Bug
Components: Producer
Affects Versions: 2.0.0-CR03
Reporter: Chris Laprun
Assignee: Chris Laprun
Labels: BetaProgram
Fix For: 2.0.0-GA
Attachments: jboss-only-2ndRenderRequest.log,
websphere-to-jboss-2ndRenderRequest.log
We got two portlets on a single page. The first one sets a public render parameter, the
second one prints it out. This works well locally and between two jboss instances.
Then we created a page with two remote portlets on websphere, while running both portlets
in the same jboss instance.
Websphere gets the parameter from the action response and send this back to jboss, but in
a different block, using wsrp extras. So the second portlet actually don't see that
value.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:04 a.m.
New subject: [JBoss JIRA] Resolved: (GTNWSRP-178) Problem with PRPs and WebSphere interoperability
[
https://jira.jboss.org/browse/GTNWSRP-178?page=com.atlassian.jira.plugin....
]
Chris Laprun resolved GTNWSRP-178.
----------------------------------
Resolution: Done
Problem with PRPs and WebSphere interoperability
------------------------------------------------
Key: GTNWSRP-178
URL: https://jira.jboss.org/browse/GTNWSRP-178
Project: GateIn WSRP
Issue Type: Bug
Components: Producer
Affects Versions: 2.0.0-CR03
Reporter: Chris Laprun
Assignee: Chris Laprun
Labels: BetaProgram
Fix For: 2.0.0-GA
Attachments: jboss-only-2ndRenderRequest.log,
websphere-to-jboss-2ndRenderRequest.log
We got two portlets on a single page. The first one sets a public render parameter, the
second one prints it out. This works well locally and between two jboss instances.
Then we created a page with two remote portlets on websphere, while running both portlets
in the same jboss instance.
Websphere gets the parameter from the action response and send this back to jboss, but in
a different block, using wsrp extras. So the second portlet actually don't see that
value.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5139
days inactive
5143
days old
5 comments
1 participants
participants (1)
-
Chris Laprun (JIRA)