View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-portal-2.6-testsuite?log=log20070405200025

TESTS FAILED
Ant Error Message: /services/cruisecontrol/work/scripts/build-jboss-portal.xml:204: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.
Date of build: 04/05/2007 20:00:25
Time to build: 84 minutes 22 seconds
Last changed: 04/05/2007 18:19:51
Last log entry: don't set on PageResult both layoutState and layoutURI. LayoutURI can be deduced from the layoutState (which is the real intention) + the layout object just before doing the request dispatching to the layout servlet. Furthermore layoutURI is an internal implementation detail of the fact that the layouting of the different regions is done primarily by a JSP

 Unit Tests: (2382)  Total Errors and Failures: (37)
testGetterOverrideorg.jboss.portal.test.common.JavaBeanModelMBeanBuilderTestCase(4_0_4_GA)
testAttributesAreNotCachedorg.jboss.portal.test.common.JavaBeanModelMBeanBuilderTestCase(4_0_4_GA)
testStaticAttributeorg.jboss.portal.test.common.JavaBeanModelMBeanBuilderTestCase(4_0_4_GA)
testGetterOverrideorg.jboss.portal.test.common.JavaBeanModelMBeanBuilderTestCase(4_0_5_GA)
testAttributesAreNotCachedorg.jboss.portal.test.common.JavaBeanModelMBeanBuilderTestCase(4_0_5_GA)
testStaticAttributeorg.jboss.portal.test.common.JavaBeanModelMBeanBuilderTestCase(4_0_5_GA)
testGetterOverrideorg.jboss.portal.test.common.JavaBeanModelMBeanBuilderTestCase(4_0_x)
testAttributesAreNotCachedorg.jboss.portal.test.common.JavaBeanModelMBeanBuilderTestCase(4_0_x)
testStaticAttributeorg.jboss.portal.test.common.JavaBeanModelMBeanBuilderTestCase(4_0_x)
testGetPortletPropertyDescriptionorg.jboss.portal.test.wsrp.v1.producer.PortletManagementTestRunner(4_0_4_GA)
testModifyRegistrationorg.jboss.portal.test.wsrp.v1.producer.RegistrationTestRunner(4_0_4_GA)
testDeregisterorg.jboss.portal.test.wsrp.v1.producer.RegistrationTestRunner(4_0_4_GA)
testGetServiceDescriptionRequiringRegistrationOfferedPortletsorg.jboss.portal.test.wsrp.v1.producer.ServiceDescriptionTestRunner(4_0_4_GA)
testGetServiceDescriptionRequiringRegistrationNoOfferedPortletsorg.jboss.portal.test.wsrp.v1.producer.ServiceDescriptionTestRunner(4_0_4_GA)
PortalInfoorg.jboss.portal.test.portlet.jsr168.api.PortalContextTestCase(4_0_4_GA)
PortalInfoorg.jboss.portal.test.portlet.jsr168.api.PortalContextTestCase(4_0_5_GA)
PortalInfoorg.jboss.portal.test.portlet.jsr168.api.PortalContextTestCase(4_0_x)
testInitCookieorg.jboss.portal.test.wsrp.v1.consumer.MarkupTestRunner(4_0_x)
testSessionHandlingorg.jboss.portal.test.wsrp.v1.consumer.MarkupTestRunner(4_0_x)
 

 Modifications since last build:  (first 50 of 147)
