February 2013 - gatein-issues - Jboss List Archives

[JBoss JIRA] (GTNPC-102) Provide readme on how to run the AS 7 tests.

by Chris Laprun (JIRA)

[ https://issues.jboss.org/browse/GTNPC-102?page=com.atlassian.jira.plugin.... ] Chris Laprun resolved GTNPC-102. -------------------------------- Fix Version/s: 2.4.1.CR02 Resolution: Done > Provide readme on how to run the AS 7 tests. > -------------------------------------------- > > Key: GTNPC-102 > URL: https://issues.jboss.org/browse/GTNPC-102 > Project: GateIn Portlet Container > Issue Type: Enhancement > Reporter: Chris Laprun > Priority: Optional > Fix For: 2.4.1.CR02 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (GTNWSRP-349) When exporting a portlet, the returned portlet handle should be the same as the one provided during the export

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNWSRP-349?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration updated GTNWSRP-349: -------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=908853 > When exporting a portlet, the returned portlet handle should be the same as the one provided during the export > -------------------------------------------------------------------------------------------------------------- > > Key: GTNWSRP-349 > URL: https://issues.jboss.org/browse/GTNWSRP-349 > Project: GateIn WSRP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Interop, Producer > Affects Versions: 2.1.7-GA, 2.2.2.Final > Reporter: Chris Laprun > Assignee: Chris Laprun > Fix For: 2.1.8-GA, 2.2.3.Final > > > Third-party consumers might be confused when the returned portlet handle differs from the provided one even though the specification doesn't mandate them to be identical... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (GTNPC-101) When importing a portlet, the portlet id used for the associated state should refer to the original portlet

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPC-101?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated GTNPC-101: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=908853 > When importing a portlet, the portlet id used for the associated state should refer to the original portlet > ----------------------------------------------------------------------------------------------------------- > > Key: GTNPC-101 > URL: https://issues.jboss.org/browse/GTNPC-101 > Project: GateIn Portlet Container > Issue Type: Feature Request > Affects Versions: 2.3.1-GA, 2.3.2-GA, 2.4.1.CR01 > Reporter: Chris Laprun > Fix For: 2.4.1.CR02 > > > If the PortletContext passed to the import method refers to a clone, then import currently creates a state that refers to the clone portlet id, which cannot be resolved anymore by the portlet container. Instead, the import method should look at the associated state to figure out what which portlet the cloned PortletContext refers to so that the state associated with the import properly refers to a portlet id that can always be resolved. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (GTNPC-102) Provide readme on how to run the AS 7 tests.

by Chris Laprun (JIRA)

Chris Laprun created GTNPC-102: ---------------------------------- Summary: Provide readme on how to run the AS 7 tests. Key: GTNPC-102 URL: https://issues.jboss.org/browse/GTNPC-102 Project: GateIn Portlet Container Issue Type: Enhancement Reporter: Chris Laprun Priority: Optional -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (GTNWSRP-349) When exporting a portlet, the returned portlet handle should be the same as the one provided during the export

by Chris Laprun (JIRA)

Chris Laprun created GTNWSRP-349: ------------------------------------ Summary: When exporting a portlet, the returned portlet handle should be the same as the one provided during the export Key: GTNWSRP-349 URL: https://issues.jboss.org/browse/GTNWSRP-349 Project: GateIn WSRP Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Interop, Producer Affects Versions: 2.2.2.Final, 2.1.7-GA Reporter: Chris Laprun Assignee: Chris Laprun Fix For: 2.1.8-GA, 2.2.3.Final Third-party consumers might be confused when the returned portlet handle differs from the provided one even though the specification doesn't mandate them to be identical... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (GTNPC-101) When importing a portlet, the portlet id used for the associated state should refer to the original portlet

by Chris Laprun (JIRA)

[ https://issues.jboss.org/browse/GTNPC-101?page=com.atlassian.jira.plugin.... ] Chris Laprun updated GTNPC-101: ------------------------------- Fix Version/s: 2.4.1.CR02 Affects Version/s: 2.4.1.CR01 2.3.2-GA 2.3.1-GA > When importing a portlet, the portlet id used for the associated state should refer to the original portlet > ----------------------------------------------------------------------------------------------------------- > > Key: GTNPC-101 > URL: https://issues.jboss.org/browse/GTNPC-101 > Project: GateIn Portlet Container > Issue Type: Feature Request > Affects Versions: 2.3.1-GA, 2.3.2-GA, 2.4.1.CR01 > Reporter: Chris Laprun > Fix For: 2.4.1.CR02 > > > If the PortletContext passed to the import method refers to a clone, then import currently creates a state that refers to the clone portlet id, which cannot be resolved anymore by the portlet container. Instead, the import method should look at the associated state to figure out what which portlet the cloned PortletContext refers to so that the state associated with the import properly refers to a portlet id that can always be resolved. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (GTNPC-101) When importing a portlet, the portlet id used for the associated state should refer to the original portlet

by Chris Laprun (JIRA)

Chris Laprun created GTNPC-101: ---------------------------------- Summary: When importing a portlet, the portlet id used for the associated state should refer to the original portlet Key: GTNPC-101 URL: https://issues.jboss.org/browse/GTNPC-101 Project: GateIn Portlet Container Issue Type: Feature Request Reporter: Chris Laprun If the PortletContext passed to the import method refers to a clone, then import currently creates a state that refers to the clone portlet id, which cannot be resolved anymore by the portlet container. Instead, the import method should look at the associated state to figure out what which portlet the cloned PortletContext refers to so that the state associated with the import properly refers to a portlet id that can always be resolved. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (GTNMGMT-41) Command "mgmt connect" responds "Error: could not authenticate user" for unauthorized but authenticated users

by Nick Scavelli (JIRA)

[ https://issues.jboss.org/browse/GTNMGMT-41?page=com.atlassian.jira.plugin... ] Nick Scavelli resolved GTNMGMT-41. ---------------------------------- Fix Version/s: 2.0.0-Alpha01 Resolution: Out of Date This is a non-issue now since authentication is done only once during ssh connection. mgmt connect now only connects to a portal container. > Command "mgmt connect" responds "Error: could not authenticate user" for unauthorized but authenticated users > ------------------------------------------------------------------------------------------------------------- > > Key: GTNMGMT-41 > URL: https://issues.jboss.org/browse/GTNMGMT-41 > Project: GateIn Management > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: cli > Affects Versions: 1.0.0-GA > Reporter: Tomas Kyjovsky > Assignee: Nick Scavelli > Priority: Minor > Fix For: 2.0.0-Alpha01 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (GTNMGMT-34) Allow pretty print option for REST responses in JSON and XML format

by Nick Scavelli (JIRA)

[ https://issues.jboss.org/browse/GTNMGMT-34?page=com.atlassian.jira.plugin... ] Nick Scavelli resolved GTNMGMT-34. ---------------------------------- Fix Version/s: 2.0.0-Alpha01 (was: 2.0.0-Beta01) Resolution: Done Pretty print flag is passed to marshallers, however it's up to implementation to support it. > Allow pretty print option for REST responses in JSON and XML format > ------------------------------------------------------------------- > > Key: GTNMGMT-34 > URL: https://issues.jboss.org/browse/GTNMGMT-34 > Project: GateIn Management > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: rest > Reporter: Nick Scavelli > Assignee: Nick Scavelli > Priority: Minor > Fix For: 2.0.0-Alpha01 > > > Allow REST services to return JSON and XML responses in pretty format by supporting a http parameter 'pretty'. If the parameter is present, the response should be formatted with line breaks, tabs, etc. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (GTNMGMT-46) Support registration of sub resources by returning @Managed object within @Managed classes.

by Nick Scavelli (JIRA)

[ https://issues.jboss.org/browse/GTNMGMT-46?page=com.atlassian.jira.plugin... ] Nick Scavelli resolved GTNMGMT-46. ---------------------------------- Fix Version/s: 2.0.0-Alpha01 (was: 2.0.0-Beta01) Resolution: Done > Support registration of sub resources by returning @Managed object within @Managed classes. > ------------------------------------------------------------------------------------------- > > Key: GTNMGMT-46 > URL: https://issues.jboss.org/browse/GTNMGMT-46 > Project: GateIn Management > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: api, spi > Reporter: Nick Scavelli > Assignee: Nick Scavelli > Fix For: 2.0.0-Alpha01 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues February 2013