[Design of JBoss Build System] - aop-mc-int tests failing
by kabir.khan＠jboss.com
| Kabir@KabirDell ~/sourcecontrol/microcontainer/aop-mc-int
| $ mvn surefire-report:report -Pant-tests-weave
| [INFO] Scanning for projects...
| [INFO] Searching repository for plugin with prefix: 'surefire-report'.
| WAGON_VERSION: 1.0-beta-2
| [INFO] ----------------------------------------------------------------------------
| [INFO] Building JBoss Microcontainer AOP MC INT
| [INFO] task-segment: [surefire-report:report]
| [INFO] ----------------------------------------------------------------------------
| [INFO] Preparing surefire-report:report
| [INFO] artifact org.apache.maven.plugins:maven-antrun-plugin: checking for updates from jboss
| [INFO] [resources:resources]
| [INFO] Using default encoding to copy filtered resources.
| [INFO] [compiler:compile]
| [INFO] Nothing to compile - all classes are up to date
| [INFO] [resources:testResources]
| [INFO] Using default encoding to copy filtered resources.
| [INFO] [compiler:testCompile]
| [INFO] Nothing to compile - all classes are up to date
| [INFO] [surefire:test]
| [INFO] Tests are skipped.
| [INFO] [surefire:test {execution: weave}]
| [INFO] Tests are skipped.
| [INFO] [surefire:test {execution: weave-secure}]
| [INFO] Tests are skipped.
| [INFO] [surefire:test {execution: no-weave}]
| [INFO] Tests are skipped.
| [INFO] [surefire:test {execution: no-weave-secure}]
| [INFO] Tests are skipped.
| Downloading: http://repository.jboss.org/maven2/junit/junit/3.8.2/junit-3.8.2.jar
| [WARNING] Unable to get resource 'junit:junit:jar:3.8.2' from repository jboss (http://repository.jboss.org/maven2)
| Downloading: http://repository.jboss.org/maven2//junit/junit/3.8.2/junit-3.8.2.jar
| [WARNING] Unable to get resource 'junit:junit:jar:3.8.2' from repository repository.jboss.org (http://repository.jboss.org/maven2/)
| Downloading: http://repository.jboss.org/maven2/junit/junit/3.8.2/junit-3.8.2.jar
| [WARNING] Unable to get resource 'junit:junit:jar:3.8.2' from repository jboss (http://repository.jboss.org/maven2)
| Downloading: http://repo1.maven.org/maven2/junit/junit/3.8.2/junit-3.8.2.jar
| 117K downloaded
| [INFO] [antrun:run {execution: ant-tests-weave}]
| [INFO] Executing tasks
| [mkdir] Created dir: C:\cygwin\home\Kabir\sourcecontrol\microcontainer-beta4\aop-mc-int\target\surefire-reports\ant-weave
| [mkdir] Created dir: C:\cygwin\home\Kabir\sourcecontrol\microcontainer-beta4\aop-mc-int\target\log
| [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 2.797 sec
| java.io.FileNotFoundException: C:\cygwin\home\Kabir\sourcecontrol\microcontainer-beta4\aop-mc-int\junitvmwatcher2026226667.properties (The system cannot find the file specified)
| at java.io.FileInputStream.open(Native Method)
| at java.io.FileInputStream.<init>(FileInputStream.java:106)
| at java.io.FileReader.<init>(FileReader.java:55)
| at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.executeAsForked(JUnitTask.java:1028)
| at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java:817)
| at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.executeOrQueue(JUnitTask.java:1657)
| at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java:764)
| at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
| 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 org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105)
| at org.apache.tools.ant.Task.perform(Task.java:348)
| at org.apache.tools.ant.Target.execute(Target.java:357)
| at org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractAntMojo.java:108)
| at org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:83)
| at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:420)
| at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
| at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
| at org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:896)
| at org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:739)
| at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:510)
| at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
| at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
| at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
| at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
| at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
| at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:330)
| at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:123)
| at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
| 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 org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
| at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
| at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
| at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
| [junit] Running org.jboss.test.aop.junit.MicrocontainerJunitSmokeTestCase
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4086645#4086645
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4086645
18 years, 6 months
[Design of POJO Server] - Re: Unifying metadata
by scott.stark＠jboss.org
In going through the initial extraction of metadata out of jbossas, its seems that what needs to be done is:
1. The existing ObjectModelFactoryDeployer based deployers producing legacy metadata need to be converted to SchemaResolverDeployer type deployers that produce the new metadata, and then create the legacy wrapper using the new metadata as the delegate. The JBossXBBuilder would be used to create the SchemaBinding for the new metadata.
One little issue here is that the SchemaResolverDeployer does not have a SchemaBindingResolver getResolver() method to allow subclasses to easily extend the default resolver.
2. Fix up misc uses of the legacy metadata. Missing methods, creation without the wrapper, etc.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4086639#4086639
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4086639
18 years, 6 months
[Design of POJO Server] - Re: ManagedOperation aspects for the ProfileService.Manageme
by alesj
"scott.stark(a)jboss.org" wrote : Yes, you have to dispatch the methods as needed. Ops on the ManagedOperation can be handled by the existing remoting wiring. The wiring for invoke to the runtime component is what you need to do such that ManagementViewImpl.invoke does the dispatch.
|
The code is commited.
I've refactored the ManagementViewImpl - no need for opMap --> added ManagedOperationDelegate that holds all the needed information.
I've also changed the ProfileServiceInvocationHandler, since there is no need for us to distinguish between ProfileService.ManagedOperation@ and other calls. I've only left the ManagementView result set to a proxy.
I added two new interfaces:
1) MetaDataNameProvider: extracts component name from MetaData
2) RuntimeComponentDispatcher: pushes attachment to MetaDataNameProvider to get the name, looks up the component via 'registry', and dispatches method invocation on the found runtime component
Currently there are just default impls:
1) Name from BeanMetaData and ServiceMetaData
2) MC's Controller dispatch
Is this what we've been looking for? :-)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4086618#4086618
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4086618
18 years, 6 months