[Design of JBoss Web Services] - Re: Using jbossws/trunk for jboss-5.0, jboss-4.2, jboss-4.0.
by dwin
Sorry to be a newbie about this, I am not too familiar with the build environment of JBossWS
The tests fail for me, it doesn't compile. It seems to be another class path issue where Junit.jar cannot be found (the only instance of junit.jar is in jbossws/build/thirdparty). I even put a force get in my ant.properties in the build folder.
I get the following output, it appears to fail at the "main" task. It all fails on Junit classes but it stops at 100 errors. I am guessing even if I do manually junit.jar to the classpath, there will be other dependency errors to deal with. I am guessing there is something wrong with my ant.properties or something did not check out right (via SVN).
| Buildfile: build.xml
|
| prepare:
| [echo] -----------------------------------------------
| [echo] jboss.home = C:\examples\jboss-4.2.x\build\output\jboss-4.2.0.CR1-ejb3
| [echo] tomcat.home = ${tomcat.home}
| [echo] java.home = C:\Sun\AppServer\jdk\jre
| [echo] endorsed.dirs = C:\examples\jboss-4.2.x\build\output\jboss-4.2.0.CR1-ejb3/lib/endorsed
| [echo] -----------------------------------------------
| .
| .
| .
| .
| . (taken out for the sake of keeping the post short)
|
| [unzip] Expanding: C:\examples\jbossws\build\thirdparty\ejb3.deployer.zip into C:\examples\jbossws\build\thirdparty
|
| thirdparty-classpath:
|
| thirdparty:
|
| init:
| [echo] excludefile = tests-jboss42-excludes.txt
|
| compile14:
|
| compile15:
| [javac] Compiling 1006 source files to C:\examples\jbossws\jbossws-tests\output\classes
| [javac] C:\examples\jbossws\jbossws-tests\src\main\java\org\jboss\test\ws\JBossWSTest.java:34: package junit.framework does not exist
| [javac] import junit.framework.TestCase;
| [javac] ^
| [javac] C:\examples\jbossws\jbossws-tests\src\main\java\org\jboss\test\ws\JBossWSTest.java:48: cannot find symbol
| [javac] symbol: class TestCase
| [javac] public abstract class JBossWSTest extends TestCase
| [javac] ^
| [javac] C:\examples\jbossws\jbossws-tests\src\main\java\org\jboss\test\ws\JBossWSTestSetup.java:24: package junit.extensions does not exist
| [javac] import junit.extensions.TestSetup;
| [javac] ^
| [javac] C:\examples\jbossws\jbossws-tests\src\main\java\org\jboss\test\ws\JBossWSTestSetup.java:25: package junit.framework does not exist
| [javac] import junit.framework.TestSuite;
| [javac] ^
| [javac]
| .
| .
| .
| .
| .
| .(taken out for the sake of keeping the post short)
|
| [javac] 100 errors
|
| compile:
|
| copy-resources:
|
| generate-sources:
| [wstools] log4j:ERROR setFile(null,false) call failed.
| [wstools] java.io.FileNotFoundException: \test.log (Access is denied)
| [wstools] at java.io.FileOutputStream.open(Native Method)
| [wstools] at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
| [wstools] at java.io.FileOutputStream.<init>(FileOutputStream.java:102)
| [wstools] at org.apache.log4j.FileAppender.setFile(FileAppender.java:272)
| [wstools] at org.apache.log4j.FileAppender.activateOptions(FileAppender.java:151)
| [wstools] at org.apache.log4j.DailyRollingFileAppender.activateOptions(DailyRollingFileAppender.java:206)
| [wstools] at org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:247)
| [wstools] at org.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.java:210)
| [wstools] at org.apache.log4j.xml.DOMConfigurator.findAppenderByName(DOMConfigurator.java:140)
| [wstools] at org.apache.log4j.xml.DOMConfigurator.findAppenderByReference(DOMConfigurator.java:153)
| [wstools] at org.apache.log4j.xml.DOMConfigurator.parseChildrenOfLoggerElement(DOMConfigurator.java:415)
| [wstools] at org.apache.log4j.xml.DOMConfigurator.parseRoot(DOMConfigurator.java:384)
| [wstools] at org.apache.log4j.xml.DOMConfigurator.parse(DOMConfigurator.java:783)
| [wstools] at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:666)
| [wstools] at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:616)
| [wstools] at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:602)
| [wstools] at org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:460)
| [wstools] at org.apache.log4j.LogManager.<clinit>(LogManager.java:113)
| [wstools] at org.jboss.logging.log4j.Log4jLoggerPlugin.init(Log4jLoggerPlugin.java:80)
| [wstools] at org.jboss.logging.Logger.getDelegatePlugin(Logger.java:393)
| [wstools] at org.jboss.logging.Logger.<init>(Logger.java:119)
| [wstools] at org.jboss.logging.Logger.getLogger(Logger.java:357)
| [wstools] at org.jboss.ws.tools.WSTools.<clinit>(Unknown Source)
| [wstools] at org.jboss.ws.tools.ant.wstools.execute(Unknown Source)
| [wstools] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
| [wstools] at org.apache.tools.ant.Task.perform(Task.java:364)
| [wstools] at org.apache.tools.ant.Target.execute(Target.java:341)
| [wstools] at org.apache.tools.ant.Target.performTasks(Target.java:369)
| [wstools] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
| [wstools] at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
| [wstools] at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
| [wstools] at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
| [wstools] at org.apache.tools.ant.Main.runBuild(Main.java:668)
| [wstools] at org.apache.tools.ant.Main.startAnt(Main.java:187)
| [wstools] at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
| [wstools] at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
| [wstools] log4j:ERROR Either File or DatePattern options are not set for appender [FILE].
| [wstools] java.lang.NullPointerException
| [wstools] at java.lang.System.arraycopy(Native Method)
| [wstools] at org.apache.xerces.impl.xs.XSModelImpl.getAnnotations(Unknown Source)
| [wstools] at org.jboss.ws.metadata.wsdl.xmlschema.WSSchemaUtils.copyXSModel(Unknown Source)
| [wstools] at org.jboss.ws.tools.JavaToXSD.parseSchema(Unknown Source)
| [wstools] at org.jboss.ws.tools.wsdl.WSDL11Reader.processTypes(Unknown Source)
| [wstools] at org.jboss.ws.tools.wsdl.WSDL11Reader.processDefinition(Unknown Source)
| [wstools] at org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory.parse(Unknown Source)
| [wstools] at org.jboss.ws.tools.WSDLToJava.convertWSDL2Java(Unknown Source)
| [wstools] at org.jboss.ws.tools.helpers.ToolsHelper.handleWSDLToJavaGeneration(Unknown Source)
| [wstools] at org.jboss.ws.tools.WSTools.process(Unknown Source)
| [wstools] at org.jboss.ws.tools.WSTools.generate(Unknown Source)
| [wstools] at org.jboss.ws.tools.ant.wstools.execute(Unknown Source)
| [wstools] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
| [wstools] at org.apache.tools.ant.Task.perform(Task.java:364)
| [wstools] at org.apache.tools.ant.Target.execute(Target.java:341)
| [wstools] at org.apache.tools.ant.Target.performTasks(Target.java:369)
| [wstools] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
| [wstools] at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
| [wstools] at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
| [wstools] at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
| [wstools] at org.apache.tools.ant.Main.runBuild(Main.java:668)
| [wstools] at org.apache.tools.ant.Main.startAnt(Main.java:187)
| [wstools] at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
| [wstools] at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
|
|
Any help would be much apperciated.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4000180#4000180
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4000180
19 years, 3 months
[Design of POJO Server] - bean/mbean integration issue
by scott.stark＠jboss.org
I was hoping to be able to reference the jboss-service.xml mbean for the socket remoting transport to register a handler for the ProfileService with it similar to how deployers register with the MainDeployer:
| ...
| <!--
| Add a ProfileService handler to the remoting socket connector
| -->
| <bean name="ProfileServiceInvocationHandler"
| class="org.jboss.aspects.remoting.AOPRemotingInvocationHandler">
| <install bean="jboss.remoting:service=Connector,transport=socket" method="addInvocationHandler">
| <parameter>ProfileService</parameter>
| <parameter><this/></parameter>
| </install>
| <uninstall bean="jboss.remoting:service=Connector,transport=socket" method="removeInvocationHandler">
| <parameter>ProfileService</parameter>
| </uninstall>
| </bean>
|
however, there is a type conflict showing up:
| 12:56:19,930 ERROR [AbstractKernelController] Error installing to Installed: name=ProfileServiceInvocationHandler state=Start
| java.lang.ClassCastException: org.jboss.system.microcontainer.ServiceControllerContext
| at org.jboss.kernel.plugins.dependency.InstallAction.installActionInternal(InstallAction.java:67)
| at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.installAction(KernelControllerContextAction.java:187)
| at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.install(KernelControllerContextAction.java:126)
| at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
| at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:233)
| at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:709)
| at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:430)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:540)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:474)
| at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:274)
| at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:177)
| at org.jboss.deployers.plugins.deployers.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:67)
| at org.jboss.deployers.plugins.deployers.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:42)
| at org.jboss.deployers.plugins.deployers.helpers.AbstractSimpleRealDeployer.deploy(AbstractSimpleRealDeployer.java:53)
| at org.jboss.deployers.plugins.deployer.AbstractSimpleDeployer.commitDeploy(AbstractSimpleDeployer.java:52)
| at org.jboss.deployers.plugins.deployer.DeployerWrapper.commitDeploy(DeployerWrapper.java:156)
| at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:523)
| at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:534)
| at org.jboss.deployers.plugins.deployment.MainDeployerImpl.process(MainDeployerImpl.java:461)
| at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:372)
| ...
|
To allow for such an interaction, the mbean needs to have a mapping of its ServiceControllerContext to a KernelControllerContext, or ServiceControllerContext and KernelControllerContext need a shared base class that adds a common DispatchJoinPoint notion.
I can workaround this by moving the legacy remoting mbean to a mc bean (hopefully).
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4000149#4000149
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4000149
19 years, 3 months