2:56 p.m.
Integrate jpdl/ws tests in automated testrun
--------------------------------------------
Key: JBPM-1291
URL: http://jira.jboss.com/jira/browse/JBPM-1291
Project: JBoss jBPM
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Thomas Diesler
Fix For: jBPM jPDL 3.2.4
--
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
2:56 p.m.
New subject: [JBoss JIRA] Updated: (JBPM-1291) Integrate jpdl/ws tests in automated testrun
[ http://jira.jboss.com/jira/browse/JBPM-1291?page=all ]
Thomas Diesler updated JBPM-1291:
---------------------------------
Description:
Open issues, things that require clarification
----------------------------------------------
[Impl]
- How will jbpm be configured (jbpm.cfg.xml) ?
- Type safety of process variables that get passed as xs:any? Maybe typed header would be
better?
- Security: For WS Username token profile should be leveraged, on the other end the
Identiy management component?
[Concept]
- Signaling just proceed without any verification
- Leverge the JBossWS record management for history view
Integrate jpdl/ws tests in automated testrun
--------------------------------------------
Key: JBPM-1291
URL: http://jira.jboss.com/jira/browse/JBPM-1291
Project: JBoss jBPM
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Thomas Diesler
Fix For: jBPM jPDL 3.2.4
Open issues, things that require clarification
----------------------------------------------
[Impl]
- How will jbpm be configured (jbpm.cfg.xml) ?
- Type safety of process variables that get passed as xs:any? Maybe typed header would be
better?
- Security: For WS Username token profile should be leveraged, on the other end the
Identiy management component?
[Concept]
- Signaling just proceed without any verification
- Leverge the JBossWS record management for history view
--
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
3:08 p.m.
New subject: [JBoss JIRA] Commented: (JBPM-1291) Integrate jpdl/ws tests in automated testrun
[ http://jira.jboss.com/jira/browse/JBPM-1291?page=comments#action_12419042 ]
Tom Baeyens commented on JBPM-1291:
-----------------------------------
this module is not necessary. if it takes too much we can just rip it out and postpone ws
support till jPDL 4.
Integrate jpdl/ws tests in automated testrun
--------------------------------------------
Key: JBPM-1291
URL: http://jira.jboss.com/jira/browse/JBPM-1291
Project: JBoss jBPM
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Thomas Diesler
Fix For: jBPM jPDL 3.2.4
Open issues, things that require clarification
----------------------------------------------
[Impl]
- How will jbpm be configured (jbpm.cfg.xml) ?
- Type safety of process variables that get passed as xs:any? Maybe typed header would be
better?
- Security: For WS Username token profile should be leveraged, on the other end the
Identiy management component?
[Concept]
- Signaling just proceed without any verification
- Leverge the JBossWS record management for history view
--
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
10:14 p.m.
New subject: [JBoss JIRA] Assigned: (JBPM-1291) Integrate jpdl/ws tests in automated testrun
[ http://jira.jboss.com/jira/browse/JBPM-1291?page=all ]
Heiko Braun reassigned JBPM-1291:
---------------------------------
Assignee: Heiko Braun
Integrate jpdl/ws tests in automated testrun
--------------------------------------------
Key: JBPM-1291
URL: http://jira.jboss.com/jira/browse/JBPM-1291
Project: JBoss jBPM
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Thomas Diesler
Assigned To: Heiko Braun
Fix For: jBPM jPDL 3.2.4
Open issues, things that require clarification
----------------------------------------------
[Impl]
- How will jbpm be configured (jbpm.cfg.xml) ?
- Type safety of process variables that get passed as xs:any? Maybe typed header would be
better?
- Security: For WS Username token profile should be leveraged, on the other end the
Identiy management component?
[Concept]
- Signaling just proceed without any verification
- Leverge the JBossWS record management for history view
--
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
10:49 a.m.
New subject: [JBoss JIRA] Commented: (JBPM-1291) Integrate jpdl/ws tests in automated testrun
[ http://jira.jboss.com/jira/browse/JBPM-1291?page=comments#action_12419170 ]
Tom Baeyens commented on JBPM-1291:
-----------------------------------
it is a community extension to our core jBPM product. we should define a way how we deal
with such extensions. something like incubation maybe ?
Integrate jpdl/ws tests in automated testrun
--------------------------------------------
Key: JBPM-1291
URL: http://jira.jboss.com/jira/browse/JBPM-1291
Project: JBoss jBPM
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Thomas Diesler
Assigned To: Heiko Braun
Fix For: jBPM jPDL 3.2.4
Open issues, things that require clarification
----------------------------------------------
[Impl]
- How will jbpm be configured (jbpm.cfg.xml) ?
- Type safety of process variables that get passed as xs:any? Maybe typed header would be
better?
- Security: For WS Username token profile should be leveraged, on the other end the
Identiy management component?
[Concept]
- Signaling just proceed without any verification
- Leverge the JBossWS record management for history view
--
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
11:51 p.m.
New subject: [JBoss JIRA] Commented: (JBPM-1291) Integrate jpdl/ws tests in automated testrun
[ http://jira.jboss.com/jira/browse/JBPM-1291?page=comments#action_12419547 ]
Thomas Diesler commented on JBPM-1291:
--------------------------------------
There should be no code whatsoever entering the code base that is not covered by tests.
Code maybe experimental, still it needs to have test coverage that documents what it is
supposed to do.
Integrate jpdl/ws tests in automated testrun
--------------------------------------------
Key: JBPM-1291
URL: http://jira.jboss.com/jira/browse/JBPM-1291
Project: JBoss jBPM
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Thomas Diesler
Assigned To: Heiko Braun
Fix For: jPDL 3.2.4
Open issues, things that require clarification
----------------------------------------------
[Impl]
- How will jbpm be configured (jbpm.cfg.xml) ?
- Type safety of process variables that get passed as xs:any? Maybe typed header would be
better?
- Security: For WS Username token profile should be leveraged, on the other end the
Identiy management component?
[Concept]
- Signaling just proceed without any verification
- Leverge the JBossWS record management for history view
--
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
9:52 a.m.
New subject: [JBoss JIRA] Updated: (JBPM-1291) remove jpdl/ws
[ http://jira.jboss.com/jira/browse/JBPM-1291?page=all ]
Tom Baeyens updated JBPM-1291:
------------------------------
Summary: remove jpdl/ws (was: Integrate jpdl/ws tests in automated testrun)
Let's take it out and keep it in the fridge till we have time to seriously build it
out. I don't think we should be spending time on maintaining or enhancing this.
remove jpdl/ws
--------------
Key: JBPM-1291
URL: http://jira.jboss.com/jira/browse/JBPM-1291
Project: JBoss jBPM
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Thomas Diesler
Assigned To: Heiko Braun
Fix For: jPDL 3.2.4
Open issues, things that require clarification
----------------------------------------------
[Impl]
- How will jbpm be configured (jbpm.cfg.xml) ?
- Type safety of process variables that get passed as xs:any? Maybe typed header would be
better?
- Security: For WS Username token profile should be leveraged, on the other end the
Identiy management component?
[Concept]
- Signaling just proceed without any verification
- Leverge the JBossWS record management for history view
--
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
1:14 p.m.
New subject: [JBoss JIRA] Assigned: (JBPM-1291) remove jpdl/ws
[
https://jira.jboss.org/jira/browse/JBPM-1291?page=com.atlassian.jira.plug...
]
Thomas Diesler reassigned JBPM-1291:
------------------------------------
Assignee: Thomas Diesler (was: Heiko Braun)
remove jpdl/ws
--------------
Key: JBPM-1291
URL: https://jira.jboss.org/jira/browse/JBPM-1291
Project: JBoss jBPM
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: JBossBPM-3.3.0.CR1
Open issues, things that require clarification
----------------------------------------------
[Impl]
- How will jbpm be configured (jbpm.cfg.xml) ?
- Type safety of process variables that get passed as xs:any? Maybe typed header would be
better?
- Security: For WS Username token profile should be leveraged, on the other end the
Identiy management component?
[Concept]
- Signaling just proceed without any verification
- Leverge the JBossWS record management for history view
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:14 p.m.
New subject: [JBoss JIRA] Work started: (JBPM-1291) remove jpdl/ws
[
https://jira.jboss.org/jira/browse/JBPM-1291?page=com.atlassian.jira.plug...
]
Work on JBPM-1291 started by Thomas Diesler.
remove jpdl/ws
--------------
Key: JBPM-1291
URL: https://jira.jboss.org/jira/browse/JBPM-1291
Project: JBoss jBPM
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: JBossBPM-3.3.0.CR1
Open issues, things that require clarification
----------------------------------------------
[Impl]
- How will jbpm be configured (jbpm.cfg.xml) ?
- Type safety of process variables that get passed as xs:any? Maybe typed header would be
better?
- Security: For WS Username token profile should be leveraged, on the other end the
Identiy management component?
[Concept]
- Signaling just proceed without any verification
- Leverge the JBossWS record management for history view
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:45 p.m.
New subject: [JBoss JIRA] Resolved: (JBPM-1291) remove jpdl/ws
[
https://jira.jboss.org/jira/browse/JBPM-1291?page=com.atlassian.jira.plug...
]
Thomas Diesler resolved JBPM-1291.
----------------------------------
Resolution: Done
Done
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] ------------------------------------------------------------------------
[INFO] JBoss jBPM ............................................ SUCCESS [3.749s]
[INFO] JBoss jBPM - jPDL ..................................... SUCCESS [0.012s]
[INFO] JBoss jBPM - jPDL Core ................................ SUCCESS [58.095s]
[INFO] JBoss jBPM - jPDL Database ............................ SUCCESS [0.163s]
[INFO] JBoss jBPM - jPDL Identity ............................ SUCCESS [11.835s]
[INFO] JBoss jBPM - jPDL Examples ............................ SUCCESS [0.302s]
[INFO] JBoss jBPM - jPDL Simulation .......................... SUCCESS [0.745s]
[INFO] JBoss jBPM - jPDL Userguide ........................... SUCCESS [0.035s]
[INFO] JBoss jBPM - 4JSF ..................................... SUCCESS [13.146s]
[INFO] JBoss jBPM - Console .................................. SUCCESS [4.350s]
[INFO] JBoss jBPM - Enterprise ............................... SUCCESS [0.636s]
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
remove jpdl/ws
--------------
Key: JBPM-1291
URL: https://jira.jboss.org/jira/browse/JBPM-1291
Project: JBoss jBPM
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: JBossBPM-3.3.0.CR1
Open issues, things that require clarification
----------------------------------------------
[Impl]
- How will jbpm be configured (jbpm.cfg.xml) ?
- Type safety of process variables that get passed as xs:any? Maybe typed header would be
better?
- Security: For WS Username token profile should be leveraged, on the other end the
Identiy management component?
[Concept]
- Signaling just proceed without any verification
- Leverge the JBossWS record management for history view
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5786
days inactive
5847
days old
9 comments
3 participants
participants (3)
-
Heiko Braun (JIRA) -
Thomas Diesler (JIRA)
-
Tom Baeyens (JIRA)