Dear readers, recently I was working on EkoBuzz marketing plan and was budgeting for the marketing conferences and exhibitions we want to participate and promote EkoBuzz in the calendar year 2010. I started looking and realized that there is no place or website that provides us this information, so I spent couple of hours on the web and researched some of the best and most sought after events in the field of marketing.  To make it convenient and save time of other marketers, below is the list I created. Hope to see you soon.

Kellogg’s Marketing Conference, Chicago

AD Age Digital Conference, New York

The Power Of eMarketing, San Fransisco

Interactive Marketing For  Small Business,  Chicago

Mobile Marketing Forum, New York

Social Media Conference, Los Angeles

Affiliate Summit  East  2010, New York

DMA 2010, San Fransisco

Internet Marketing Conference, New york

ADTECH, New York

Lets grow this list together

Thanks for reading

Digital marketing, Mobile Advertising, Text/SMS marketing, digital direct marketing, mobile and email marketing Add new tag, mobile marketing association, mobile marketing campaigns

Probably due to my endless wanderings in jbpm 4.3, I’ve ran into what seems to be a limitation that I haven’t encountered in jbpm 3.2.

I’ve described it in detail in jboss forum and tried to give a few attempts to answer it.

However, I don’t like any of my answers there:

• Dropping a constrain on a table is outright wrong
• Fudging jbpm code won’t survive any updates
• Providing my own implementation would’ve been an elegant attempt except for the fact that it was wrong – PVM was persistent in its preferences and insisted on talking to ExecutionImpl directly ignoring my subclass

It did seem that the problem would’ve been eliminated by doing a few minor changes to the ExecutionImpl class: that would’ve avoided the db constrain problem and eliminated an additional update issued against the table.

So I ended up by bringing ExecutionImpl.java into my project and doing the following:

• in #initializeProcessInstance method, removed a call to composeIds()
• in #save(), added a cal to composeIds() before dbSession.save()

The downside to it is composeId() being called twice for createExecution(), but I’ll worry about this later.

EkoBuzz Labs