You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Shammy Chen (JIRA)" <ji...@apache.org> on 2008/12/07 04:43:44 UTC

[jira] Created: (ODE-455) make ODE process DebuggerSupport configurable

make ODE process DebuggerSupport configurable
---------------------------------------------

                 Key: ODE-455
                 URL: https://issues.apache.org/jira/browse/ODE-455
             Project: ODE
          Issue Type: Improvement
          Components: BPEL Runtime
    Affects Versions: 1.2
         Environment: Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03)
            Reporter: Shammy Chen
            Priority: Minor


DebuggerSupport is needed and preferred when developing and debug a process,especially when encounting problems.But in production systems,we don't want process to be debugable,mainly for the following two reasons:

(1)performance
We want our process to run as fast as possible,so our system can handle more and more tasks

(2)safety
We can't bear a careless administartor to do any harm to the system,e.g. set Breakpoints and debug the process when the process is running.

Can we configure this behavior by change something in the deploy.xml file,just like 
<in-memory>true</in-memory>
or
<active>true</active>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (ODE-455) make ODE process DebuggerSupport configurable on per process basis

Posted by "Shammy Chen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/ODE-455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shammy Chen updated ODE-455:
----------------------------

    Description: 
DebuggerSupport is needed and preferred when developing and debugging a process,especially when encounting problems.But in production systems,we don't want process to be debugable,mainly for the following two reasons:

(1)performance
We want our process to run as fast as possible,so our system can handle more and more tasks

(2)safety
We can't bear a careless administartor to do any harm to the system,e.g. set Breakpoints and debug the process when the process is running.

Can we configure this behavior by change something in the deploy.xml file,just like 
<in-memory>true</in-memory>
or
<active>true</active>


  was:
DebuggerSupport is needed and preferred when developing and debug a process,especially when encounting problems.But in production systems,we don't want process to be debugable,mainly for the following two reasons:

(1)performance
We want our process to run as fast as possible,so our system can handle more and more tasks

(2)safety
We can't bear a careless administartor to do any harm to the system,e.g. set Breakpoints and debug the process when the process is running.

Can we configure this behavior by change something in the deploy.xml file,just like 
<in-memory>true</in-memory>
or
<active>true</active>


        Summary: make ODE process DebuggerSupport configurable on per process basis  (was: make ODE process DebuggerSupport configurable)

> make ODE process DebuggerSupport configurable on per process basis
> ------------------------------------------------------------------
>
>                 Key: ODE-455
>                 URL: https://issues.apache.org/jira/browse/ODE-455
>             Project: ODE
>          Issue Type: Improvement
>          Components: BPEL Runtime
>    Affects Versions: 1.2
>         Environment: Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03)
>            Reporter: Shammy Chen
>            Priority: Minor
>
> DebuggerSupport is needed and preferred when developing and debugging a process,especially when encounting problems.But in production systems,we don't want process to be debugable,mainly for the following two reasons:
> (1)performance
> We want our process to run as fast as possible,so our system can handle more and more tasks
> (2)safety
> We can't bear a careless administartor to do any harm to the system,e.g. set Breakpoints and debug the process when the process is running.
> Can we configure this behavior by change something in the deploy.xml file,just like 
> <in-memory>true</in-memory>
> or
> <active>true</active>

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (ODE-455) make ODE process DebuggerSupport configurable on per process basis

Posted by "Tammo van Lessen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/ODE-455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tammo van Lessen updated ODE-455:
---------------------------------

    Fix Version/s: 1.3.5

> make ODE process DebuggerSupport configurable on per process basis
> ------------------------------------------------------------------
>
>                 Key: ODE-455
>                 URL: https://issues.apache.org/jira/browse/ODE-455
>             Project: ODE
>          Issue Type: Improvement
>          Components: BPEL Runtime
>    Affects Versions: 1.2
>         Environment: Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03)
>            Reporter: Shammy Chen
>            Priority: Minor
>             Fix For: 1.3.5
>
>
> DebuggerSupport is needed and preferred when developing and debugging a process,especially when encounting problems.But in production systems,we don't want process to be debuggable,mainly for the following two reasons:
> (1)performance
> We want our process to run as fast as possible,so our system can handle more and more tasks
> (2)safety
> We can't bear a careless administartor to do any harm to the system,e.g. set Breakpoints and debug the process when the process is running.
> Can we configure this behavior by changing something in the deploy.xml file,just like 
> <in-memory>true</in-memory>
> or
> <active>true</active>

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Updated: (ODE-455) make ODE process DebuggerSupport configurable on per process basis

