You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oodt.apache.org by "Lewis John McGibbney (JIRA)" <ji...@apache.org> on 2013/03/21 03:29:15 UTC
[jira] [Commented] (OODT-578) Workflow Monitor experiences runtime
exception (NPE) out of the box with RADIX
[ https://issues.apache.org/jira/browse/OODT-578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13608548#comment-13608548 ]
Lewis John McGibbney commented on OODT-578:
-------------------------------------------
Hi,
I can reproduce this with many aspects of the Wicket driven opsui application.
I must make it explicit that I have not read any data into the CAS Metadata Catalogue yet.
I merely built the RADiX project and started up the tomcat server.
When I point my browser to the opsui web application available within Tomcat, I experience numerous Exceptions from many pages.
@Arni, can you please describe how you are experiencing the problem please?
Does this only happen when you navigate to the workflow monitor page?
> Workflow Monitor experiences runtime exception (NPE) out of the box with RADIX
> ------------------------------------------------------------------------------
>
> Key: OODT-578
> URL: https://issues.apache.org/jira/browse/OODT-578
> Project: OODT
> Issue Type: Bug
> Components: opsui
> Affects Versions: 0.6
> Environment: RADiX used with the following flags:-DarchetypeVersion=0.6-SNAPSHOT -Doodt=0.6-SNAPSHOT
> Reporter: Arni Sumarlidason
> Assignee: Chris A. Mattmann
> Labels: OPSUI, RADiX, workflow
> Fix For: 0.6
>
> Attachments: OODT-578_031913_sumarlidason.arni.patch.txt
>
>
> Page fails to load, run time exception: java.lang.NullPointerException
> WicketMessage: Can't instantiate page using constructor public org.apache.oodt.pcs.opsui.WorkflowInstanceViewerPage(org.apache.wicket.PageParameters) and argument status = "ALL" pageNum = "1"
> Reproduce:
> Build oodt with RADiX, deploy, and start. Visit http://localhost:8080/opsui/ and click on "workflow monitor".
--
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