[JBoss Portal] - problem when deploying IPC portlet
by matt4400
Hello,
I'm working with JBoss Portal 2.6CR2 and I'm developping IPC portlet. When I deploy the .sar file in JBoss I have this exception :
java.lang.ClassNotFoundException: No ClassLoaders found for: com.wyniwyg.core.blog.portlet.ResourceListePortlet$Listener
| ...
| --- MBeans waiting for other MBeans ---
| ObjectName: portal:service=ListenerService,type=blog_listener
| State: FAILED
| Reason: java.lang.ClassNotFoundException: No ClassLoaders found for: com.wyniwyg.core.blog.portlet.ResourceListePortlet$Listener
| I Depend On:
| portal:service=ListenerRegistry
|
| --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
| ObjectName: portal:service=ListenerService,type=blog_listener
| State: FAILED
| Reason: java.lang.ClassNotFoundException: No ClassLoaders found for: com.wyniwyg.core.blog.portlet.ResourceListePortlet$Listener
| I Depend On:
| portal:service=ListenerRegistry
|
The jboss-service.xml
| <mbean
| code="org.jboss.portal.core.event.PortalEventListenerServiceImpl"
| name="portal:service=ListenerService,type=blog_listener"
| xmbean-dd=""
| xmbean-code="org.jboss.portal.jems.as.system.JBossServiceModelMBean">
| <xmbean/>
| <depends
| optional-attribute-name="Registry"
| proxy-type="attribute">portal:service=ListenerRegistry</depends>
| <attribute name="RegistryId">blog_listener</attribute>
| <attribute name="ListenerClassName">com.wyniwyg.core.blog.portlet.ResourceListePortlet$Listener</attribute>
| </mbean>
|
The default-object.xml
| <deployments>
| <deployment>
| <if-exists>overwrite</if-exists>
| <parent-ref>default</parent-ref>
| <page>
| <page-name>Blog</page-name>
| <listener>blog_listener</listener>
| <properties/>
| <window>
| <window-name>BlogPortlet</window-name>
| <instance-ref>BlogPortletInstance</instance-ref>
| <region>center</region>
| <height>0</height>
| </window>
| <window>
| <window-name>AddResourcePortlet</window-name>
| <instance-ref>AddResourceInstance</instance-ref>
| <region>left</region>
| <height>0</height>
| </window>
| <window>
| <window-name>ResourceListePortlet</window-name>
| <instance-ref>ResourceListeInstance</instance-ref>
| <region>left</region>
| <height>1</height>
| </window>
| </page>
| </deployment>
| </deployments>
|
The portlet.xml
| <portlet>
| <description>Portlet to add resource</description>
| <portlet-name>AddResourcePortlet</portlet-name>
| <display-name>AddResource</display-name>
| <portlet-class>com.wyniwyg.core.blog.portlet.AddResourcePortlet</portlet-class>
| <expiration-cache>0</expiration-cache>
| <supports>
| <mime-type>text/html</mime-type>
| <portlet-mode>VIEW</portlet-mode>
| </supports>
| <portlet-info>
| <title>Add a resource</title>
| <short-title>Add a resource</short-title>
| </portlet-info>
| </portlet>
| <portlet>
| <description>Portlet to view resource</description>
| <portlet-name>ResourceListePortlet</portlet-name>
| <display-name>ResourceListe</display-name>
| <portlet-class>com.wyniwyg.core.blog.portlet.ResourceListePortlet</portlet-class>
| <expiration-cache>0</expiration-cache>
| <supports>
| <mime-type>text/html</mime-type>
| <portlet-mode>VIEW</portlet-mode>
| </supports>
| <portlet-info>
| <title>Resource of the article</title>
| <short-title>Resource of the article</short-title>
| </portlet-info>
| </portlet>
|
The portlet-instance.xml
| <deployment>
| <instance>
| <instance-id>AddResourceInstance</instance-id>
| <portlet-ref>AddResourcePortlet</portlet-ref>
| </instance>
| </deployment>
| <deployment>
| <instance>
| <instance-id>ResourceListeInstance</instance-id>
| <portlet-ref>ResourceListePortlet</portlet-ref>
| </instance>
| </deployment>
|
Thinks for help
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4057737#4057737
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4057737
18Â years, 10Â months
[JBoss Seam] - [2.0 beta1]Problem caused by regression between jdk 1.5 and
by enzhao
environment: Seam 2.0 beta1, JBoss 4.2, JDK 1.6 b06 on Windows XP. My project configuration all correctly updated using the Seam-gen came with 2.0 beta1.
Today when I ran test classes extending SeamTest, there was this exception:
DeploymentFilter -> java.lang.ClassNotFoundException: [Ljava.lang.String;
jboss.kernel:service=Kernel -> **ERROR**
at org.jboss.embedded.Bootstrap.checkIncomplete(Bootstrap.java:144)
at org.jboss.embedded.Bootstrap.bootstrapURL(Bootstrap.java:169)
at org.jboss.embedded.Bootstrap.bootstrap(Bootstrap.java:201)
at org.jboss.embedded.Bootstrap.bootstrap(Bootstrap.java:214)
at org.jboss.seam.mock.BaseSeamTest.startJbossEmbeddedIfNecessary(BaseSeamTest.java:919)
at org.jboss.seam.mock.BaseSeamTest.init(BaseSeamTest.java:856)
at org.jboss.seam.mock.SeamTest.init(SeamTest.java:42)
... Removed 22 stack frames
I have tried to compile all my own code at the source level 1.5, did not work. And then tried to build the Seam 2.0 beta 1 at source level 1.6. The build was successful but it did not solve the problem, either. Then I googled for this strange exception and got some useful information here:
https://glassfish.dev.java.net/issues/show_bug.cgi?id=714
Seems it is not a Seam problem but something lies in the jboss-embedded-all.jar. (Which is JBossAS 5.0 project I think). The fix should be easy according to the bug-report I linked above.
For now I would have to install a jdk 1.5. But I'll try to file a JIRA bug report for JBossAS 5.0.
I hope this info could be helpful to those who are developing on JBoss AS + Seam + JDK 1.6 stack.
Regards,
Ellen
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4057731#4057731
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4057731
18Â years, 10Â months
[JNDI/Naming/Network] - JNDI Look up in JBoss 4.0.5GA
by pmadhum
Hi,
I am migrating the application from Jboss 3.2.8 to Jboss4.0.5GA.
I can deploy the ear file successfully in Jboss4.0.5 and all beans deployed correctly. Global JNDI Names space looks like this. I can run the application in Jboss 3.2.8, but not in jboss 4.0.5 getting error,while looking up session bean.
----------------------------
javax.naming.NamingException: Could not dereference object [Root exception is javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out]]
----------------------------------------------
the lookup code is, below worked in jboss 3.2 but getting above error in jboss 4.0.5GA, Can you please help me with the problem.?
--------------------------
InitialContext ictx = new InitialContext();
ictx.lookup("java:comp/env/ejb/SessionMaterial")
-------------------------------------------
--------------------------
Global JNDI Namespace
+- MaterialLocal (proxy: $Proxy63 implements interface com.skandia.model.entity.material.MaterialLocalHome)
+- TopicConnectionFactory (class: org.jboss.naming.LinkRefPair)
+- jmx (class: org.jnp.interfaces.NamingContext)
| +- invoker (class: org.jnp.interfaces.NamingContext)
| | +- RMIAdaptor (proxy: $Proxy42 implements interface org.jboss.jmx.adaptor.rmi.RMIAdaptor,interface org.jboss.jmx.adaptor.rmi.RMIAdaptorExt)
| +- rmi (class: org.jnp.interfaces.NamingContext)
| | +- RMIAdaptor[link -> jmx/invoker/RMIAdaptor] (class: javax.naming.LinkRef)
+- ZugangLocal (proxy: $Proxy62 implements interface com.skandia.model.entity.zugang.ZugangLocalHome)
+- BestellungLocal (proxy: $Proxy65 implements interface com.skandia.model.entity.bestellung.BestellungLocalHome)
+- HTTPXAConnectionFactory (class: org.jboss.mq.SpyXAConnectionFactory)
+- ConnectionFactory (class: org.jboss.mq.SpyConnectionFactory)
+- MaterialversionLocal (proxy: $Proxy66 implements interface com.skandia.model.entity.materialversion.MaterialversionLocalHome)
+- UserTransactionSessionFactory (proxy: $Proxy12 implements interface org.jboss.tm.usertx.interfaces.UserTransactionSessionFactory)
+- HTTPConnectionFactory (class: org.jboss.mq.SpyConnectionFactory)
+- XAConnectionFactory (class: org.jboss.mq.SpyXAConnectionFactory)
+- UserTransaction (class: org.jboss.tm.usertx.client.ClientUserTransaction)
+- UILXAConnectionFactory[link -> XAConnectionFactory] (class: javax.naming.LinkRef)
+- UIL2XAConnectionFactory[link -> XAConnectionFactory] (class: javax.naming.LinkRef)
+- queue (class: org.jnp.interfaces.NamingContext)
| +- A (class: org.jboss.mq.SpyQueue)
| +- testQueue (class: org.jboss.mq.SpyQueue)
| +- ex (class: org.jboss.mq.SpyQueue)
| +- DLQ (class: org.jboss.mq.SpyQueue)
| +- D (class: org.jboss.mq.SpyQueue)
| +- C (class: org.jboss.mq.SpyQueue)
| +- B (class: org.jboss.mq.SpyQueue)
+- topic (class: org.jnp.interfaces.NamingContext)
| +- testDurableTopic (class: org.jboss.mq.SpyTopic)
| +- testTopic (class: org.jboss.mq.SpyTopic)
| +- securedTopic (class: org.jboss.mq.SpyTopic)
+- console (class: org.jnp.interfaces.NamingContext)
| +- PluginManager (proxy: $Proxy43 implements interface org.jboss.console.manager.PluginManagerMBean)
+- LagerbestandLocal (proxy: $Proxy64 implements interface com.skandia.model.entity.lagerbestand.LagerbestandLocalHome)
+- UIL2ConnectionFactory[link -> ConnectionFactory] (class: javax.naming.LinkRef)
+- HiLoKeyGeneratorFactory (class: org.jboss.ejb.plugins.keygenerator.hilo.HiLoKeyGeneratorFactory)
+- UILConnectionFactory[link -> ConnectionFactory] (class: javax.naming.LinkRef)
+- ejb (class: org.jnp.interfaces.NamingContext)
| +- SessionMaterial (proxy: $Proxy76 implements interface com.skandia.model.session.material.SessionMaterialHome,interface javax.ejb.Handle)
| +- SessionCodes (proxy: $Proxy74 implements interface com.skandia.model.session.codes.SessionCodesHome,interface javax.ejb.Handle)
+- AbgangLocal (proxy: $Proxy67 implements interface com.skandia.model.entity.abgang.AbgangLocalHome)
+- QueueConnectionFactory (class: org.jboss.naming.LinkRefPair)
+- UUIDKeyGeneratorFactory (class: org.jboss.ejb.plugins.keygenerator.uuid.UUIDKeyGeneratorFactory)
------------------------------------------
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4057727#4057727
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4057727
18Â years, 10Â months
[JBoss Seam] - Error during navigation before response fully rendered - cri
by jeneric
We've got our application almost ready to go (seam 1.1.6, myfaces) but we need to address a critical error that occurs during page navigation. If a user accidentally clicks to navigate prior to a previous navigation's response being rendered - the system crashes and returns the user to the default - no conversation view-id.
Here is an example of the navigation flow...
| Step 1 Step 2
| click link OK click link Not OK
| Default ViewId --> ViewId2 --> ViewId3
| / \
| | Step 3
| | click link Not Ok
| | --> ViewId4
|
| While ViewId3 is being rendered
| (step2 is being processed) the
| user clicks another link to go
| to ViewId4. Neither ViewId is
| rendered correctly - the system
| redirects the user back to the
| default ViewId.
Is there a common approach to solving this scenario - basically we want to block the user from performing any navigation prior to the response getting fully rendered?
We were hoping to avoid having to put javascript on all the submit buttons/links for disabling the forms.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4057723#4057723
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4057723
18Â years, 10Â months