[Microcontainer] - Re: lifecycle-configure not found as a child of {urn:jboss:b
by ataylor
With Trace on I do get the following
| @main 09:50:57,224 DEBUG [JBossEntityResolver] Cannot resolve [publicID=urn:jboss:aop-beans:1.0,systemID=null]
| @main 09:50:57,234 DEBUG [JBossEntityResolver] Cannot resolve [publicID=null,systemID=urn:jboss:aop-beans:1.0]
| @main 09:50:57,234 DEBUG [JBossEntityResolver] Cannot resolve [publicID=urn:jboss:aop-beans:1.0,systemID=null]
| @main 09:50:57,267 DEBUG [JBossEntityResolver] Cannot resolve [publicID=null,systemID=urn:jboss:aop-beans:1.0]
| @main 09:50:57,270 TRACE [JBMBootstrapServer] Exception during JBoss Kernel Bootstrap.
|
however i have the jboss-aop-mc-int.jar in my classpath, which is where the schema definition is!!!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4095940#4095940
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4095940
18Â years, 9Â months
[JBoss Seam] - pages.xml action method fired on ajax requests - must be wro
by gothmog
Hi,
I have just spent the whole day re-structuring my seam application to make use of the action method on a page element in pages.xml only to find to my dismay that the action method fires not only on redirects to the page (as it should) but also on ajax callbacks.
This should not be the case as the action method on the page should fire on the first time load of the page only, thus a perfect place to put initial model setup logic (or to ensure the model is setup so that pages.xml can redirect elsewhere if not, say by using an if-outcome etc), whilst all the ajax calls are technically working with the same page via postbacks (and hence don't need the setup logic).
What this means is that the setup logic that I put into action method gets called ALL the time effectively eliminating the work of my ajax postback to change the model in order to change the display. i.e. during the rendering phase the setup logic gets called again, changing the model back to the initial page load state (and un-doing the work the ajax call did in the first place).
My specific example is as follows
pages.xml fragment
| <page view-id="/pm_ncrv.xhtml" action="#{maintainComponent.setupRelationshipsView}" login-required="true">
| ...
| </page>
|
Now there is an ajax callback in the page as follows
| <a4j:outputPanel id="childAttributes">
| <s:div rendered="#{not attributeProps.show}">
| <a4j:commandLink
| action="#{maintainComponent.addNewChildComponent}"
| immediate="true" value="Add new child component"
| reRender="childAttributes"
| oncomplete="initFileUploads()"
| styleClass="button" />
| </s:div>
| <s:div rendered="#{attributeProps.show}">
| ...
| </s:div>
| </a4j:outputPanel>
|
Now the setup method setupRelationshipsView() called in the action parameter of pages.xml does the following so that the ajax panel childAttributes is not rendered when you first redirect to the page:
| public void setupRelationshipsView() {
| log.info("setupRelationshipsView()");
| component = null;
| attributeProps = new AttributeProperties();
| attributeProps.setLegendText("Child Component Attributes");
| attributeProps.setReadOnly(false);
| attributeProps.setShow(false);
| }
|
The ajax call addNewChildComponent() wants to show the child attributes panel inline so that a new child component can be added so it does this:
| public void addNewChildComponent() {
| log.info("addNewChildComponent():mainComponent=" + mainComponent);
| if (mainComponent == null) {
| facesMessages.add("Main component not in correct state. " +
| "Child component could not be added. Please check log for errors.");
| log.error("addNewChildComponent():mainComponent not " +
| "in correct state:mainComponent=" + mainComponent);
| }
| else {
| if (mainComponent.getChildComponents() == null) {
| mainComponent.setChildComponents(new ArrayList<ISISComponent>());
| }
| component = new ISISComponent();
| component.setParentComponent(mainComponent);
| imageHolder = component;
| attributeProps = new AttributeProperties();
| attributeProps.setLegendText("Add new child component attributes");
| attributeProps.setReadOnly(false);
| attributeProps.setShow(true);
| }
| }
|
In other words it sets the show flag on attributeProps so that the inline panel is displayed. BUT... from the logs I see that the pages.xml action method gets called after the ajax call which resets the model variable attributeProps so that the inline panel is never displayed.
| 21:38:43,044 INFO [MaintainComponentAction] addNewChildComponent():mainComponent=model.ISISComponent@780767
| 21:38:43,053 INFO [MaintainComponentAction] setupRelationshipsView()
|
How does one stop the pages.xml from firing on ajax callbacks? I would consider this a major architectual flaw if this could not be done!! HELP!
Thanks
Troy
Seam 2.0.0 BETA
RichFaces 3.1.0
Jboss 4.2.0.GA
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4095936#4095936
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4095936
18Â years, 9Â months
[JBoss Seam] - Re: Form-based authemtication
by shamoh
Out corporation has User Management (UM) application to manage users and roles for all company applications. There is no self-registration in single applications.
Out application platform is IBM WebSphere 6.1 (WAS). We have implementation of custom user registry (external JACC authorization provider), which negotiates container managed authentication/authorization.
Our applications transparently use FORM-based authentication and users are checked against UM.
This approach ensures the Subject of logged in user contains LTPA token in its private credentials. It means I can call EJB deployed in different WAS instance and this call is trusted.
So thera two + one reasons:
- all applications use same user registry
- LTPA token
+ form-based auth is "recommended" solution of out company
-lk
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4095932#4095932
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4095932
18Â years, 9Â months
[JBoss Seam] - problem with deploy
by oakchild
Hi all,
In seam-gen command ( 2.0.0 cr1 ), i setup a new project named myproject
if i answer these:
- [Enter the JDBC URL for your database]
jdbc:sqlserver://localhost:1433;DatabaseName=bookingtest
- [Are you working with tables that already exits in the database?] n
- [Do you want to drop and recreate the database tables and data in import.sql each time you deploy?] y
I then deployed with mssql (lib: jqljdbc.jar)
(this time database=bookingtest not exist)
--> start jboss 4.2.1 with fragment error:
14:44:45,765 ERROR [MainDeployer] Could not start deployment: file:/D:/jboss-4.2
| .1.GA/server/default/deploy/myproject.war/
| org.jboss.deployment.DeploymentException: URL file:/D:/jboss-4.2.1.GA/server/def
| ault/deploy/myproject.war/ deployment failed
| at org.jboss.web.tomcat.service.TomcatDeployer.performDeployInternal(Tom
| catDeployer.java:379)
| at org.jboss.web.tomcat.service.TomcatDeployer.performDeploy(TomcatDeplo
| yer.java:104)
| at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:375)
|
| at org.jboss.web.WebModule.startModule(WebModule.java:83)
| at org.jboss.web.WebModule.startService(WebModule.java:61)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanS
| upport.java:289)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMB
| eanSupport.java:245)
| at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
| sorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
| er.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
| java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl
| ler.java:978)
| at $Proxy0.start(Unknown Source)
| at org.jboss.system.ServiceController.start(ServiceController.java:417)
| at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
| sorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
| er.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
| java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy45.start(Unknown Source)
| at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:46
| 6)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
| java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
| sorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
| er.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
| or.java:133)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
| BeanOperationInterceptor.java:142)
| at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor
| .java:97)
| at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(Intercepto
| rServiceMBeanSupport.java:238)
| at org.jboss.ws.integration.jboss42.DeployerInterceptor.start(DeployerIn
| terceptor.java:93)
| at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.
| start(SubDeployerInterceptorSupport.java:188)
| at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterce
| ptor.java:95)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
| java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy46.start(Unknown Source)
| at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
| at sun.reflect.GeneratedMethodAccessor18.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
| sorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
| er.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
| or.java:133)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
| BeanOperationInterceptor.java:142)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
| java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy9.deploy(Unknown Source)
| at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymen
| tScanner.java:421)
| at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentS
| canner.java:634)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.
| doScan(AbstractDeploymentScanner.java:263)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(A
| bstractDeploymentScanner.java:336)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanS
| upport.java:289)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMB
| eanSupport.java:245)
| at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
| sorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
| er.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
| java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl
| ler.java:978)
| at $Proxy0.start(Unknown Source)
| at org.jboss.system.ServiceController.start(ServiceController.java:417)
| at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
| sorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
| er.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
| java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy4.start(Unknown Source)
| at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
| at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
| java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
| sorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
| er.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
| or.java:133)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
| BeanOperationInterceptor.java:142)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
| java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy5.deploy(Unknown Source)
| at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
| at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
| at org.jboss.Main.boot(Main.java:200)
| at org.jboss.Main$1.run(Main.java:508)
| at java.lang.Thread.run(Thread.java:595)
| 14:44:45,875 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
|
| --- Incompletely deployed packages ---
| org.jboss.deployment.DeploymentInfo@f92ad73 { url=file:/D:/jboss-4.2.1.GA/server
| /default/deploy/myproject.war/ }
| deployer: MBeanProxyExt[jboss.web:service=WebServer]
| status: Deployment FAILED reason: URL file:/D:/jboss-4.2.1.GA/server/default/d
| eploy/myproject.war/ deployment failed
| state: FAILED
| watch: file:/D:/jboss-4.2.1.GA/server/default/deploy/myproject.war/WEB-INF/web
| .xml
| altDD: null
| lastDeployed: 1192607070015
| lastModified: 1192606186984
| mbeans:
|
| --- MBeans waiting for other MBeans ---
| ObjectName: jboss.web.deployment:war=myproject.war,id=261270899
| State: FAILED
| Reason: org.jboss.deployment.DeploymentException: URL file:/D:/jboss-4.2.1.GA/
| server/default/deploy/myproject.war/ deployment failed
|
| --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
| ObjectName: jboss.web.deployment:war=myproject.war,id=261270899
| State: FAILED
| Reason: org.jboss.deployment.DeploymentException: URL file:/D:/jboss-4.2.1.GA/
| server/default/deploy/myproject.war/ deployment failed
Then i tried again with a database existed (bookingtest)
-->deploy --> OK
How to deploy a new project which generates database?
Thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4095928#4095928
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4095928
18Â years, 9Â months