Bug 777807 (SOA-333) - Need to document workaround for SOA-250 in SOA-P 4.2 release notes
Summary: Need to document workaround for SOA-250 in SOA-P 4.2 release notes
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-333
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: Documentation
Version: 4.2 Beta 1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.2 CR1
Assignee: Joshua Wulf
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-01-16 16:14 UTC by Len DiMaggio
Modified: 2014-10-19 22:59 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-01-20 13:25:48 UTC
Type: Task


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-333 0 None None None Never

Description Len DiMaggio 2008-01-16 16:14:17 UTC
Affects: Documentation (Ref Guide, User Guide, etc.), Release Notes
Date of First Response: 2008-01-20 07:39:42
project_key: SOA

The workaround for the problem is described in detail here:

       http://jira.jboss.com/jira/browse/SOA-250#action_12395346

Comment 1 Mark Little 2008-01-16 17:19:45 UTC
Affects: Added: [Documentation (Ref Guide, User Guide, etc.), Release Notes]


Comment 2 Joshua Wulf 2008-01-20 12:39:42 UTC
==Release Note text==

Problem generating a form for a task via (jBPM) GPD if the task properties dialog is maximized
            
n JBoss Developer Studio, jbpm-jpdl-designer-3.1.2, or jbpm-jpdl-designer-3.1.0.SP1, generating a form for a task while the properties dialog is maximized results in a dialogue that will not respond when the OK button is clicked. Examining the log reveals a java.lang.NullPointerException. At this time the workaround is to generate the form without the properties dialog maximized. Additionally, you should avoid using whitespaces in task names, as this can also cause problems with form generation.  


Note You need to log in before you can comment on or make changes to this bug.