1 2 Previous Next 21 Replies Latest reply on Sep 29, 2006 9:16 AM by falazar

    3.2 alpha 1 release status

    tom.baeyens

      Hi,

      Just to let you know what we're up to:

      The new jpdl suite is building correctly and repeatable. Almost ready for release. The things left todo are release notes, some readme's and that kind of little things.

      3.2 alpha 1 is almost releasable. Code is good enough but with one exception: the new job scheduler still has problem with hibernate. So timers and asynchronous messages can not be executed yet. I'm currently thinking of marking this as a known issue and proceed with the release.

      Yesterday, Koen managed to get the forms generator embedded in the designer tool. Great JIT-work, Koen ! thanks.

      Hopefully i'll find time in the next few days to put the little last pieces of the puzzle in place.

        • 1. Re: 3.2 alpha 1 release status

          Sounds great!

          A couple things we have noticed in heavy work on the web console is that the task assigned to swimlanes or pooled users is not showing up in the web console (thought the db shows them correctly),
          and if a task is assigned to a group, say CSD, and someone takes that task and completes it, the actorid is not being saved in the db.

          James

          • 2. Re: 3.2 alpha 1 release status
            kukeltje

            afaik, this is on the list for being fixed in 3.2 and if the webapp can be made backwardscompatible with 3.1 it hopefully is fixed there to.

            • 3. Re: 3.2 alpha 1 release status
              aguizar

              JobExecutor and JobExecutorServlet invoke some Thread methods introduced in java 5. Is this on purpose?

              • 4. Re: 3.2 alpha 1 release status
                kukeltje

                isn't the retro library included for running this as well on 1.4?

                • 5. Re: 3.2 alpha 1 release status
                  tom.baeyens

                  aha. i wasn't aware that i used 1.5 methods. i'll fix that.

                  • 6. Re: 3.2 alpha 1 release status
                    tom.baeyens

                    strange. i just build the distro and the javac task has source="1.4" and target="1.4" and this doesn't seem to be giving a problem... i'll investigate futher

                    • 7. Re: 3.2 alpha 1 release status

                      Is that on the list TO BE fixed or on list of things that were fixed?

                      We finaly added another query that joined the taskinstance and pooledactors for tasks with a swimlane instance, but we couldnt find away to do it in the single query.

                      It is all working in our version of the web console now.

                      James

                      • 8. Re: 3.2 alpha 1 release status
                        tom.baeyens

                        aha

                        right.

                        i'll verify that there is no usage of 1.5 API's before i do the release.

                        • 9. Re: 3.2 alpha 1 release status

                          You should be able to see it easily if you set a task to a pooled-actor list directly,
                          as opposed to setting it to a swimlane that has pooled users in it.

                          The query will pick up the tasks that are defined with the pooled-actors
                          but not the other way.

                          It is doing a triple join across
                          taskinstance, taskactorpool, and pooledactor
                          and for swimlane pooled actors there is no entry made in the taskactorpool table.

                          It seems like a couple of these tables may not be normalized very well either.

                          James

                          • 10. Re: 3.2 alpha 1 release status
                            tom.baeyens

                            i verified and my IDE's source compliance level is set to 1.4. job executor stuff compiles without complaints.

                            so alex, can you be more precise on which java 5 methods you mean ?

                            • 11. Re: 3.2 alpha 1 release status
                              dmlloyd

                               

                              "tom.baeyens@jboss.com" wrote:
                              strange. i just build the distro and the javac task has source="1.4" and target="1.4" and this doesn't seem to be giving a problem... i'll investigate futher


                              Setting -source/-target 1.4 does not prevent usage of new 1.5 JDK features, just language constructs.

                              • 12. Re: 3.2 alpha 1 release status
                                dmlloyd

                                 

                                "david.lloyd@jboss.com" wrote:
                                "tom.baeyens@jboss.com" wrote:
                                strange. i just build the distro and the javac task has source="1.4" and target="1.4" and this doesn't seem to be giving a problem... i'll investigate futher


                                Setting -source/-target 1.4 does not prevent usage of new 1.5 JDK features, just language constructs.


                                ...which is to say, using -source 1.4 you couldn't use enums, generics, or annotations, but you can still use new classes/methods. There's nothing within the JDK classes that marks specific classes or methods as new for 1.5 such that the compiler would be able to detect it.

                                • 13. Re: 3.2 alpha 1 release status
                                  dmlloyd

                                   

                                  "falazar" wrote:
                                  A couple things we have noticed in heavy work on the web console is that the task assigned to swimlanes or pooled users is not showing up in the web console (thought the db shows them correctly),

                                  Are you referring to the results of TaskMgmtSesssion.findPooledTaskInstances()?

                                  "falazar" wrote:
                                  It seems like a couple of these tables may not be normalized very well either.

                                  I'm with you there, but from talking to Tom I don't think we can expect this to change in the 3.x series, since we're going to avoid any sweeping database changes, especially those that would introduce compatibility problems... Tom, correct me if I'm wrong.

                                  • 14. Re: 3.2 alpha 1 release status

                                    Yes I believe that was the function.

                                    We attempted to change it with no luck, but then finally just create another one which covers the rest caleld finSwimlanePooledTaskInstances()

                                    because if you just have pooled users in a swimlane with a task it will NOT currently show up in the web app.

                                    James

                                    1 2 Previous Next