Wildfly cache won't let me deploy updated Code?

[goot]

Since yesterday I'm facing some heavy issues with Wildfly Beta 1.

I updated my Java EE Project and deployed it on my server. It looks like the Wildfly Cache won't update the code. It's the same thing with my EJB Project (But I can't really tell...I can't debug properly at the moment...).

This even happened after I installed a new instance of eclipse and created a new workspace.

I deleted the wildfly tmp folder  and removed all data from the deployments folder....like a thousand times. I restarte the computer, I cleared my browsers cache.

It became impossible for me to work with wildfly. How can I stop this caching?(implying, this is caused by caching...)

Goot

[jaikiran]

I am not sure what exactly is being cached, but take a look at this recent thread and see if it is related Wildfly caches resources in exploded content deployment mode

[goot]

This seems to be related.  I also deployed an EAR Project, containing my EJBs. Wildfly tells me that the handshake has been successful, but when I call some EJB funtions it won't return feedback to the frontend. Anyway I can't debug this issue.

[goot]

I followed the workaround of https://issues.jboss.org/browse/WFLY-2391

It didn't work. Eclipse still won't update my sourcecode, even after I reinstalled WildFly Beta1 again.

I removed all EJB-Lookups and replaced them with some methods in my Frontend.

Also I undeployed the EJB-Project, It is not deployed according to my Jboss Management Console.

When I call the replaced method, it will return some value which does not exiist in the current code.

Lets say My Method returned  "foo.jsp" and the new method returns "bar.jsp", it will still replace "foo.jsp", even if there is no clue of "foo.jsp" in my project. Also it looks like Wildfly successfully handshakes with my EJB-Project...which is not deployed...

[CODE]15:15:10,698 INFO  [org.jboss.ejb.client.remoting] (Remoting "config-based-ejb-client-endpoint" task-3) EJBCLIENT000017: Received server version 2 and marshalling strategies [river]

15:15:10,700 INFO  [org.jboss.ejb.client.remoting] (default task-30) EJBCLIENT000013: Successful version handshake completed for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@6aa64816, receiver=Remoting connection EJB receiver [connection=org.jboss.ejb.client.remoting.ConnectionPool$PooledConnection@5ff67da6,channel=jboss.ejb,nodename=goot_acer]} on channel Channel ID da4bf31a (outbound) of Remoting connection 1e673864 to /127.0.0.1:8080[/CODE]

whats going on here?