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

[Design of JCA on JBoss] - Re: JBAS-1437 RARMetaDataRepository

by scott.stark＠jboss.org

18 years, 10 months

1
0
0 / 0

[Design of POJO Server] - Re: Jboss build from the head starting with errors .

by vickyk

Here is the output when I start from jboss-5.0.0.Beta anonymous wrote : C:\svn\trunk\build\output\jboss-5.0.0.Beta\bin>run | =============================================================================== | | JBoss Bootstrap Environment | | JBOSS_HOME: C:\svn\trunk\build\output\jboss-5.0.0.Beta\bin\\.. | | JAVA: C:\jdk\jdk1.5.0_01\bin\java | | JAVA_OPTS: -Dprogram.name=run.bat -server -Xms128m -Xmx512m -Dsun.rmi.dgc.cli | ent.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 | | CLASSPATH: C:\jdk\jdk1.5.0_01\lib\tools.jar;C:\svn\trunk\build\output\jboss-5. | 0.0.Beta\bin\\run.jar | | =============================================================================== | | 00:19:18,140 INFO [ServerImpl] Starting JBoss (Microcontainer)... | 00:19:18,140 INFO [ServerImpl] Release ID: JBoss [Morpheus] 5.0.0.Beta (build: | CVSTag=HEAD date=200610012004) | 00:19:18,140 INFO [ServerImpl] Home Dir: C:\svn\trunk\build\output\jboss-5.0.0. | Beta | 00:19:18,140 INFO [ServerImpl] Home URL: file:/C:/svn/trunk/build/output/jboss- | 5.0.0.Beta/ | 00:19:18,140 INFO [ServerImpl] Library URL: file:/C:/svn/trunk/build/output/jbo | ss-5.0.0.Beta/lib/ | 00:19:18,140 INFO [ServerImpl] Patch URL: null | 00:19:18,140 INFO [ServerImpl] Server Name: default | 00:19:18,140 INFO [ServerImpl] Server Home Dir: C:\svn\trunk\build\output\jboss | -5.0.0.Beta\server\default | 00:19:18,140 INFO [ServerImpl] Server Home URL: file:/C:/svn/trunk/build/output | /jboss-5.0.0.Beta/server/default/ | 00:19:18,140 INFO [ServerImpl] Server Data Dir: C:\svn\trunk\build\output\jboss | -5.0.0.Beta\server\default\data | 00:19:18,140 INFO [ServerImpl] Server Temp Dir: C:\svn\trunk\build\output\jboss | -5.0.0.Beta\server\default\tmp | 00:19:18,140 INFO [ServerImpl] Server Config URL: file:/C:/svn/trunk/build/outp | ut/jboss-5.0.0.Beta/server/default/conf/ | 00:19:18,140 INFO [ServerImpl] Server Library URL: file:/C:/svn/trunk/build/out | put/jboss-5.0.0.Beta/server/default/lib/ | 00:19:18,140 INFO [ServerImpl] Root Deployment Filename: jboss-service.xml | 00:19:18,171 INFO [ServerImpl] Starting Microcontainer, bootstrapURL=file:/C:/s | vn/trunk/build/output/jboss-5.0.0.Beta/server/default/conf/deployer-beans.xml | 00:19:18,875 INFO [ProfileImpl] Using profile root:C:\svn\trunk\build\output\jb | oss-5.0.0.Beta\bin\file:\C:\svn\trunk\build\output\jboss-5.0.0.Beta\server\defau | lt\profile | 00:19:19,531 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0_01-b08 | ,Sun Microsystems Inc. | 00:19:19,546 INFO [ServerInfo] OS-System: Windows XP 5.1,x86 | 00:19:19,609 INFO [JMXKernel] Legacy JMX core initialized | 00:19:23,359 INFO [WebService] Using RMI server codebase: http://D6XT8G1S:8083/ | | 00:19:23,984 INFO [NamingService] JNDI bootstrap JNP=/0.0.0.0:1099, RMI=/0.0.0. | 0:1098, backlog=50, no client SocketFactory, Server SocketFactory=class org.jbos | s.net.sockets.DefaultSocketFactory | 00:19:25,000 INFO [SocketServerInvoker] Invoker started for locator: InvokerLoc | ator [socket://10.11.15.21:4446/?dataType=invocation&enableTcpNoDelay=true&marsh | aller=org.jboss.invocation.unified.marshall.InvocationMarshaller&socketTimeout=6 | 00000&unmarshaller=org.jboss.invocation.unified.marshall.InvocationUnMarshaller] | | 00:19:27,234 ERROR [BeanMetaDataDeployer] Error during deployment: jboss.remotin | g:handler=ejb3,name=DefaultEjb3Connector,type=Connector | org.jboss.deployers.spi.DeploymentException: Error deploying: java:comp/Initiali | zer | at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentExcept | ion(DeploymentException.java:49) | at org.jboss.deployers.plugins.deployers.kernel.BeanMetaDataDeployer.dep | loy(BeanMetaDataDeployer.java:71) | at org.jboss.deployers.plugins.deployers.kernel.BeanMetaDataDeployer.dep | loy(BeanMetaDataDeployer.java:42) | at org.jboss.deployers.plugins.deployers.helpers.AbstractSimpleRealDeplo | yer.deploy(AbstractSimpleRealDeployer.java:56) | at org.jboss.deployers.plugins.deployer.AbstractSimpleDeployer.commitDep | loy(AbstractSimpleDeployer.java:52) | at org.jboss.deployers.plugins.deployer.DeployerWrapper.commitDeploy(Dep | loyerWrapper.java:145) | at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy( | MainDeployerImpl.java:440) | at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy( | MainDeployerImpl.java:451) | at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy( | MainDeployerImpl.java:451) | at org.jboss.deployers.plugins.deployment.MainDeployerImpl.process(MainD | eployerImpl.java:381) | at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadPr | ofile(ProfileServiceBootstrap.java:359) | at org.jboss.system.server.profileservice.ProfileServiceBootstrap.bootst | rap(ProfileServiceBootstrap.java:246) | at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBoot | strap.java:89) | at org.jboss.system.server.profileservice.ServerImpl.doStart(ServerImpl. | java:401) | at org.jboss.system.server.profileservice.ServerImpl.start(ServerImpl.ja | va:340) | at org.jboss.Main.boot(Main.java:210) | at org.jboss.Main$1.run(Main.java:508) | at java.lang.Thread.run(Thread.java:595) | Caused by: java.lang.IllegalStateException: java:comp/Initializer is already ins | talled. | at org.jboss.dependency.plugins.AbstractController.install(AbstractContr | oller.java:249) | at org.jboss.dependency.plugins.AbstractController.install(AbstractContr | oller.java:177) | at org.jboss.deployers.plugins.deployers.kernel.BeanMetaDataDeployer.dep | loy(BeanMetaDataDeployer.java:67) | ... 16 more | 00:19:29,078 INFO [Embedded] Catalina naming disabled | 00:19:29,093 INFO [ClusterRuleSetFactory] Unable to find a cluster rule set in | the classpath. Will load the default rule set. | 00:19:29,093 INFO [ClusterRuleSetFactory] Unable to find a cluster rule set in | the classpath. Will load the default rule set. | 00:19:29,296 INFO [AprLifecycleListener] The Apache Tomcat Native library which | allows optimal performance in production environments was not found on the java | .library.path: C:\jdk\jdk1.5.0_01\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOW | S\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\JBossTrainingSession\labs\ant- | dist\bin;C:\Program Files\Microsoft Office\OFFICE11\Business Contact Manager\IM; | C:\Program Files\Microsoft SQL Server\80\Tools\Binn\;C:\Program Files\Microsoft | Office\OFFICE11\Business Contact Manager\;C:\Opensources\ANT\apache-ant-1.6.5\bi | n\;C:\Installed\CVS;C:\Installed\jvmstat\bat;C:\jdk\j2sdk1.4.2_09\bin;C:\Program | Files\MySQL\MySQL Server 4.1\bin;C:\Opensources\jwsdp-2.0\jwsdp-shared\bin;C:\P | rogram Files\OpenVPN\bin;C:\Program Files\CVSNT\ | 00:19:29,968 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-0.0.0.0 | -8080 | 00:19:29,968 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-0.0.0.0-8009 | | 00:19:29,984 INFO [Catalina] Initialization processed in 875 ms | 00:19:29,984 INFO [StandardService] Starting service jboss.web | 00:19:29,984 INFO [StandardEngine] Starting Servlet Engine: Apache Tomcat/2.0.0 | .dev | 00:19:30,015 INFO [StandardHost] XML validation disabled | 00:19:30,031 INFO [Catalina] Server startup in 47 ms | 00:19:30,703 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of | incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): | | *** DEPLOYMENTS IN ERROR: Name -> Error | | file:/C:/svn/trunk/build/output/jboss-5.0.0.Beta/server/default/deployers/ejb3.d | eployer/ -> java.lang.IllegalStateException: java:comp/Initializer is already in | stalled. | | | 00:19:30,734 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-808 | 0 | 00:19:30,750 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-0.0.0.0-8009 | 00:19:30,812 INFO [ServerImpl] JBoss (Microcontainer) [5.0.0.Beta (build: CVSTa | g=HEAD date=200610012004)] Started in 12s:672ms View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4022616#4022616 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4022616

