[JBoss jBPM] - Diploma thesis jbpm
by asmo
Hi!
I am writing a diploma thesis ( i don't know, if this is the right term for the german word Diplomarbeit ), which deals with jbpm.
Therefor, i have some question and i would be very grateful, if anyone could answer them.
My challenge it to implement a workflow with jbpm.
I thought about two appendages:
1. run the workflow in the frontend. this means to create a web application and the jbpm actions call the backend functions over business delegates.
2. run the workflow in the backend. Therefor i would create a stateless session bean, that contains the jbpm code.
In the meantime i think, that the first approach is more common.
Could someone tell my something about the adavantages / disadvantages of these two approaches.
Is one of them gernerally wrong?
I would be very thankful for any information!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979041#3979041
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3979041
19 years, 8 months
[JBossWS] - ServiceLifecycle troubles
by Kimerinn
Hi. I have implemented JSR-109 POJO Endpoint. This endpoint implements ServiceLifecycle interface. But init() method is never invokes. What's wrong?
I am using JBoss 4.0.4. Here is a code:
=============
Endpoint interface:
public interface ClientInterface extends Remote
{
public boolean login(String login, String psw) throws RemoteException;
public void logout() throws RemoteException;
}
==============
Endpoint implementation:
public class ClientInterfaceImpl implements ClientInterface, ServiceLifecycle
{
private ServletEndpointContext context;
public void init(Object object) throws ServiceException
{
this.context = (ServletEndpointContext)context;
}
public void destroy()
{
}
public boolean login(String login, String psw)
{
...
}
public void logout()
{
...
}
}
===========
Web.xml:
<web-app>
<display-name>server8hWeb</display-name>
<servlet-name>ClientInterfaceWS</servlet-name>
<servlet-class>com.logiamobile.server8h.core.ClientInterfaceImpl</servlet-class>
<servlet-mapping>
<servlet-name>ClientInterfaceWS</servlet-name>
<url-pattern>/ClientInterface</url-pattern>
</servlet-mapping>
</web-app>
==============
webservices.xml:
<webservice-description>
<webservice-description-name>server8h</webservice-description-name>
<wsdl-file>WEB-INF/wsdl/server8h.wsdl</wsdl-file>
<jaxrpc-mapping-file>WEB-INF/jaxrpc-mapping.xml</jaxrpc-mapping-file>
<port-component>
<port-component-name>ClientInterfacePort</port-component-name>
<wsdl-port>impl:ClientInterfacePort</wsdl-port>
<service-endpoint-interface>com.logiamobile.server8h.core.ClientInterface</service-endpoint-interface>
<service-impl-bean>
<servlet-link>ClientInterfaceWS</servlet-link>
</service-impl-bean>
</port-component>
</webservice-description>
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979033#3979033
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3979033
19 years, 8 months
[JBoss Seam] - Re: Seam application with tree on left and editor for select
by christian.bauer＠jboss.com
This is how I get stuff into the tree:
| package adapters;
|
| import org.apache.myfaces.trinidad.model.ChildPropertyTreeModel;
| import org.apache.myfaces.trinidad.model.TreeModel;
|
| import java.util.Collection;
|
| /**
| * Wraps a nested tree of nodes into a Trinidad TreeModel.
| *
| * The primary purpose of this adapter is to check if a node has children,
| * or not. The wrapped TreeModel then results in correct rendering of the
| * tree, either as a container or a node icon.
| *
| * See faces-config.xml for a usage example.
| *
| * @author Christian Bauer
| */
| public class TreeModelAdapter {
|
| private Collection rootCollection;
| private String childCollectionPropertyName;
|
| public TreeModelAdapter() {}
|
| public TreeModel getTreeModel() {
| return new ContainerAwareChildPropertyTreeModel(rootCollection, childCollectionPropertyName);
| }
|
| public Collection getRootCollection() {
| return rootCollection;
| }
|
| public void setRootCollection(Collection rootCollection) {
| this.rootCollection = rootCollection;
| }
|
| public String getChildCollectionPropertyName() {
| return childCollectionPropertyName;
| }
|
| public void setChildCollectionPropertyName(String childCollectionPropertyName) {
| this.childCollectionPropertyName = childCollectionPropertyName;
| }
|
| /**
| * This inner class extends the built-in Trinidad TreeModel, which by default
| * treats every node as a container. Users have to click on a node to see
| * if there is something in the container, and the rendering is also wrong.
| * This might trigger loading of the children (the collection of children is
| * touched) if you have lazy loading. However, you now get correct rendering
| * of nodes and a regular node does no longer appear as a container.
| */
| class ContainerAwareChildPropertyTreeModel extends ChildPropertyTreeModel {
|
| public ContainerAwareChildPropertyTreeModel(Object object, String string) {
| super(object, string);
| }
|
| public ContainerAwareChildPropertyTreeModel() {
| super();
| }
|
| public boolean isContainer() {
| boolean hasChildren = false;
| // Hit the children collection of this container to
| // figure out if its really a container
| enterContainer();
| if (getRowCount() > 0) hasChildren = true;
| exitContainer();
|
| return hasChildren;
| }
| }
| }
|
| <faces-config>
|
| <!-- JSF backing beans that call Seam components, these
| backing beans provide an additional layer between
| business components managed by Seam and presentation-only
| beans. Common backing beans in a Seam application are
| model adapters (that convert from a java.util.Collection
| to a Trinidad TreeModel, for example).
| -->
| <managed-bean>
| <managed-bean-name>catalogCategoryAdapter</managed-bean-name>
| <managed-bean-class>adapters.TreeModelAdapter</managed-bean-class>
| <managed-bean-scope>request</managed-bean-scope>
| <managed-property>
| <property-name>rootCollection</property-name>
| <value>#{catalog.rootCategories}</value>
| </managed-property>
| <managed-property>
| <property-name>childCollectionPropertyName</property-name>
| <value>childCategories</value>
| </managed-property>
| </managed-bean>
| ...
|
I guess I should use a Seam component for this last bit, instead of a dumb JSF backing bean.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979032#3979032
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3979032
19 years, 8 months