Bug 781168 (SOA-3670) - NullPointerException deploying a scheduled-listener with invalid scheduleidref attribute
Summary: NullPointerException deploying a scheduled-listener with invalid scheduleidre...
Keywords:
Status: CLOSED UPSTREAM
Alias: SOA-3670
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: JBossESB
Version: 5.2.0 GA
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-19 10:40 UTC by Martin Weiler
Modified: 2025-02-10 03:14 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-02-10 03:14:58 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBESB-3721 0 Major Open NullPointerException deploying a scheduled-listener with invalid scheduleidref attribute 2014-04-08 16:54:46 UTC
Red Hat Issue Tracker SOA-3670 0 Major Closed NullPointerException deploying a scheduled-listener with invalid scheduleidref attribute 2014-04-08 16:54:46 UTC

Description Martin Weiler 2011-12-19 10:40:20 UTC 
Help Desk Ticket Reference: https://na7.salesforce.com/500A0000008zBL9
project_key: SOA

Platform issue for JBESB-3721: NullPointerException deploying a scheduled-listener with invalid scheduleidref attribute
Comment 1 Martin Weiler 2011-12-19 10:40:53 UTC 
Link: Added: This issue depends JBESB-3721
Comment 2 Suz 2012-06-15 04:48:45 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
An error occurs when using deploying a scheduled-listener with invalid scheduleidref attribute. Upon deployment, a NullPointerException error will be displayed.
Comment 6 Red Hat Bugzilla 2025-02-10 03:14:58 UTC 
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.
Note You need to log in before you can comment on or make changes to this bug.