Posted by "Shammy Chen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/ODE-455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shammy Chen updated ODE-455:
----------------------------

    Description: 
DebuggerSupport is needed and preferred when developing and debugging a process,especially when encounting problems.But in production systems,we don't want process to be debuggable,mainly for the following two reasons:

(1)performance
We want our process to run as fast as possible,so our system can handle more and more tasks

(2)safety
We can't bear a careless administartor to do any harm to the system,e.g. set Breakpoints and debug the process when the process is running.

Can we configure this behavior by changing something in the deploy.xml file,just like 
<in-memory>true</in-memory>
or
<active>true</active>


  was:
DebuggerSupport is needed and preferred when developing and debugging a process,especially when encounting problems.But in production systems,we don't want process to be debuggable,mainly for the following two reasons:

(1)performance
We want our process to run as fast as possible,so our system can handle more and more tasks

(2)safety
We can't bear a careless administartor to do any harm to the system,e.g. set Breakpoints and debug the process when the process is running.

Can we configure this behavior by change something in the deploy.xml file,just like 
<in-memory>true</in-memory>
or
<active>true</active>



> make ODE process DebuggerSupport configurable on per process basis
> ------------------------------------------------------------------
>
>                 Key: ODE-455
>                 URL: https://issues.apache.org/jira/browse/ODE-455
>             Project: ODE
>          Issue Type: Improvement
>          Components: BPEL Runtime
>    Affects Versions: 1.2
>         Environment: Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03)
>            Reporter: Shammy Chen
>            Priority: Minor
>
> DebuggerSupport is needed and preferred when developing and debugging a process,especially when encounting problems.But in production systems,we don't want process to be debuggable,mainly for the following two reasons:
> (1)performance
> We want our process to run as fast as possible,so our system can handle more and more tasks
> (2)safety
> We can't bear a careless administartor to do any harm to the system,e.g. set Breakpoints and debug the process when the process is running.
> Can we configure this behavior by changing something in the deploy.xml file,just like 
> <in-memory>true</in-memory>
> or
> <active>true</active>

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (ODE-455) make ODE process DebuggerSupport configurable on per process basis

Posted by "Shammy Chen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/ODE-455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shammy Chen updated ODE-455:
----------------------------

    Description: 
DebuggerSupport is needed and preferred when developing and debugging a process,especially when encounting problems.But in production systems,we don't want process to be debuggable,mainly for the following two reasons:

(1)performance
We want our process to run as fast as possible,so our system can handle more and more tasks

(2)safety
We can't bear a careless administartor to do any harm to the system,e.g. set Breakpoints and debug the process when the process is running.

Can we configure this behavior by change something in the deploy.xml file,just like 
<in-memory>true</in-memory>
or
<active>true</active>


  was:
DebuggerSupport is needed and preferred when developing and debugging a process,especially when encounting problems.But in production systems,we don't want process to be debugable,mainly for the following two reasons:

(1)performance
We want our process to run as fast as possible,so our system can handle more and more tasks

(2)safety
We can't bear a careless administartor to do any harm to the system,e.g. set Breakpoints and debug the process when the process is running.

Can we configure this behavior by change something in the deploy.xml file,just like 
<in-memory>true</in-memory>
or
<active>true</active>



> make ODE process DebuggerSupport configurable on per process basis
> ------------------------------------------------------------------
>
>                 Key: ODE-455
>                 URL: https://issues.apache.org/jira/browse/ODE-455
>             Project: ODE
>          Issue Type: Improvement
>          Components: BPEL Runtime
>    Affects Versions: 1.2
>         Environment: Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03)
>            Reporter: Shammy Chen
>            Priority: Minor
>
> DebuggerSupport is needed and preferred when developing and debugging a process,especially when encounting problems.But in production systems,we don't want process to be debuggable,mainly for the following two reasons:
> (1)performance
> We want our process to run as fast as possible,so our system can handle more and more tasks
> (2)safety
> We can't bear a careless administartor to do any harm to the system,e.g. set Breakpoints and debug the process when the process is running.
> Can we configure this behavior by change something in the deploy.xml file,just like 
> <in-memory>true</in-memory>
> or
> <active>true</active>

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.