[JBoss JIRA] (GTNPORTAL-2691) Sample Portal rendered without RightHome.jpg Background image
by Peter Palaga (JIRA)
Peter Palaga created GTNPORTAL-2691:
---------------------------------------
Summary: Sample Portal rendered without RightHome.jpg Background image
Key: GTNPORTAL-2691
URL: https://issues.jboss.org/browse/GTNPORTAL-2691
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Peter Palaga
Assignee: Peter Palaga
In
{code}examples/portal/war/src/main/webapp/templates/skin/webui/component/UIHomePagePortlet/DefaultStylesheet.css{code}
a semicolon is missing before {{/* orientation=rt */}} in the following rule:
{code}
.UIHomePagePortlet .AdImageLeft {
background: url('DefaultSkin/background/RightHome.jpg') no-repeat left top; /* orientation=lt */
background: url('DefaultSkin/background/RightHome-rt.jpg') no-repeat right top; /* orientation=rt */
}
{code}
--
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, 6 months
[JBoss JIRA] (GTNPORTAL-2687) Improve Maven Build of Sample Portal and Extension
by Peter Palaga (JIRA)
Peter Palaga created GTNPORTAL-2687:
---------------------------------------
Summary: Improve Maven Build of Sample Portal and Extension
Key: GTNPORTAL-2687
URL: https://issues.jboss.org/browse/GTNPORTAL-2687
Project: GateIn Portal
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Peter Palaga
Assignee: Peter Palaga
(1) Config projects
Maven jar packager does not include
src/main/java/conf/configuration.xml
This is a problem in both portal and extension config projects.
conf/configuration.xml needs to be moved from src/main/java to
src/main/resources
(2) EAR
(2.1) Delete src/main/application/META-INF/gatein-jboss-beans.xml
(2.2) Move MANIFEST.MF from
packaging/jboss-as7/pkg/src/main/resources/jboss/samples/gatein/extensions/*/META-INF
to src/main/resources of the respective projects and configure
maven-ear-plugin to use
<manifestFile>src/main/resources/META-INF/MANIFEST.MF</manifestFile>
(2.3) remove the two application.xml files from
packaging/jboss-as7/pkg/src/main/resources/jboss/samples/gatein/extensions/*/META-INF
and configure maven-ear-plugin to reach the same result which can be
done very easily.
(2.4) Adjust the the ant code in
packaging/jboss-as7/pkg/package.xml
to the changes done in (2.3) and (2.4).
Open question:
* Is it OK to make the GateIn build process to use EAR archives instead
of *.ear directories to deploy the samples?
--
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, 6 months
[JBoss JIRA] (GTNWSRP-317) WSRP Admin is not rendered in cluster profile
by Michal Vanco (JIRA)
Michal Vanco created GTNWSRP-317:
------------------------------------
Summary: WSRP Admin is not rendered in cluster profile
Key: GTNWSRP-317
URL: https://issues.jboss.org/browse/GTNWSRP-317
Project: GateIn WSRP
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Admin GUI
Affects Versions: 2.2.0.Beta08
Environment: GateIn - master from Oct 16
Reporter: Michal Vanco
Assignee: Chris Laprun
Fix For: 2.2.0
When you start portal in cluster profile, WSRP admin isn't displayed.
Error log & screen attached.
To start portal in cluster profile, simply run:
sh standalone.sh -c standalone-ha.xml
(all required system properties for clustering are part of standalone-ha.xml, you could also need to set -u multicast-addr1 -Dgatein.jgroups3.udp.mcast_addr=multicast-addr2 -Djboss.jgroups.udp_async.mcast_addr=multicast-addr3 with some 3 multicast addressed for cluster isolation)
--
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, 6 months
[JBoss JIRA] (GTNPORTAL-2576) Update WSRP module definition to use proper version of Apache HttpClient
by Chris Laprun (JIRA)
Chris Laprun created GTNPORTAL-2576:
---------------------------------------
Summary: Update WSRP module definition to use proper version of Apache HttpClient
Key: GTNPORTAL-2576
URL: https://issues.jboss.org/browse/GTNPORTAL-2576
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Packaging
Affects Versions: 3.4.0.Final
Reporter: Chris Laprun
Fix For: 3.5.0.Beta01
WSRP uses Apache httpclient 3.1 which is not compatible with the newer Apache httpcomponents library that's bundled with AS 7, resulting in class not found exceptions.
Long term solution should probably be to migrate WSRP to httpcomponents.
--
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, 6 months
[JBoss JIRA] (GTNPORTAL-2602) IllegalStateException on shutdown on AS7
by Boleslaw Dawidowicz (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-2602?page=com.atlassian.jira.pl... ]
Boleslaw Dawidowicz updated GTNPORTAL-2602:
-------------------------------------------
Fix Version/s: 3.5.0.Beta02
(was: 3.5.0.Beta01)
> IllegalStateException on shutdown on AS7
> ----------------------------------------
>
> Key: GTNPORTAL-2602
> URL: https://issues.jboss.org/browse/GTNPORTAL-2602
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Packaging
> Reporter: Chris Laprun
> Priority: Minor
> Fix For: 3.5.0.Beta02
>
>
> {code}
> 1:43:52,396 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/sample-ext]] Exception sending context destroyed event to listener instance of class org.exoplatform.container.web.PortalContainerConfigOwner: java.lang.IllegalStateException: No pre init tasks can be added to the portal container 'portal', because it has already been initialized. Check the webapp 'sample-ext'
> at org.exoplatform.container.RootContainer$PortalContainerPreInitTask.onAlreadyExists(RootContainer.java:1305) [exo.kernel.container-2.4.0-Beta01.jar:2.4.0-Beta01]
> at org.exoplatform.container.RootContainer.addInitTask(RootContainer.java:1096) [exo.kernel.container-2.4.0-Beta01.jar:2.4.0-Beta01]
> at org.exoplatform.container.PortalContainer.addInitTask(PortalContainer.java:464) [exo.kernel.container-2.4.0-Beta01.jar:2.4.0-Beta01]
> at org.exoplatform.container.PortalContainer.addInitTask(PortalContainer.java:438) [exo.kernel.container-2.4.0-Beta01.jar:2.4.0-Beta01]
> at org.exoplatform.container.web.PortalContainerConfigOwner.contextDestroyed(PortalContainerConfigOwner.java:56) [exo.kernel.container-2.4.0-Beta01.jar:2.4.0-Beta01]
> at org.apache.catalina.core.StandardContext.listenerStop(StandardContext.java:3489) [jbossweb-7.0.16.Final.jar:]
> at org.apache.catalina.core.StandardContext.stop(StandardContext.java:3999) [jbossweb-7.0.16.Final.jar:]
> at org.jboss.as.web.deployment.WebDeploymentService.stop(WebDeploymentService.java:108) [jboss-as-web-7.1.2.Final.jar:7.1.2.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:1911)
> at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:1874)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [classes.jar:1.6.0_35]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_35]
> at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_35]
> {code}
--
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, 6 months