[Design of JBoss jBPM] - Task Forms
by david.lloyd@jboss.com
Currently, the JSF Task Forms have a lot of requirements about the circumstances of their execution. For example, they assume that they are loaded from the /jbpm-console/participant/ path, so all their references are relative to there.
They also assume the existance of "taskBean", the presence of certain images in the "../images" path, and the presense of "../css/jbpm.css". And finally, they rely on structural details of the taskBean, such as action methods.
I propose that rather than having this information in the form (and thus putting significant restrictions on how the forms are displayed and used), each of those constructs could be replaced by a combination of a set of XML elements that perform each function, and using EL to import significant variables right into the task form space; for example, assuming an "tf" prefix for "task form":
<img src="../images/formline.jpg" width="100%" height="24" border="0" alt=""/>
Becomes:
<tf:formline/>
And:
<input jsfc="h:inputText" value="#{taskInstanceBean.variables['paymentId']}" />
Becomes:
<input jsfc="h:inputText" value="#{paymentId}"/>
And finally:
<input type="submit" jsfc="h:commandButton" id="transitionButton" action="#{taskInstanceBean.saveAndClose}" value="Save and Close Task"/>
| <input type="submit" jsfc="h:commandButton" action="#{taskInstanceBean.save}" value="Save"/>
| <input type="submit" jsfc="h:commandButton" action="#{taskInstanceBean.cancel}" value="Cancel"/>
Becomes:
<tf:transitionButtons/>...or can be left out altogether.
Also, the task form need not include <h:form> tags, since this is really implicit; by providing this ourselves, we can add any hidden inputs we need to, and this frees the form designer from worring about the implementation details of the web application that utilizes the forms.
Opinions?
Also, one other unrelated problem is that some of the example task forms have multiple elements with the same ID, which is not allowed by either JSF or HTML.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3983792#3983792
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3983792
19 years, 5 months
[Design of JBoss jBPM] - Re: libraries in an .ear file
by andyredhead
Just had a look at the JEE 5 spec (JSR 244), section EE.8.1.2Application Assembly talks about how to put together .ear files and section EE.8.2Library Support goes on to describe how to include libraries.
Option 2 in section 8.1.2:
anonymous wrote : A .ear file may contain a directory that contains libraries packaged in JAR files. The library-directory element of the .ear file?s deployment descriptor contains the name of this directory. If a library-directory element isn?t specified,
| or if the .ear file does not contain a deployment descriptor, the directory named lib is used. An empty library-directory element may be used to specify
| that there is no library directory.
| All files in this directory (but not subdirectories) with a .jar extension must be made available to all components packaged in the EAR file, including application clients. These libraries may reference other libraries, either bundled
| with the application or installed separately, using any of the techniques described herein.
Which sounds like what you are trying to achieve?
That whole section is probably worth a read as it covers the whole ear assembly...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3983699#3983699
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3983699
19 years, 5 months
[Design of POJO Server] - Re: Are you considering an OSGi based micro kernel ?
by c.vidal
Hi Sacha,
Nice to meet you. Well actually, I would be very interested in implementing an OSGi deployer for JBoss on top of JBossMC.
OSGi is really getting a lot of momentum and will definitely be a serious actor in the near future, some other J2EE servers seem to already be migrating their core to OSGi or tightly integrating it (WAS 6.1, JOnAS amongst others) and JBoss would definitely benefit from a tight integration with OSGi.
Quickly as a first impression, the target functionalities I think would be great about that integration would be:
- possibility to plug in any OSGi container (Equinox, Oscar, Knopflerfish, ...)
- OSGi bundles would be automatically exposed as JMX Beans and/or JBossMC Beans
- OSGi bundles could transparently benefit from J2EE services: JTA, JMS, EJB3, JPA, ... and maybe why not even clustering of OSGi services
- OSGi bundles would be an alternative SAR deployment method
That's a first rough draft. Is this the kind of integration with OSGi that you expect ?
Regards
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3983696#3983696
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3983696
19 years, 5 months