February 2007 - jboss-dev-forums - Jboss List Archives

[Design of JBoss Wiki] - Installing Wiki Error. wikiService

by indyJones

JRE - 1.5 JBoss AS - 4.0.5 GA JBoss Portal - 2.4.1 EJB - 3.0 RC 8 Trying to install JBoss Wiki... I get the following error.. | | 11:11:50,031 INFO [TomcatDeployer] deploy, ctxPath=/wiki, warUrl=.../deploy/wiki.ear/wiki.war/ | 11:11:50,153 ERROR [WikiFileAccessFilter] Couldn't find WikiManagement | org.jboss.wiki.exceptions.WikiManagementNotFoundException: java.lang.RuntimeException: Error creating MBeanProxy: wiki:service=wikiService | at org.jboss.wiki.WikiCommon.getWikiManagement(WikiCommon.java:72) | | ...and... | | 11:11:51,384 INFO [WikiEngine] Loaded wikiPageDictionary: org.jboss.wiki.FileWikiPageDictionary@1289697 | 11:11:51,385 INFO [WikiEngine] Loaded credentialsClass: class org.jboss.wiki.JBossPortalCredentials | 11:11:51,394 INFO [PortletAppDeployment] These instances have been found in -object.xml, you should put them in the file /home/jboss/JBoss Portal 2.4 - YourEncore/jboss-4.0.5.GA/server/default/./deploy/wiki.ear/wiki.war/WEB-INF/portlet-instances.xml | 11:11:51,394 INFO [PortletAppDeployment] <?xml version="1.0" encoding="utf-8" standalone="yes"?> | <deployments> | <deployment> | <instance> | <instance-id>WikiPortletInstance</instance-id> | <portlet-ref>WikiPortlet</portlet-ref> | </instance> | </deployment> | </deployments> | | 11:11:52,052 INFO [EARDeployer] Started J2EE application: file:/home/jboss/JBoss Portal 2.4 - YourEncore/jboss-4.0.5.GA/server/default/deploy/wiki.ear/ | 11:11:52,054 ERROR [URLDeploymentScanner] Incomplete Deployment listing: | | --- Packages waiting for a deployer --- | org.jboss.deployment.DeploymentInfo@7caa2d { url=file:/home/jboss/JBoss Portal 2.4 - YourEncore/jboss-4.0.5.GA/server/default/deploy/wiki.ear/wiki.ejb3 } | deployer: null | status: Starting | state: START_SUBDEPLOYMENTS | watch: file:/home/jboss/JBoss Portal 2.4 - YourEncore/jboss-4.0.5.GA/server/default/deploy/wiki.ear/wiki.ejb3 | altDD: null | lastDeployed: 1171296709722 | lastModified: 1171296709000 | mbeans: | Any ideas? Thanks Indy View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4015155#4015155 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4015155

19 years, 1 month

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Scoped beans deployment

by alesj

"adrian(a)jboss.org" wrote : | Perhaps an even safer mechanism would be to leave the context | in the NOT_YET_INSTALLED state in the root kernel until the describe action | dependencies are satisifed. Then promote it to the scoped kernel | in the describe action? Sounds good, but quite un-natural. What about adding additional state after DESCRIBE --> SCOPE? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4015147#4015147 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4015147

19 years, 1 month

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Scoped beans deployment

by alesj

"adrian(a)jboss.org" wrote : | I'm thinking of the case where the class itself is annotated with the scope. | You cannot retrieve the annotation from the class until the classloading dependencies | are satisifed. Yup, you're right. Which Controller SPI to modify with Scoping - plain Controller or KernelController? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4015140#4015140 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4015140

19 years, 1 month

1
0
0 / 0

[Design of JBoss Transaction Services] - Transaction Timeout Simulation not working

by juser2007

