[JBoss JIRA] Updated: (JBIDE-1494) TextFomating tag should have default behaviour, now it is used as copy everywhere
by Denis Golovin (JIRA)
[ http://jira.jboss.com/jira/browse/JBIDE-1494?page=all ]
Denis Golovin updated JBIDE-1494:
---------------------------------
Summary: TextFomating tag should have default behaviour, now it is used as copy everywhere (was: TextFomating tag should have default bexaviour, now it is used as copy everywhere)
> TextFomating tag should have default behaviour, now it is used as copy everywhere
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-1494
> URL: http://jira.jboss.com/jira/browse/JBIDE-1494
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: Cleanup
> Affects Versions: 2.0.0.GA
> Reporter: Denis Golovin
> Assigned To: Maxim Areshkau
> Fix For: 2.1
>
>
> It should be renamed to vpe:textFormatting
> Now there ar ea lot of blocks like posted below:
> <vpe:textFormating>
> <vpe:format type="BlockFormat" addChildren="deny" />
> <vpe:format type="UnderlineFormat">
> <vpe:formatAttribute type="style" />
> </vpe:format>
> <vpe:format type="BoldFormat">
> <vpe:formatAttribute type="style" />
> </vpe:format>
> <vpe:format type="ItalicFormat">
> <vpe:formatAttribute type="style" />
> </vpe:format>
> <vpe:format type="FontNameFormat">
> <vpe:formatAttribute type="style" />
> </vpe:format>
> <vpe:format type="FontSizeFormat">
> <vpe:formatAttribute type="style" />
> </vpe:format>
> <vpe:format type="BackgroundColorFormat">
> <vpe:formatAttribute type="style" />
> </vpe:format>
> <vpe:format type="ForegroundColorFormat">
> <vpe:formatAttribute type="style" />
> </vpe:format>
> </vpe:textFormating>
> It should have default behavior that is defined by inserting just <vpe:textFormatting> tag inside template. If some behavior should be redefined use vpe:format tag for it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 3 months
[JBoss JIRA] Created: (JBIDE-1589) CLONE -JBDS - cannot generate a form for a task via (jBPM) GPD
by Koen Aers (JIRA)
CLONE -JBDS - cannot generate a form for a task via (jBPM) GPD
--------------------------------------------------------------
Key: JBIDE-1589
URL: http://jira.jboss.com/jira/browse/JBIDE-1589
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 2.0.0.GA
Environment: JBoss Developer Studio, Build id: 200712091205-nightly
and
Eclipse Europa + jbpm-jpdl-designer-3.0.13 Stable 9.2 MB 2007-01-25
Reporter: Koen Aers
Assigned To: Koen Aers
I'm unable to generate a new form for a task with either the 1.0 JBDS bits or Eclipse Europa + jbpm-jpdl-designer-3.0.13 Stable 9.2 MB 2007-01-25
To recreate the problem - using the attached jBPM process project - it's based on the 'holiday request' jBPM demo - at the start task node, attempt to generate a form.
The screen displayed in the screenshot attachment is brought up - pressing OK has no effect. The form xhtml file is not created - and no error/sttaus message is displayed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 3 months
[JBoss JIRA] Created: (JBIDE-1295) Allow @Destroy annotated methods in abstract Pojos
by Andy Gibson (JIRA)
Allow @Destroy annotated methods in abstract Pojos
--------------------------------------------------
Key: JBIDE-1295
URL: http://jira.jboss.com/jira/browse/JBIDE-1295
Project: JBoss Tools
Issue Type: Feature Request
Components: Seam
Environment: JBoss Tools nightly from 11/11/2007, Win XP SP2, JBoss 4.2.2, Seam 2.0 project , Eclipse 3.3.1.1
Reporter: Andy Gibson
It would be nice if we could create abstract classes with a @Destroy annotated method. While it appears possible to do this, the IDE complains that only components can have a @Destroy method, which is correct, but the class is abstract and will be subclassed as a component elsewhere. I think it will compile, deploy and run, but it puts several lines of red squiggles in the code which is distracting.
I'm requesting that the class be allowed to pass the validation if it is marked as abstract.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 3 months