6933modifiedjulien@jboss.com//trunk/core/src/main/org/jboss/portal/core/model/portal/command/RenderPageCommand.javadon't set on PageResult both layoutState and layoutURI. LayoutURI can be deduced from the layoutState (which is the real intention) + the layout object just before doing the request dispatching to the layout servlet. Furthermore layoutURI is an internal implementation detail of the fact that the layouting of the different regions is done primarily by a JSP
6933modifiedjulien@jboss.com//trunk/theme/src/main/org/jboss/portal/test/theme/tmp/render/TestRenderedMarkup.javadon't set on PageResult both layoutState and layoutURI. LayoutURI can be deduced from the layoutState (which is the real intention) + the layout object just before doing the request dispatching to the layout servlet. Furthermore layoutURI is an internal implementation detail of the fact that the layouting of the different regions is done primarily by a JSP
6933modifiedjulien@jboss.com//trunk/core/src/main/org/jboss/portal/core/model/instance/command/InvokePortletInstanceRenderCommand.javadon't set on PageResult both layoutState and layoutURI. LayoutURI can be deduced from the layoutState (which is the real intention) + the layout object just before doing the request dispatching to the layout servlet. Furthermore layoutURI is an internal implementation detail of the fact that the layouting of the different regions is done primarily by a JSP
6933modifiedjulien@jboss.com//trunk/theme/src/main/org/jboss/portal/theme/page/PageResult.javadon't set on PageResult both layoutState and layoutURI. LayoutURI can be deduced from the layoutState (which is the real intention) + the layout object just before doing the request dispatching to the layout servlet. Furthermore layoutURI is an internal implementation detail of the fact that the layouting of the different regions is done primarily by a JSP
6933modifiedjulien@jboss.com//trunk/theme/src/main/org/jboss/portal/test/theme/tmp/servlet/TestThemeServlet.javadon't set on PageResult both layoutState and layoutURI. LayoutURI can be deduced from the layoutState (which is the real intention) + the layout object just before doing the request dispatching to the layout servlet. Furthermore layoutURI is an internal implementation detail of the fact that the layouting of the different regions is done primarily by a JSP
6933modifiedjulien@jboss.com//trunk/theme/src/main/org/jboss/portal/theme/impl/JSPLayout.javadon't set on PageResult both layoutState and layoutURI. LayoutURI can be deduced from the layoutState (which is the real intention) + the layout object just before doing the request dispatching to the layout servlet. Furthermore layoutURI is an internal implementation detail of the fact that the layouting of the different regions is done primarily by a JSP
6933modifiedjulien@jboss.com//trunk/theme/src/main/org/jboss/portal/test/theme/TestServlet.javadon't set on PageResult both layoutState and layoutURI. LayoutURI can be deduced from the layoutState (which is the real intention) + the layout object just before doing the request dispatching to the layout servlet. Furthermore layoutURI is an internal implementation detail of the fact that the layouting of the different regions is done primarily by a JSP
6932modifiedjulien@jboss.com//trunk/core/src/main/org/jboss/portal/core/model/portal/command/RenderPageCommand.javasimplify theme header rendering
6932modifiedjulien@jboss.com//trunk/theme/src/main/org/jboss/portal/theme/page/PageResult.javasimplify theme header rendering
6932modifiedjulien@jboss.com//trunk/theme/src/main/org/jboss/portal/theme/tag/ThemeTagHandler.javasimplify theme header rendering
6932modifiedjulien@jboss.com//trunk/theme/src/main/org/jboss/portal/theme/impl/WARTheme.javasimplify theme header rendering
6932modifiedjulien@jboss.com//trunk/theme/src/main/org/jboss/portal/theme/ThemeConstants.javasimplify theme header rendering
6932deletedjulien@jboss.com//trunk/theme/src/main/org/jboss/portal/theme/ThemeResult.javasimplify theme header rendering
6932modifiedjulien@jboss.com//trunk/theme/src/main/org/jboss/portal/theme/PortalTheme.javasimplify theme header rendering
6932modifiedjulien@jboss.com//trunk/theme/src/main/org/jboss/portal/theme/page/PageRendition.javasimplify theme header rendering
6931modifiedchris.laprun@jboss.com//trunk/wsrp/src/main/org/jboss/portal/wsrp/servlet/ReleaseSessionsSessionListener.java- Now implements PortalEventListener and uses Portal-level events.- Still needs to be wired as a service...
6930modifiedjulien@jboss.com//trunk/build/build.xmladding web module into build
6929modifiedjulien@jboss.com//trunk/portlet/src/main/org/jboss/portal/portlet/aspects/portlet/ContextDispatcherInterceptor.javaextract the servlet container spi into a 'web' module. it will probably contains different implementations in the future
6929modifiedjulien@jboss.com//trunk/build/ide/intellij/idea60/modules/core/core.imlextract the servlet container spi into a 'web' module. it will probably contains different implementations in the future
6929modifiedjulien@jboss.com//trunk/theme/src/main/org/jboss/portal/theme/LayoutDispatcher.javaextract the servlet container spi into a 'web' module. it will probably contains different implementations in the future
6929modifiedjulien@jboss.com//trunk/server/src/resources/test/test-charset-sar/META-INF/jboss-service.xmlextract the servlet container spi into a 'web' module. it will probably contains different implementations in the future
6929modifiedjulien@jboss.com//trunk/theme/src/main/org/jboss/portal/theme/page/PageResult.javaextract the servlet container spi into a 'web' module. it will probably contains different implementations in the future
6929addedjulien@jboss.com//trunk/web/src/main/org/jbossextract the servlet container spi into a 'web' module. it will probably contains different implementations in the future
6929modifiedjulien@jboss.com//trunk/theme/build.xmlextract the servlet container spi into a 'web' module. it will probably contains different implementations in the future
6929modifiedjulien@jboss.com//trunk/server/src/resources/test/test-response-sar/META-INF/jboss-service.xmlextract the servlet container spi into a 'web' module. it will probably contains different implementations in the future
6929modifiedjulien@jboss.com//trunk/theme/src/main/org/jboss/portal/theme/impl/JSPLayout.javaextract the servlet container spi into a 'web' module. it will probably contains different implementations in the future
6929addedjulien@jboss.com//trunk/server/src/main/org/jboss/portal/webextract the servlet container spi into a 'web' module. it will probably contains different implementations in the future
6929addedjulien@jboss.com//trunk/theme/src/bin/test/theme-test-war/WEB-INF/portal-renderSet.xmlextract the servlet container spi into a 'web' module. it will probably contains different implementations in the future
6929modifiedjulien@jboss.com//trunk/server/src/main/org/jboss/portal/server/impl/ServerImpl.javaextract the servlet container spi into a 'web' module. it will probably contains different implementations in the future
6929modifiedjulien@jboss.com//trunk/theme/src/main/org/jboss/portal/theme/render/RenderContext.javaextract the servlet container spi into a 'web' module. it will probably contains different implementations in the future
6929addedjulien@jboss.com//trunk/theme/src/bin/test/theme-test-war/WEB-INFextract the servlet container spi into a 'web' module. it will probably contains different implementations in the future
6929deletedjulien@jboss.com//trunk/portlet-server/src/main/org/jboss/portal/web/jbossextract the servlet container spi into a 'web' module. it will probably contains different implementations in the future
6929modifiedjulien@jboss.com//trunk/portlet/src/main/org/jboss/portal/portlet/spi/RequestContext.javaextract the servlet container spi into a 'web' module. it will probably contains different implementations in the future
6929addedjulien@jboss.com//trunk/webextract the servlet container spi into a 'web' module. it will probably contains different implementations in the future
6929addedjulien@jboss.com//trunk/web/src/main/org/jboss/portal/webextract the servlet container spi into a 'web' module. it will probably contains different implementations in the future
6929modifiedjulien@jboss.com//trunk/build/ide/intellij/idea60/modules/theme/theme.imlextract the servlet container spi into a 'web' module. it will probably contains different implementations in the future
6929modifiedjulien@jboss.com//trunk/tools/etc/buildfragments/modules.entextract the servlet container spi into a 'web' module. it will probably contains different implementations in the future
6929modifiedjulien@jboss.com//trunk/core/src/resources/portal-core-sar/META-INF/jboss-service.xmlextract the servlet container spi into a 'web' module. it will probably contains different implementations in the future
6929addedjulien@jboss.com//trunk/web/build.batextract the servlet container spi into a 'web' module. it will probably contains different implementations in the future
6929modifiedjulien@jboss.com//trunk/server/src/main/org/jboss/portal/server/Server.javaextract the servlet container spi into a 'web' module. it will probably contains different implementations in the future
6929addedjulien@jboss.com//trunk/web/build.shextract the servlet container spi into a 'web' module. it will probably contains different implementations in the future
6929addedjulien@jboss.com//trunk/server/src/main/org/jboss/portal/web/jbossextract the servlet container spi into a 'web' module. it will probably contains different implementations in the future
6929modifiedjulien@jboss.com//trunk/core/build.xmlextract the servlet container spi into a 'web' module. it will probably contains different implementations in the future
6929modifiedjulien@jboss.com//trunk/server/src/resources/test/test-servlet-sar/META-INF/jboss-service.xmlextract the servlet container spi into a 'web' module. it will probably contains different implementations in the future
6929modifiedjulien@jboss.com//trunk/portlet/build.xmlextract the servlet container spi into a 'web' module. it will probably contains different implementations in the future
6929modifiedjulien@jboss.com//trunk/wsrp/src/resources/tests/test-wsrp-producer-sar/META-INF/jboss-service.xmlextract the servlet container spi into a 'web' module. it will probably contains different implementations in the future
6929addedjulien@jboss.com//trunk/web/src/mainextract the servlet container spi into a 'web' module. it will probably contains different implementations in the future
6929modifiedjulien@jboss.com//trunk/core/src/main/org/jboss/portal/core/controller/ajax/AjaxResponseHandler.javaextract the servlet container spi into a 'web' module. it will probably contains different implementations in the future
6929deletedjulien@jboss.com//trunk/portlet/src/main/org/jboss/portal/web/spi/RequestDispatchCallback.javaextract the servlet container spi into a 'web' module. it will probably contains different implementations in the future
6929modifiedjulien@jboss.com//trunk/portlet-server/build.xmlextract the servlet container spi into a 'web' module. it will probably contains different implementations in the future