"pete.muir(a)jboss.org" wrote : Can you tell me how you got the error if its simple?
I added my own app as an example to Seam example directory.
Basically I copied some previous example - structure, build.xml, ...
In order to build my own example I had to set this two properties to build.properties:
version=2.0
patchlevel=CR1
Otherwise it complained with some weird exception.
And the references to dependency libs are messed up:
- drools (they have no version so -* wont pick them up)
- richfaces (they have versions; just the opposite of drools)
The initial page of the app was successfully rendered, but the moment I logged in or did any other invocation that returned some value, the exception popped up.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4087310#4087310
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4087310
PROBLEM SOLVED :
Apparently jBPM cannot use a timer when the corresponding process definition has only been instantiated in memory from an XML definition but has not been persisted (at least in the Hibernate L1 cache if not in the DB).
When I add this call after instantiating the process definition, I don't get the Hibernate transient exception anymore :
jbpmContext.deployProcessDefinition(processDefinition);
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4087306#4087306
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4087306
Hi, I noticed that this was fixed in JBossWS 2.0.1.GA but then recently re-opened. I'm using JBossAS 4.2.1.GA and JBossWS 2.0.1.GA plus JBoss Seam 2.0.CR1 and RichRaces 3.1.1.SNAPSHOT, with exploded/unpacked EAR.
I'm still seeing some strange behavior here. Of course its possible I'm doing something wrong.
First time I run, everything is OK (I think). I have two web services defined and when I look at http://localhost:8080/jbossws/services I see 4 Registered Service Endpoints. For simplicity, I'll only describe one of the service definitiions.
| @WebService(name = "FlashServiceEndpointInterface", targetNamespace = "http://clooster.com/web/services/flash", serviceName = "FlashService")
| @SOAPBinding(style = SOAPBinding.Style.RPC)
| @Remote(EJB3RemoteFlashService.class)
| @RemoteBinding(jndiBinding = "/ejb3/EJB3FlashService")
| @Stateless
| @WebContext(transportGuarantee = "NONE", contextRoot = "/Clooster", urlPattern = "/common/services/FlashService")
| public class EJB3RemoteFlashServiceBean implements
| EJB3RemoteFlashService
| {
| ...
| }
|
First time I run I see endpoints as follows:
| http://MillGatewayFX:8080/Clooster/common/services/FlashService?wsdl
|
| AND
|
| http://MillGatewayFX:8080/CloosterRichWeb2-CloosterRichWeb2/EJB3RemoteFla...
|
|
This works and in my client code I access using the first one defined as it is in my EJB mentioned above.
However the second time I run I only see:
| http://MillGatewayFX:8080/CloosterRichWeb2-CloosterRichWeb2/EJB3RemoteFla...
|
and my client side code fails. So I'm back to square one and am forced to modify the run.bat to replace web.xml with web.xml.org for it to work correctly. Its not a major deal but for me I still consider it a bug.
Just giving you a heads up and thanks for all your hard work!
PVM
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4087300#4087300
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4087300