18 years, 10 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Does the EJB deployer only deploy jars?

by bill.burke＠jboss.com

name your directory foo.jar View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4022613#4022613 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4022613

18 years, 10 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Closures, better aop support in jdk7?

by scott.stark＠jboss.org

I viewed the closure talk Jason sent out a link to: http://video.google.com/videoplay?docid=4051253555018153503&q=engEDU The www.javac.info has several links to closure related stuff, but its not responding this morning. Must be running on Neal's laptop. His blog (http://gafter.blogspot.com/) also contains related posts. Although he plays down the usefulness of a closure function pointer/type it would seem to be a natural typed representation of an aspect, and is something I wish we had to avoid going from a type explicit pointcut to the detyped interceptor callback. He talks about closure examples that are obvious advices, but the inclusion of these in the code of the business object still is not correct. It seems that annotations/syntax that makes it easy to add extension points for advices written as closures is what is needed to have proper support for aop in java. Take a look at look this and let me know what you think. Since closures have not been proposed as a jsr due to conflicting view from within Google, maybe its something we would want to do with this aop view in mind. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4022612#4022612 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4022612

18 years, 10 months

1
0
0 / 0

[Design of JCA on JBoss] - Re: JBAS-1437 RARMetaDataRepository

by weston.price＠jboss.com

