[JBoss jBPM] - JBPM and MYSQL
by vanman733
HI,
I am really new to JBPM and am having some problems.
I am trying to get MYSQL to work with JBPM and I an running into some problems. I downloaded the 3.2 starter kit, installed MYSQL got the schema inserted but my problem is making the JBPM webapp use the MYSQL as the data source.
Following the user guide I cannot find the following:
Making the default webapp talk to the correct datasource is again not very difficult. The first step in doing this is simply locate the 'jboss-service.xml' file in the folder '${JBPM_SDK_HOME}/jbpm-server/server/jbpm/deploy/jbpm.sar/META-INF'.
There is no jbpm.sar, is this a separate download because it is not in the kit.
Because of this I cannot find the hibernate.cfg.xml file that is supposed to be in the directory.
Is there an updated doc for integrating MYSQL and JBPM?
Any Help would we great.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4092110#4092110
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4092110
18Â years, 6Â months
[JBoss Seam] - Re: [NamespaceScanner] Cannot load package
by alexeinov
I found out that the described effect occurs when JBoss is started with Sun's jdk1.5.0_12 JVM. Running it with JRockit 1.5 or with Sun's jdk1.6.0_2 does not lead to this problem.
Debugging of NameScanner have shown that the method getPackage() cannot obtain a package info.
| protected Package getPackage(String name)
| {
| try
| {
| Class c = classLoader.loadClass(name + ".package-info");
| return c != null ? c.getPackage() : null;
| }
| catch (Exception e)
| {
| return null;
| }
| }
|
The loadClass() method throw exceptions like this:
anonymous wrote : java.lang.ClassNotFoundException: org.jboss.seam.drools.package-info
As a result of this error no namespace-prefixed components are initialized in component.xml, after that lots of things go wrong. For instance, core:init component will be uninitialized, which makes that jndiPattern is not set, which in turn makes that no application components can be accessed in an EJB module.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4092106#4092106
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4092106
18Â years, 6Â months
[JBossWS] - Re: Unmarshalling Exception with Web Service Array Input
by sumitsu
I'd prefer to retain the 2.1 SLSB if I can... is there a reason that Array-type inputs should not work under JAX-RPC with the server/JBossWS config I described? Please let me know if you see anything obviously wrong with my WSDL/code/artifacts... I could not find many other references to this Exception in the forum.
If it helps, here is an extract from my mapping.xml file, also (currently) generated by wscompile:
| <?xml version="1.0" encoding="UTF-8" standalone="no" ?>
| <java-wsdl-mapping xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
| version="1.1" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://www.ibm.com/webservices/xsd/j2ee_jaxrpc_mapping_1_1.xsd">
| <package-mapping>
| <package-type>com.business.WebService.messageProcessing</package-type>
| <namespaceURI>InboundWebService</namespaceURI>
| </package-mapping>
| <package-mapping>
| <package-type>com.business.WebService.messageProcessing</package-type>
| <namespaceURI>InboundWebService</namespaceURI>
| </package-mapping>
| <java-xml-type-mapping>
| <java-type>com.business.WebService.dto.ServiceStatus</java-type>
| <root-type-qname xmlns:typeNS="InboundWebService">typeNS:ServiceStatus</root-type-qname>
| <qname-scope>complexType</qname-scope>
| <variable-mapping>
| <java-variable-name>code</java-variable-name>
| <xml-element-name>code</xml-element-name>
| </variable-mapping>
| <variable-mapping>
| <java-variable-name>subject</java-variable-name>
| <xml-element-name>subject</xml-element-name>
| </variable-mapping>
| </java-xml-type-mapping>
| <java-xml-type-mapping>
| <java-type>com.business.WebService.dto.CustomField</java-type>
| <root-type-qname xmlns:typeNS="InboundWebService">typeNS:CustomField</root-type-qname>
| <qname-scope>complexType</qname-scope>
| <variable-mapping>
| <java-variable-name>name</java-variable-name>
| <xml-element-name>name</xml-element-name>
| </variable-mapping>
| <variable-mapping>
| <java-variable-name>value</java-variable-name>
| <xml-element-name>value</xml-element-name>
| </variable-mapping>
| </java-xml-type-mapping>
| <java-xml-type-mapping>
| <java-type>com.business.WebService.dto.ServiceRequest</java-type>
| <root-type-qname xmlns:typeNS="InboundWebService">typeNS:ServiceRequest</root-type-qname>
| <qname-scope>complexType</qname-scope>
| <variable-mapping>
| <java-variable-name>customFields</java-variable-name>
| <xml-element-name>customFields</xml-element-name>
| </variable-mapping>
| </java-xml-type-mapping>
| <service-interface-mapping>
| <service-interface>com.business.WebService.messageProcessing.LiaisonB2BWebServiceInterface</service-interface>
| <wsdl-service-name xmlns:serviceNS="InboundWebService">serviceNS:LiaisonB2BWebServiceInterface</wsdl-service-name>
| <port-mapping>
| <port-name>MessageEndPointPort</port-name>
| <java-port-name>MessageEndPointPort</java-port-name>
| </port-mapping>
| </service-interface-mapping>
| <service-endpoint-interface-mapping>
| <service-endpoint-interface>com.business.WebService.messageProcessing.MessageEndPoint</service-endpoint-interface>
| <wsdl-port-type xmlns:portTypeNS="InboundWebService">portTypeNS:MessageEndPoint</wsdl-port-type>
| <wsdl-binding xmlns:bindingNS="InboundWebService">bindingNS:MessageEndPointBinding</wsdl-binding>
| <service-endpoint-method-mapping>
| <java-method-name>processMessage</java-method-name>
| <wsdl-operation>processMessage</wsdl-operation>
| <method-param-parts-mapping>
| <param-position>0</param-position>
| <param-type>com.business.WebService.dto.ServiceRequest</param-type>
| <wsdl-message-mapping>
| <wsdl-message xmlns:wsdlMsgNS="InboundWebService">wsdlMsgNS:MessageEndPoint_processMessage</wsdl-message>
| <wsdl-message-part-name>ServiceRequest</wsdl-message-part-name>
| <parameter-mode>IN</parameter-mode>
| </wsdl-message-mapping>
| </method-param-parts-mapping>
| <wsdl-return-value-mapping>
| <method-return-value>com.business.WebService.dto.ServiceStatus</method-return-value>
| <wsdl-message xmlns:wsdlMsgNS="InboundWebService">wsdlMsgNS:MessageEndPoint_processMessageResponse</wsdl-message>
| <wsdl-message-part-name>result</wsdl-message-part-name>
| </wsdl-return-value-mapping>
| </service-endpoint-method-mapping>
| </service-endpoint-interface-mapping>
| </java-wsdl-mapping>
|
Thanks again.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4092096#4092096
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4092096
18Â years, 6Â months