Got it. The invalid token is undefined.
When subcribing to the topics, two tokens are returned. However, upon the first
poll the second one is being sent as undefined. Subsequent polls use both
tokens correctly. Looks like a typical uninitialized javascript variable
somewhere on the Seam part.
Done. JBSEAM-1229. I hope it's an easy fix.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4039808#4039808
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4039808
___
jboss-user
Ok, some progress.
I left the subscription registry in a single JAR file and removed the install
parameter (did not work wiht install==true or install=false). The
application deploys fine, seam remoting is working, but it is breaking when
trying to subscribe to JMS topic:
| 15:35:58,898
Ok, some progress.
I left the subscription registry in a single JAR file and removed the install
parameter (did not work wiht install==true or install=false). The
application deploys fine, seam remoting is working, but it is breaking when
trying to subscribe to JMS topic:
| 15:35:58,898
Anybody?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4038777#4038777
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4038777
___
jboss-user mailing list
jboss-user@lists.jboss.org
I'm going to test that, but I had no problem deploying multiple jars with that
components.xml included. It's only whan I have both jars and wars when problems
start to appear. The same setup was working fine with Seam 1.1 and the
documentation doesn't seem to indicate anything was changed with
Ok, here goes.
I tried as advised (using this in a single components.xml):
components
| component
class=org.jboss.seam.remoting.messaging.SubscriptionRegistry install=true
| property name=allowedTopicsclientNotificationTopic,
inventoryNotifications/property
|
Forgot about this. The first error is caused by:
| Caused by: java.lang.IllegalArgumentException: no such setter method:
org.jboss.seam.remoting.messaging.SubscriptionRegistry.install
| at org.jboss.seam.util.Reflections.getSetterMethod(Reflections.java:219)
| at
That didn't fix it.
Here goes:
EAR's jboss-app.xml:
jboss-app
| security-domain/security-domain
| loader-repository
| seam.jboss.org:loader=loader-emp
| /loader-repository
| /jboss-app
component.xml in each JAR's META-INF contains:
components
|
There are no class loades defined in any jboss-web.xml either.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4038439#4038439
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4038439
I'm trying to migrate an application from Seam 1.1 to 1.2.1GA. The problem is I
cannot make Seam Remoting to work. My app is packaged as an EAR with multiple
WARs and JARs inside (basically some portlets built on top of some
services/EJBs). I followed the Seam documentation and made the changes
Using:
JBoss 4.0.5 (JEMS Installer, EJB3 profile)
Portal 2.6.0.ALPHA1
MySQL
Fedora Core 6
Sun JDK 1.5.0_10
Problem:
java.lang.ClassCastException: org.jboss.portal.core.impl.model.portal.PortalImpl
|
12 matches
Mail list logo
