JBossDeveloper

Hi,

Encountered an issue already reported here with org.jboss.seam.jmx.jbossClusterMonitor.locateJBoss() returning null.
Stack trace identical to mentioned post.

Environment is JBoss EAP 4.2 clustered, deployed in farm. Had to revert to 2.1.0.SP1.

Regards

I was just testing Seam 2.1.1 on both JBoss 5 and 4.2.3 and the restart instead of explode happens only on JBoss 5.

Another problem I want to mention is with hot redeploying groovy components. On JBoss 5 everything works ok, since restart is executed even on explode, but on JBoss 4.2.3 explode does a real explode and any change to the Groovy component leads to a Two components with the same name and precedence after seam explode message which disappears after restart.

Cheers.

Hi,

Though I haven't downloaded the Seam 2.1.1.GA but Seam 2.1.1.CR2, I think they are almost the same.

I add the tomcat.home to the build.properties
I start the Tomcat 6.0.14
I deploy the example such as seamdiscs with command 'ant tomcat.deploy'

But I got a lot of exceptions.

Have the developer of Seam already tested it?

I just downloaded the Seam 2.1.1.GA. It seems there is little posibility to build the example project to run on Tomcat.

I am somewhat disappointed.

Nowadays many people use maven2 to build the project. I wonder why JBoss doesn't provide a pom.xml for the examples?

I am sure if JBoss make Seam mavenize, Seam will become more popular.

It's not only that you need a pom, but you need a good 'profile' to for each appserver. Otherwise people will complain that 'it does not run on Tomcat' or whatever..

Feel free to contribute...

Ronald van Kuijk wrote on Jan 23, 2009 11:11:


It's not only that you need a pom, but you need a good 'profile' to for each appserver. Otherwise people will complain that 'it does not run on Tomcat' or whatever..

Feel free to contribute...

If you can, that is not bad.

I wonder why there is target 'tomcat.undeploy' but no 'tomcat.deploy'?

If you haven't deploy the application to Tomcat, how to undeploy it?

Hi-
We've just upgraded to 2.1.1 GA on JBOSS 4.2 and periodically our app hangs in the middle of a remote call in IE 7 for no good reason. Works fine in FF 3. This is an app that is in production and running fine. Using HttpWatch in IE shows nothing - just a break in the process. No errors on the log - nothing. We are making multiple remote calls per page and specifying the cid specifically in each call. Our app is structured using xhtml pages.
Any help is greatly appreciated.
thanks!
Max Tomlinson

This was due to a bug in remote.js jar - in the 2.1.1 jboss-seam-remoting.jar

we commented out the  teh setTimeout code and now it works in IE

Max

Hi. We've migrated to 2.1.1.GA, fixed all errors and now application works, but very very slow. And it is reproducing for one user to, there are't errors in the log. I check many setting files and don't find solution. The simptoms is similar to described here.

Do you have any ideas?

i'd like to point to https://jira.jboss.org/jira/browse/JBSEAM-2915.

the upgrade broke our application.  in the mails we send out we need to have a link back to the application. the application is multi tenant (it has different host names). we need to know the host name the user is using to build urls (email confirmation for example) to the correct host.

the contract was changed in the above change. Renderer should use it's own copy of JSF, based around a mock servlet context and mock requests

this should at least be configurable or an alternative should be proposed !!!!
it's a pretty fundamental change of contract !!!

thanx for your feedback

JBoss and the Seam QC team (if one exists?) need to really focus on improving QC.  Functionality breaking in prod after an upgrade (and resorting to modifying distro jars like the jboss-seam-remoting.jar is poor.  I wonder if they even test with IE7 (that is our corporate standard here at Cox).

Is it mandatory to use new CacheProvider from Seam in order to use jboss cache ?

Upgrading from seam 2.0.0CR2 to 2.1.1GA would appear to have broken previous jboss configuration , which started jboss cache by have treecache.xml in root of ear

Since seam upgrade JBoss cache not starting. Can see it missing from jmx console

Hi,

I have a weird issue with 2.1.1 GA (actually, this issue was in CR2 too), but I've already created a new topic about it: My Link
Could You check it?

Thanks,
Tamas