суббота, 6 августа 2011 г.

Alfresco: strong text search with wildcard using lucene

My new problem is not very difficult, but have interesting solution (I think :)). For example we have four objects in our alfresco repository that have next titles:
  • James John
  • Li Joan
  • Johan Jazz
  • Bill

For get all objects that begins from 'Joh', I use the next query:
+TYPE:"my:object" +@cm\:title:"joh*"

The result of the query:
  • James John
  • Johan Jazz
  • Li Joan

'Joan' doesn't contain 'joh' in title. For solve that I modify my query:
+TYPE:"my:object" +@cm\:title:"[joh*]"

This query returns the right result:
  • James John
  • Johan Jazz

You can find more lucene tricks in wonderful book that called: "Lucene in Action" :)

вторник, 2 августа 2011 г.

Quartz: running jobs sequentially

To initialize (import dictionaries, create system users and roles, etc) our system we use quartz. But yesterday after I've created new job I saw that my new job depends on other jobs. Still I don't get how can I create dependencies over jobs and I think that the usage of dependencies in jobs is an ugly solution. The solution is simply to run jobs sequentially - one by one. But I couldn't find fast way to do that. One job runs in one thread and if I set threads count to 1, then I solve my problem. Here is the code to do that:

Properties schedProps = new Properties();
schedProps.setProperty(StdSchedulerFactory.PROP_THREAD_POOL_CLASS, SimpleThreadPool.class.getName());
schedProps.setProperty(StdSchedulerFactory.PROP_THREAD_POOL_PREFIX + ".threadCount", "1");
StdSchedulerFactory factory = new StdSchedulerFactory(schedProps);
Scheduler initScheduler = factory.getScheduler();
Now all jobs in initScheduler will run one by one.
It's simple and actually work :)

вторник, 28 июня 2011 г.

Generate changelog from Bamboo with Mercurial

Hi!

We use bamboo(v.3) for supports continuum integration in our project and mercurial as control version system. We wrote some core functions for the project and now should test it. Testers want to see what's new we do in new build. For this reason developers should wrote changelog for new build. But we are lazy developers and don't want to do this :) Unfortunately, bamboo can not generate changelog for mercurial. For make this, I added new stage to bamboo and create one script task in it.

Bamboo has list of global variables that you can use in scripts. Full list of these variables you can see here. I interested two of these variables:
bamboo.repository.revision.number - The revision number
repository.previous.revision.number - The previous revision number (might not exist if for example is initial build)
Now, I simple need to get changes between these revisions. Mercurial has powerful command:
hg log. It supports different templates. I use next command to get log:
hg log -r ${bamboo.repository.previous.revision.number}:${bamboo.repository.revision.number} --template "{rev}:{author} - {desc}\n" -P ${bamboo.repository.previous.revision.number}
I use flag -P to exclude revision from previous build.

Our build server works under Windows Server 2008 and I wrote batch in script task to generate changelog.

IF EXIST C:\changelog.txt (
  COPY C:\changelog.txt C:\changelog.txt.tmp
)

ECHO Build ${bamboo.buildNumber} - ${bamboo.buildTimeStamp} > C:\changelog.txt

IF ${bamboo.repository.previous.revision.number}==${bamboo.repository.revision.number} (
   echo [No changes] >> C:\changelog.txt
) ELSE ( 
   hg log -r ${bamboo.repository.previous.revision.number}:${bamboo.repository.revision.number} --template "{rev}:{author} - {desc}\n" -P ${bamboo.repository.previous.revision.number} >> C:\changelog.txt
)

ECHO ++++++++++++++++++++++++++ >> C:\changelog.txt
ECHO. >> C:\changelog.txt

IF EXIST C:\changelog.txt.tmp (
  TYPE C:\changelog.txt.tmp >> C:\changelog.txt
  DEL C:\changelog.txt.tmp
)

пятница, 29 апреля 2011 г.

Process workflow with alfresco and actitviti

Alfresco release new version of their ECM - 3.4.e. Major feature of this release is integration with activiti BPM platform. That's a good news, because JBPM 3 is obsolete. Of course, I try to use it and have some problems ;) In our projects we use WorkflowService to control business processes. To move workflow from one task to another we have to end current task and specify the transition name(more details you can find here:
    workflowService.endTask(task.getId(), "transitionName");

But when we migrate simple workflow from jbpm to activiti, we got exception :(

I start to discover alfresco sources and found interesting method in activiti workflow component:
    private WorkflowTask endNormalTask(String taskId, String localTaskId, String transition)
    {
        // Retrieve task
        Task task = taskService.createTaskQuery().taskId(localTaskId).singleResult();
        
        if(task == null)
        {
            String msg = messageService.getMessage(ERR_END_UNEXISTING_TASK, taskId);
            throw new WorkflowException(msg);
        }
        
        // Signal the transition on the task
        if (transition != null && 
                ActivitiConstants.DEFAULT_TRANSITION_NAME.equals(transition)==false)
        {
            // Only 'Next' is supported as transition.
            String msg = messageService.getMessage(ERR_END_TASK_INVALID_TRANSITION, transition, taskId, ActivitiConstants.DEFAULT_TRANSITION_NAME);
            throw new WorkflowException(msg);
        }
        setOutcome(task);
        taskService.complete(localTaskId);
        // The task should have a historicTaskInstance
        HistoricTaskInstance historicTask = historyService.createHistoricTaskInstanceQuery().taskId(task.getId()).singleResult();
        return typeConverter.convert(historicTask);
    }

YOOHOO! Now, you can use only "Next" keyword to move activiti workflow and code to end task should looks like this:
     workflowService.endTask(task.getId(),ActivitiConstants.DEFAULT_TRANSITION_NAME);

Most popular

Authors