Hi, As part of a debugging process, I am trying to enforce Transaction Time out. I am using Jboss-3.2.3 and have changed the following configurations. The beans are Container managed. jboss-service.xml - with "TransactionTimeout" attribute set to 45 sec. <mbean code="org.jboss.tm.TransactionManagerService" name="jboss:service=TransactionManager" xmbean-dd="resource:xmdesc/TransactionManagerService-xmbean.xml"> 45 <depends optional-attribute-name="XidFactory">jboss:service=XidFactory jboss.xml in META-INF - <ejb-name>TestSessionBean</ejb-name> <jndi-name>TestService/TestSession</jndi-name> <exception-on-rollback>true</exception-on-rollback> true <method-attributes> <method-name>testOverriddenTimeoutExpires</method-name> <transaction-timeout>5</transaction-timeout> <method-name>testOverriddenTimeoutDoesNotExpire</method-name> <transaction-timeout>5</transaction-timeout> </method-attributes> I have tried to trace the Transaction Log by appending in log4j.xml, but could not find any relevant information. I have added code to make sure that the processing would take more than a minute, but still haven't been able to simulate the transaction time out. Please let me know what else is needed to be done. Thanks for your help. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4015135#4015135 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4015135

19 years, 1 month

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Scoped beans deployment

by adrian＠jboss.org

"adrian(a)jboss.org" wrote : | But, you don't need classloading dependencies satisifed to create a scope | or a scoped kernel. Perhaps an even safer mechanism would be to leave the context in the NOT_YET_INSTALLED state in the root kernel until the describe action dependencies are satisifed. Then promote it to the scoped kernel in the describe action? I'm thinking of the case where the class itself is annotated with the scope. You cannot retrieve the annotation from the class until the classloading dependencies are satisifed. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4015113#4015113 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4015113

19 years, 1 month

1
0
0 / 0

[Design of EJB 3.0] - Re: VirtualFile abstraction

by thomas.diesler＠jboss.com

When this is done, we can change our jboss42 integration layer. jboss40 will probably still hava to use the abstraction View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4015106#4015106 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4015106

19 years, 1 month

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Scoped beans deployment

by adrian＠jboss.org

"alesj" wrote : "adrian(a)jboss.org" wrote : | | What about the things we already do in DescribeAction? Should be moved to this preparation stage as well? | | No, because most of what is done in the DecribeAction cannot be done | until dependencies are satisifed. Most importantly classloading dependencies | when that has been integrated. | | e.g. You don't want to ask AOP for the dependencies if the class is not deployed yet. | Nor do you want to try to retrieve the BeanInfo. | | But, you don't need classloading dependencies satisifed to create a scope | or a scoped kernel. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4015093#4015093 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4015093

19 years, 1 month

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Scoped beans deployment

by alesj

"adrian(a)jboss.org" wrote : | I think the solution is for the BeanMetaData to fully describe itself | and then have the install/uninstall into the root kernel do the work | from the description (again mostly delegating the KernelMetaDataRepository). | | The difference being that the install/uninstall just "does it" based | on what the BeanMetaData tells it, it doesn't make any policy decisions. What all should we describe (prepare) besides the Scopes (to create the ScopeKey) from annotations on BeanMetaData? What about the things we already do in DescribeAction? Should be moved to this preparation stage as well? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4015071#4015071 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4015071

19 years, 1 month

1
0
0 / 0

[Design of Clustering on JBoss (Clusters/JBoss)] - Re: JBoss cannot find Windows NLB Virtual IP

by somejunk

Hi, We are running into same problem...Could you tell me the procedure you followed to resolve it? Thanks... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4015070#4015070 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4015070

19 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Re: Relating configuration and monitoring

by adrian＠jboss.org

"scott.stark(a)jboss.org" wrote : Yes, but I"m not sure what else might need to be updated to support this yet. I believe the existing jmx notification based stuff should map over to an aspect that exposes a ManagedDeployment and its ManagedComponents as the jsr77 mbeans. I think we should really be doing this on the ManagedObjects? We already have a type, so once we have the notion of scope in the ManagedObjects it should be relatively trivial to map them to the jsr77 tree/naming convention? I think the only issue is whether we enforce that the POJOs/MBeans should implement the jsr77 classes, e.g. the statistics classes or whether we do some adaption in the jsr77 facade? I'd favour the latter simply because it allows the implementation to provide custom extra statistics and seperate the invocation/pooling/caching stats while still being able to map them to the standard classes for jsr77. The downside is that it is going to require some knowledge (hard wiring) of the real implementation in the jsr77 facade to make this work. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4015054#4015054 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4015054

19 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums February 2007