[Design of JBoss Portal] - migration from 2.6.0 to 2.6.2
by sviluppatorefico
while I migrate from 2.6.0 to 2.6.2 version of portal I see some differences to resolve for a correct migration:
all samples excluded basic samples are of 'samples' group into 2.6.0. Into 2.6.2 version they are called so:
- portal-jsp-samples for JSPPortlet
- portal-weather-samples for WeatherPortlet
- portal-news-samples for NewsPortlet
the tables that have theese differences are: JBP_PORTLET_STATE and JBP_INSTANCE.
To get a correct migration is important rename 'samples' groups for NewsPortlet, WeatherPortlet and JSPPortlet in 'portal-news-samples' , 'portal-weather-samples' and 'portal-jsp-samples' or change the contextRoot into jboss.xml files for theese three portlet. If you don't make this you cannot to see the initial pag of portal and then no other page you can to view.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109479#4109479
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4109479
17 years, 3 months
[Design of POJO Server] - Multiple deployments of the same mbean service
by anil.saldhana＠jboss.com
I remember seeing some discussion on the MBean registration aspect. But as it stands, the deploy/undeploy of an mbean service is still not working right as far as the registration is concerned.
You will see errors, such as:
vfsfile:/C:/cygwin/home/asaldhana/jboss-5.0/jboss-head/testsuite/output/resources/security-spi/rolemapping/rolemapping-test-service.xml -> java.lang.IllegalStateException: jboss.security.tests:service=DynamicLoginConfig is already installed.
|
|
| at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:696)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:642)
| at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:618)
| at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:607)
|
Is there an open JIRA issue on this?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109425#4109425
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4109425
17 years, 3 months
[Design of POJO Server] - A valid empty jboss.xml
by alesj
What should an empty jboss.xml look like, in order not to fail in the following way:
This is my empty jboss.xml:
| <?xml version="1.0"?>
| <jboss
| xmlns="http://www.jboss.com/xml/ns/javaee"
| xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
| xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee
| http://www.jboss.org/j2ee/schema/jboss_5_0.xsd"
| version="3.0">
| </jboss>
|
And the output:
| C:\Java\jdk1.5.0_11\bin\java -Didea.launcher.port=7532 -Didea.launcher.bin.path=C:\JetBrains\IDEA6.0\bin -Dfile.encoding=UTF-8 -classpath ... com.intellij.rt.execution.application.AppMain Test
| 19:34:04,484 ERROR [AbstractController] Error installing to Parse: name=vfsfile:/C:/projects/seam/examples/booking/resources/META-INF/jboss.xml state=Not Installed mode=Manual requiredState=Parse
| org.jboss.deployers.spi.DeploymentException: The xml is not well formed!
| at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:134)
| at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:86)
| at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:223)
| at org.jboss.deployment.JBossEjbParsingDeployer.createMetaData(JBossEjbParsingDeployer.java:104)
| at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:199)
| at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:162)
| at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:853)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:794)
| at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327)
| at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309)
| at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784)
| at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622)
| at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:498)
| at org.jboss.deployers.plugins.main.MainDeployerImpl.deploy(MainDeployerImpl.java:386)
| at Test.main(Test.java:62)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at com.intellij.rt.execution.application.AppMain.main(AppMain.java:90)
| org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
|
| *** DEPLOYMENTS MISSING DEPLOYERS: Name
|
| vfsfile:/C:/projects/seam/examples/booking/resources/META-INF/jboss.xml
|
| *** DEPLOYMENTS IN ERROR: Name -> Error
|
| vfsfile:/C:/projects/seam/examples/booking/resources/META-INF/jboss.xml -> org.jboss.deployers.spi.DeploymentException: The xml is not well formed!
|
|
| *** CONTEXTS IN ERROR: Name -> Error
|
| vfsfile:/C:/projects/seam/examples/booking/resources/META-INF/jboss.xml -> org.jboss.deployers.spi.DeploymentException: The xml is not well formed!
|
|
| at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:696)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:642)
| at org.jboss.deployers.plugins.main.MainDeployerImpl.deploy(MainDeployerImpl.java:399)
| at Test.main(Test.java:62)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at com.intellij.rt.execution.application.AppMain.main(AppMain.java:90)
|
| Process finished with exit code 0
|
My test:
| import java.io.File;
| import java.util.Collections;
|
| import org.jboss.dependency.plugins.AbstractController;
| import org.jboss.deployers.client.spi.Deployment;
| import org.jboss.deployers.plugins.deployers.DeployersImpl;
| import org.jboss.deployers.plugins.main.MainDeployerImpl;
| import org.jboss.deployers.spi.deployer.Deployer;
| import org.jboss.deployers.spi.deployer.Deployers;
| import org.jboss.deployers.vfs.plugins.structure.VFSStructuralDeployersImpl;
| import org.jboss.deployers.vfs.plugins.structure.VFSStructureBuilder;
| import org.jboss.deployers.vfs.plugins.structure.file.FileStructure;
| import org.jboss.deployers.vfs.spi.client.VFSDeploymentFactory;
| import org.jboss.deployers.vfs.spi.structure.StructureDeployer;
| import org.jboss.deployment.JBossEjbParsingDeployer;
| import org.jboss.virtual.VFS;
| import org.jboss.virtual.VirtualFile;
|
| /**
| * @author alesj
| */
| public class Test
| {
| public static void main(String[] args)
| {
| try
| {
| VFSDeploymentFactory factory = VFSDeploymentFactory.getInstance();
| File file = new File("C:\\projects\\seam\\examples\\booking\\resources\\META-INF\\jboss.xml");
| VirtualFile vf = VFS.getRoot(file.toURL());
| Deployment deployment = factory.createVFSDeployment(vf);
| MainDeployerImpl main = new MainDeployerImpl();
| StructureDeployer fileDeployer = new FileStructure();
| VFSStructuralDeployersImpl structuralDeployers = new VFSStructuralDeployersImpl(Collections.singleton(fileDeployer));
| structuralDeployers.setStructureBuilder(new VFSStructureBuilder());
| main.setStructuralDeployers(structuralDeployers);
| JBossEjbParsingDeployer jbossParser = new JBossEjbParsingDeployer();
| jbossParser.setUseSchemaValidation(false);
| jbossParser.setUseValidation(false);
| Deployer deployer = jbossParser;
| Deployers deployers = new DeployersImpl(new AbstractController(), Collections.singleton(deployer));
| main.setDeployers(deployers);
| main.deploy(deployment);
| }
| catch (Exception e)
| {
| e.printStackTrace();
| }
| }
| }
|
Otherwise I get a NPE, since there is no JBossMetaData instance in the attachments for Ejb3Deployer.
| [testng] Caused by: java.lang.NullPointerException
| [testng] at org.jboss.ejb3.interceptor.InterceptorInfoRepository.initialise(InterceptorInfoRepository.java:101)
| [testng] at org.jboss.ejb3.Ejb3HandlerFactory$DDFactory.<init>(Ejb3HandlerFactory.java:48)
| [testng] at org.jboss.ejb3.Ejb3HandlerFactory.getInstance(Ejb3HandlerFactory.java:83)
| [testng] at org.jboss.ejb3.Ejb3Deployment.deploy(Ejb3Deployment.java:431)
| [testng] at org.jboss.ejb3.Ejb3Deployment.create(Ejb3Deployment.java:375)
| [testng] at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:145)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109424#4109424
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4109424
17 years, 3 months