Sorry, I am not sure I follow. Right now what I do is simply parse the *-ds.xml file using straight JAXP. While this works, is quick and has no dependencies on any binding framework (JAXB, JBossXB) I started thinking about it a bit more. The problems I see with this are 1) The element name mappings have to be hardcoded somewhere. Example: <min-pool-size/> <max-pool-size/> <connection-url/> <xa-datasource-property/> All of this stuff has to resolve to something in the MetaData, and then applied correctly to ServiceMetaData instances to construct and deploy the MBeans for a MCF. Right now I simply have a helper class that maintains a map of these values that the parser consults when processing the *-ds.xml file. It's this mess that I thought about replacing with something more extensible, ie, an aspectized parser where each aspect in the chain knows enough about the *-ds.xml format to construct the MetaData. As new elements get added to the *-ds.xml file, these aspects can be extended to accomodate this. 2) The parsing itself looks pretty ugly. Again, JAXP was used more as a convenience than anything else. It was *simple* from the perspective that I could get something up and running, but now I am rethinking the design. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4022609#4022609 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4022609

18 years, 10 months

1
0
0 / 0

[Design of POJO Server] - Jboss build from the head starting with errors .

by vickyk

anonymous wrote : 23:50:33,562 INFO [ProfileImpl] Using profile root:C:\svn\trunk\build\output\jb | oss-5.0.0.Beta2\bin\file:\C:\svn\trunk\build\output\jboss-5.0.0.Beta2\server\def | ault\profile | 23:50:40,296 INFO [ServerInfo] Java version: 1.5.0_01,Sun Microsystems Inc. | 23:50:40,296 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0_01-b08 | ,Sun Microsystems Inc. | 23:50:40,296 INFO [ServerInfo] OS-System: Windows XP 5.1,x86 | 23:50:40,421 INFO [JMXKernel] Legacy JMX core initialized | 23:50:54,046 INFO [WebService] Using RMI server codebase: http://D6XT8G1S:8083/ | | 23:51:02,234 ERROR [BeanDeployer] Error during deployment: vfsfile:/C:/svn/trunk | /build/output/jboss-5.0.0.Beta2/server/default/deployers/aop-mc-int-aspect-beans | .xml | org.jboss.deployers.spi.DeploymentException: Error creating managed object for v | fsfile:/C:/svn/trunk/build/output/jboss-5.0.0.Beta2/server/default/deployers/aop | -mc-int-aspect-beans.xml | at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentExcept | ion(DeploymentException.java:49) | at org.jboss.deployers.plugins.deployers.helpers.AbstractParsingDeployer | .createMetaData(AbstractParsingDeployer.java:121) The above errors crops up when I am trying to run the jboss5 which I am building from https://svn.jboss.org/repos/jbossas/trunk I have been using the svn plugin for the Ecllipse to checkout the source code and here is the latest updated version anonymous wrote : Updated to revision 60910. | ===== File Statistics: ===== | Merged: 1 Any hints about what I am doing wrong ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4022607#4022607 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4022607

