Hi, I think this is related to http://jira.jboss.com/jira/browse/JBPM-949 which we upgraded to 3.2.1 to get around. We changed our code to specify a business key when creating a new process instance. Now our 2nd and subsequent processes start OK, but the subprocesses that they might fork fail with the same problem. How do we set the business 'key' for a subprocess, as it is not inherited from the parent process? Currently we can run only one instance of a subprocess or this problem will bite us! We don't want to relax the constraint in the database...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4068778#4068778
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4068778
I really think you should try to just get the zip file containing the binary, unzip it, and run it. If your UNIX box does not have an unzip utility, you can always unzip on Windows and copy the whole directory tree to UNIX.
The primary reason some people even used the installer was to get EJB3 support. In 4.2, that support is built in. I suspect that most JBoss AS users simply download the zip file - before 4.0.3(?) that was the only method of installing JBoss AS.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4068777#4068777
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4068777
We have been trying to fix this problem for .Net clients. The java2wsdl generated file has the parameters as a element that references a complex type. Unfortunately the proxy classes .Net creates interprets this as a separate object that needs to be passed into the method. .Net seems to want the element tag to wrap the type definition. Otherwise it sticks in this extra object as the parameter. Is there a easy way to control the way java2wsdl creates the wsdl file? I have examples below of both formats.
java2wsdl format:
Desired .Net friendly format:
Our WebSphere servers are creating the ".Net Friendly" format but they are probably built on an earlier version of axis.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4068768#4068768
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4068768
You are getting an "Access Denied" message from the CMS Service and not from the Portlet Container which manages the CMSAdminPortletInstance.
The CMSAdminPortletInstance is getting rendered, which is what is expected, but the CMS Service does not have proper permissions set for the role in question to access CMS content.
The Portal only goes as far as protecting the window, but the content inside the window is outside its control and security is managed by the actual application producing the content inside this window. In this case its the CMS Service and proper permissions need to be set on it via the CMS Admin Security console
Thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4068766#4068766
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4068766