[Design of JBoss jBPM] - Mail session configuration
by alex.guizar＠jboss.com
Here is the preeliminary format.
<mail-session>
| <mail-server>
| <address-filter>
| <include>.+(a)jbpm.org</include>
| <exclude>.+(a)jboss.com</exclude>
| </address-filter>
| <session-properties>
| <property name='mail.host' value='localhost' />
| <property name='mail.user' value='aguizar' />
| <property name='mail.from' value='noreply(a)jbpm.org' />
| </session-properties>
| </mail-server>
| </mail-session>
Some notes:
It is not particularly easy to make the address filter implementation pluggable, and the usefulness of a filter other than a pattern matcher is doubtful. So I have turned the AddressFilter interface into a concrete class, and absorbed the functionality of WildCardAddressFilter.
Element session-properties is parsed via PropertiesBinding, so properties can be read from an external file, resource or URL as well. The properties are used to create a javax.mail.Session
Multiple mail-server elements can be specified.
MailSessionWireTest was added to test correct parsing
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224187#4224187
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4224187
17 years
[Design of POJO Server] - Re: Integration of Clustered DeploymentRepository in
by bstansberry＠jboss.com
No comments, so I'm going to go with "A) Keep two versions of this profile.xml file in the source tree".
Looking at how these files end up in the various configs, it's a bit untidy so I'm going to clean up a bit. The following current content in the server module's src/etc/conf ends up creating the content in the conf dir of each config.
| |-- default
| | |-- bootstrap
| | | |-- aop.xml
| | | |-- bindings.xml
| | | |-- classloader.xml
| | | |-- deployers.xml
| | | |-- jmx.xml
| | | |-- logging.xml
| | | |-- profile.xml
| | | `-- vfs.xml
| | |-- bootstrap-minimal.xml
| | |-- bootstrap.xml
| | |-- java.policy
| | |-- jax-ws-catalog.xml
| | |-- jboss-log4j.xml
| | |-- jboss-minimal.xml
| | |-- jboss-service.xml
| | |-- jndi.properties
| | |-- login-config.xml
| | |-- props
| | | |-- jbossws-roles.properties
| | | |-- jbossws-users.properties
| | | |-- jmx-console-roles.properties
| | | `-- jmx-console-users.properties
| | |-- standardjboss.xml
| | |-- standardjbosscmp-jdbc.xml
| | `-- xmdesc
| | |-- AttributePersistenceService-xmbean.xml
| | |-- ClientUserTransaction-xmbean.xml
| | |-- JNDIView-xmbean.xml
| | |-- Log4jService-xmbean.xml
| | |-- NamingBean-xmbean.xml
| | `-- NamingService-xmbean.xml
| |-- standard
| | |-- ear-deployer-jboss-beans.xml
| | |-- jboss-service.xml
| | `-- jndi.properties
| `-- web
| |-- jboss-service.xml
| `-- jmx-invoker-service.xml
|
Without objection, I'm going to:
1) Rename "default" to "all". This drives the creation of the "all" config and is the foundation for "default", "web" and "standard".
2) Replace all/bootstrap/profile.xml with the clustered version.
3) Create a new default/bootstrap folder containing the non-clustered profile.xml.
4) Change the build/build.xml to use 3) in the "default" config, inherited by "web" and "standard".
5) Create a new "minimal" dir under conf.
6) Move bootstrap-minimal and jboss-minimal to it (and rename them), rather than leaving them grouped with "all".
7) Change build/build.xml to reflect 6) in the "minimal" config build.
Basically, make the organization of the files reflect the way build/build.xml consumes them.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224154#4224154
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4224154
17 years
[Design of JBoss jBPM] - HTML Formatted Emails
by bradsdavis
I am working on HTML emails. This would be for stylized emails within companies.
The first stab is: org.jbpm.pvm.internal.email.producer.impl.HtmlScriptMailProducer.java within the email_branch.
The class allows a user to populate the field "html", and will run through the HTML embedding images into the message as attachments, replacing URLs for the images with cid: references.
Also, this extends the Script Email Producer, which allows the subject, body, and now HTML to resolve fields using the ScriptManager from jBPM.
I would like to add template support for emails [both HTML and non-HTML emails]. I am currently looking at alternatives to the JBPM 3.x email template implementation. While the 3.x solution worked quite well for textual emails, I would like to package templates such that rich templates containing images and HTML could be available to JBPM.
Has anyone given any thought to how to package rich templates in JBPM yet?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224152#4224152
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4224152
17 years