18 years, 10 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Automatic Scoped Kernels - A good idea

by scott.stark＠jboss.org

I would like to see the scoped kernel notion overviewed in the context of the existing architecture as it seems its too much of a piecewise prototype at this point. The main sticking points are namespaces, cross kernel dependencies, and relation to type systems/class loaders. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4022604#4022604 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4022604

18 years, 10 months

1
0
0 / 0

[Design of JCA on JBoss] - Re: JBAS-1437 RARMetaDataRepository

by scott.stark＠jboss.org

The natural way to do that is via the use of separate namespaces. If you transformed the raw unpartitioned ds.xml into a version where the separate concernce where under separate namespaces jbossxb naturually would support running separate binding layers for this. Hopefully jaxb could do the same. Alternatively, you just reparse the same file multiple times. I think the only question is what usecases need better helpers to avoid excessive duplication in new deployers. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4022601#4022601 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4022601

18 years, 10 months

1
0
0 / 0

[Design of JCA on JBoss] - Re: JBAS-1437 RARMetaDataRepository

by weston.price＠jboss.com

This simply involves the parsing/binding of the *-ds.xml file. I was just throwing out an idea to break up the actual parsing into aspects. Example: ConnectionPoolParsing aspect knows about the specific elements that make up the ConnectionPoolMetaData. ServiceDependency aspect knows about the specific elements that constitute ServiceMean dependencies in the *-ds.xml file. These aspects would form a parsing chain that gets applied on parse. Nothign more than that. Again, this would be an alternate approach (refactoring) as I have already written the JAXP based parser of the *-ds.xml file to construct the MetaData which works, but is not as elegant/clean as I would have liked. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4022593#4022593 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4022593

18 years, 10 months

1
0
0 / 0

[Design of JCA on JBoss] - Re: JBAS-1437 RARMetaDataRepository

by scott.stark＠jboss.org

The resolution to the JAXB, JBossXB was that either could be used. It would be better to talk about what your looking for in the context of a testcase. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4022585#4022585 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4022585

18 years, 10 months

1
0
0 / 0

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