[Design of JBoss jBPM] - Re: jBPM 4 Email Question
by bradsdavis
Here are my initial thoughts on properties for configuration.
To address point 1 of the 2 points in my previous post, we could have the mail servers have include-domains and exclude-domains depending on which domains they should handle. This way, multiple servers could be configured in, and the email service could determine the appropriate email handler.
| <jbpm-mail-service>
| <jbpm-mail-producers>
| <jbpm-mail-producer name="simple" class="org.jbpm.pvm.internal.email.SimpleMailProducer"/>
| </jbpm-mail-producers>
|
| <jbpm-mail-servers>
| <jbpm-mail-server name="internal">
| <smtp>
| <host></host>
| <port></port>
| <security>
| <authentication>
| <authType></authType>
| <user></user>
| <pass></pass>
| </authentication>
| <sslPort></sslPort>
| <tlsEnabled></tlsEnabled>
| </security>
| <socketFactory>
| <class></class>
| <fallback></fallback>
| <port></port>
| </socketFactory>
| </smtp>
| <include-domains>
| <domain>*</domain>
| </include-domains>
| </jbpm-mail-server>
| </jbpm-mail-servers>
|
| </jbpm-mail-service>
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223127#4223127
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223127
15 years, 1 month
[Design of JBoss jBPM] - Re: jBPM 4 Email Question
by bradsdavis
>From my experience in the field, here are two features we should actively pursue.
1) Multiple email servers. Reason: a lot of companies have multiple SMTP servers. The reason is, generally one sends internally and one externally. I think we could accomplish this by having a configuration for the email servers in the mail configuration. This would be a list of servers, which could take simple domain filtering. For example servers could include "*jboss.org" and that would indicate the mail server can serve all jboss.org emails. We could also support pop or smtp mail pretty easily.
2) Email Attachments are often an interest for clients. An example would be sending an order in PDF format when the task to sign off on the order is produced.
We could create an email producer interface that we could use to make email producers plugable. It could take the environment context as a parameter, and return an email object [see apache email commons]. That would make the interface flexible enough to return either a simple text email, HTML email, or Multipart email with attachments.
The email producer that we could ship could target using jsr223 or velocity or freemarker. I have noticed all of those have been tossed around as possible templating.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223089#4223089
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223089
15 years, 1 month
[Design of JBoss jBPM] - GSoC proposal: Process instance migration in JBPM
by tom.baeyens＠jboss.com
For this proposal, I think the following timeline is achievable:
Milestone 1 (approx 7 days): Get overview of the jBPM codebase and learn the build system.
Milestone 2 (approx 12 days): Work out the simplest possible example and discuss the proposed solution. Starting points: add a property to the deployment (probably as an attribute in the process definition). Add process instance migration code to the JpdlDeployer.
Milestone 3 (approx 7 days): Add a translation map in case activity names have changed. Define how this mapping information will be part of a deployment.
Milestone 4 (approx 15 days): Analyse exact constraints for migrating process instances over to a changed process definition. What kind of changes can be handled. And what kind of changes cannot be handled. Add those constraints to the process instance migration.
Milestone 5 (approx 15 days): Develop a testing strategy for process instance migrations.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4222989#4222989
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4222989
15 years, 1 month