I noticed later that it also mucked around with my jboss/server/default/lib directory. I had to restore that as well. I had JBossWS-native 3.0.1 installed inside Jboss 4.2.2 and it removed libraries required for that to work. It would be ideal if this application did not install its own libraries into the server directory. That might be possible with the newer version of jboss and jbossws.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I took a look to uninstall task, and doesn't seem it delete all jboss deploy dir since it specify a single file.
I didn't investigate about what it does with lib dir sice JBOSSWS 3.0.1 isn't supported by current version, and I know it needs some improvement to supprt it (not only in install/uninstall)
We will take care about these points in next release, now we are working on a different approach separating core by UI (a blog post on www.javalinux.it soon) . We will put our mind on 3.0.1 later. I kepp this issue opened as a reminder.
Thanks
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: NO
I noticed later that it also mucked around with my jboss/server/default/lib directory. I had to restore that as well. I had JBossWS-native 3.0.1 installed inside Jboss 4.2.2 and it removed libraries required for that to work. It would be ideal if this application did not install its own libraries into the server directory. That might be possible with the newer version of jboss and jbossws.
Logged In: YES
user_id=23676
Originator: NO
I took a look to uninstall task, and doesn't seem it delete all jboss deploy dir since it specify a single file.
I didn't investigate about what it does with lib dir sice JBOSSWS 3.0.1 isn't supported by current version, and I know it needs some improvement to supprt it (not only in install/uninstall)
We will take care about these points in next release, now we are working on a different approach separating core by UI (a blog post on www.javalinux.it soon) . We will put our mind on 3.0.1 later. I kepp this issue opened as a reminder.
Thanks