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

[Design of POJO Server] - Re: Running with the full featured profile service

by charles.crouch＠jboss.com

I'm getting exactly two tests passing, just not including the one I really want :-). FWIW BasicDeploymentTemplateInfo is in /trunk/profileservice and getting built. Testcase: testProfileKeys took 2.653 sec | Testcase: testDataSourceType took 0.151 sec | Testcase: testAddDataSource took 0.06 sec | Caused an ERROR | org.jboss.profileservice.management.plugins.BasicDeploymentTemplateInfo | java.lang.ClassNotFoundException: org.jboss.profileservice.management.plugins.BasicDeploymentTemplateInfo | at java.net.URLClassLoader$1.run(URLClassLoader.java:200) | at java.security.AccessController.doPrivileged(Native Method) | at java.net.URLClassLoader.findClass(URLClassLoader.java:188) | at java.lang.ClassLoader.loadClass(ClassLoader.java:306) | at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268) | at java.lang.ClassLoader.loadClass(ClassLoader.java:251) | at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) | at java.lang.Class.forName0(Native Method) | at java.lang.Class.forName(Class.java:242) | at org.jboss.remoting.loading.RemotingClassLoader.loadClass(RemotingClassLoader.java:50) | at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) | at java.lang.Class.forName0(Native Method) | at java.lang.Class.forName(Class.java:242) | at org.jboss.remoting.loading.ObjectInputStreamWithClassLoader.resolveClass(ObjectInputStreamWithClassLoader.java:139) | at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1543) | at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1465) | at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1698) | at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1304) | at java.io.ObjectInputStream.readObject(ObjectInputStream.java:349) | at org.jboss.aop.joinpoint.InvocationResponse.readExternal(InvocationResponse.java:122) | at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1758) | at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1716) | at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1304) | at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1917) | at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1841) | at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1718) | at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1304) | at java.io.ObjectInputStream.readObject(ObjectInputStream.java:349) | at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.receiveObject(JavaSerializationManager.java:132) | at org.jboss.remoting.marshal.serializable.SerializableUnMarshaller.read(SerializableUnMarshaller.java:66) | at org.jboss.invocation.unified.marshall.InvocationUnMarshaller.read(InvocationUnMarshaller.java:48) | at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.versionedRead(MicroSocketClientInvoker.java:485) | at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:356) | at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:125) | at org.jboss.remoting.Client.invoke(Client.java:589) | at org.jboss.remoting.Client.invoke(Client.java:581) | at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:62) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at AOPProxy$1.getTemplate(AOPProxy$1.java) | at org.jboss.test.profileservice.test.ProfileServiceUnitTestCase.testAddDataSource(ProfileServiceUnitTestCase.java:91) | at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:74) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at AOPProxy$1.getTemplate(AOPProxy$1.java) | at org.jboss.test.profileservice.test.ProfileServiceUnitTestCase.testAddDataSource(ProfileServiceUnitTestCase.java:91) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4002001#4002001 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4002001

19 years, 2 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBMESSAGING-674 - Propagating changes on ClusteredConnec

by clebert.suconic＠jboss.com

Never mind my latest post... I will put this into ServerConnectionFactoryEndpoint... a ServerConnectionFactoryEndpoing will know the connection it has created. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4001999#4001999 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4001999

19 years, 2 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBMESSAGING-674 - Propagating changes on ClusteredConnec

by clebert.suconic＠jboss.com

I wanted to have a static Collection/Map on server side for all active collections. I could navigate on JMSDispatcher for this but I wanted to capture ServerConnectionFactoryEndpoint::createConnection and ServerConnectionEndpoint::close to keep a list of these active connections. This is to send the notification for all active connections on update their respective CFs. I was going to add this into JMSDispatcher but didn't se a proper place. Any ideas where I could put such static map? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4001997#4001997 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4001997

19 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Soap with Attachments and document/literal

by darran.lofthouse＠jboss.com

I think the original WSDL at the top of the user post is correct, the basic profile only specifies that the part must reference elements if the part is referenced from a soapbind:body element, it doesn't specify a requirement for mime:content parts. anonymous wrote : R2204 A document-literal binding in a DESCRIPTION MUST refer, in each of its soapbind:body element(s), only to wsdl:part element(s) that have been defined using the element attribute. The attachments profile also contains the following parts defined in a document/literal example: - | <wsdl:message name="ClaimIn"> | <wsdl:part name="body" element="types:ClaimDetail"/> | <wsdl:part name="ClaimPhoto" type="xsd:base64Binary"/> | </wsdl:message> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4001996#4001996 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4001996

19 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBWS-1452 - WSDL To Java, Array unwrapping.

by jason.greene＠jboss.com

The case in 732 is a contrived example that was made to have good coverage of jbossxb's handling of nulls and arrays. In most cases, a document/literal wrapped wsdl will not wrap the array yet again in another element definition. Take a look at the wscompile output of testMethod(String[] request, int foo) You should see something like this | <complexType name="testMethod"> | <sequence> | <element name = "request" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/> | <element name="foo" type="xsd:int"/> | </sequence> | </complexType> | The only reason to create a wrapper element is to be able to have a distinction between a null array, and a null array element. Without the wrapper, as in above, this is not possible. Even so, for the purpose of simplifying the wsdl, most toolkits will make the sacrifice. That said there is no reason to not do it for document/literal, so you can disable that check if you like. -Jason View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4001994#4001994 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4001994

19 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Maven build scripts

by pgier

Hi Everyone, I created some maven scripts for building the microcontainer project. The scripts are organized the same way that the jboss common scripts are organized. There is one main pom.xml in the build directory, and each subproject has its own pom.xml. Each subproject can be built by itself (assuming it's not dependent on recent changes in another subproject) or by building the entire project. Here is what the main pom.xml file looks like: | <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" | xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> | <modelVersion>4.0.0</modelVersion> | <groupId>jboss</groupId> | <version>2.0.0.Beta</version> | <artifactId>jboss-microcontainer</artifactId> | <name>JBoss Microcontainer Build</name> | <url>http://www.jboss.org</url> | <description>Parent POM for the JBoss Microcontainer Projects</description> | <licenses> | <license> | <name>lgpl</name> | <url>http://repository.jboss.com/licenses/lgpl.txt</url> | </license> | </licenses> | <organization> | <name>JBoss Inc.</name> | <url>http://www.jboss.org</url> | </organization> | | <packaging>pom</packaging> | <modules> | <module>../container</module> | <module>../dependency</module> | <module>../metatype</module> | <module>../kernel</module> | <module>../managed</module> | <module>../deployers</module> | <module>../aop-mc-int</module> | <module>../osgi-int</module> | <module>../spring-int</module> | </modules> | <reporting> | <plugins> | <plugin> | <groupId>org.apache.maven.plugins</groupId> | <artifactId>maven-project-info-reports-plugin</artifactId> | <reportSets> | <reportSet> | <reports> | <report>dependencies</report> | <report>issue-tracking</report> | <report>license</report> | <report>scm</report> | </reports> | </reportSet> | </reportSets> | </plugin> | </plugins> | </reporting> | | <distributionManagement> | <repository> | <id>cvs-file-repository</id> | <url>file://${maven.cvs.root}</url> | </repository> | </distributionManagement> | | </project> | | And here is the one for the container subproject: | | <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" | xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> | <modelVersion>4.0.0</modelVersion> | <groupId>jboss</groupId> | <artifactId>jboss-container</artifactId> | <packaging>jar</packaging> | <version>2.0.0.Beta</version> | <name>JBoss Microcontainer Container</name> | <url>http://www.jboss.org</url> | <description>JBoss Microcontainer Container</description> | <licenses> | <license> | <name>lgpl</name> | <url>http://repository.jboss.com/licenses/lgpl.txt</url> | </license> | </licenses> | <organization> | <name>JBoss Inc.</name> | <url>http://www.jboss.org</url> | </organization> | | <repositories> | <repository> | <id>jboss</id> | <name>JBoss Inc. Repository</name> | <layout>default</layout> | <url>http://repository.jboss.com/maven2/</url> | <snapshots> | <enabled>true</enabled> | </snapshots> | </repository> | </repositories> | | <pluginRepositories> | <pluginRepository> | <id>jbosspluginrepo</id> | <name>jboss plugin repository</name> | <url>http://repository.jboss.com/maven2</url> | <layout>default</layout> | <snapshots> | <enabled>false</enabled> | <updatePolicy>never</updatePolicy> | </snapshots> | </pluginRepository> | </pluginRepositories> | | <build> | <sourceDirectory>src/main</sourceDirectory> | <testSourceDirectory>src/tests</testSourceDirectory> | <finalName>${artifactId}</finalName> | <plugins> | |  | <plugin> | <artifactId>maven-compiler-plugin</artifactId> | <version>2.0</version> | <configuration> | <optimize>true</optimize> | <source>1.5</source> | <target>1.5</target> | </configuration> | </plugin> | | <plugin> | <groupId>org.apache.maven.plugins</groupId> | <artifactId>maven-jar-plugin</artifactId> | <configuration> | <archive> | <manifest> | <addDefaultSpecificationEntries>true</addDefaultSpecificationEntries> | <addDefaultImplementationEntries>true</addDefaultImplementationEntries> | </manifest> | </archive> | </configuration> | </plugin> | |  | <plugin> | <artifactId>maven-source-plugin</artifactId> | <inherited>true</inherited> | <executions> | <execution> | <goals> | <goal>jar</goal> | </goals> | </execution> | </executions> | </plugin> | <plugin> | <groupId>org.apache.maven.plugins</groupId> | <artifactId>maven-surefire-plugin</artifactId> | <configuration> | <skip>true</skip> | </configuration> | </plugin> | | </plugins> | </build> | <dependencies> |  | <dependency> | <groupId>javassist</groupId> | <artifactId>javassist</artifactId> | <version>3.4.GA</version> | </dependency> | <dependency> | <groupId>jboss</groupId> | <artifactId>jboss-vfs</artifactId> | <version>2.0.4.snapshot</version> | </dependency> | |  | <dependency> | <groupId>jboss</groupId> | <artifactId>jboss-test</artifactId> | <version>1.0.1.GA</version> | <scope>test</scope> | </dependency> | <dependency> | <groupId>junit</groupId> | <artifactId>junit</artifactId> | <version>3.8.1</version> | <scope>test</scope> | </dependency> | <dependency> | <groupId>jboss.profiler.jvmti</groupId> | <artifactId>jboss-profiler-jvmti</artifactId> | <version>1.0.0.CR5</version> | <scope>test</scope> | </dependency> | </dependencies> | </project> | | The other pom.xml files look pretty similar to the one for the container subproject, just with different dependency lists and a few other minor differences. Let me know if you have any comments or questions about these files. I'm planning to commit them to the repository next to the build.xml as long as no one has a problem with this. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4001986#4001986 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4001986

19 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Soap with Attachments and document/literal

by jason.greene＠jboss.com

I will revert the patch that disabled this, and take a look and see if there are any bugs with doc/lit attachments, but the use case that that jira issue was testing was using an invalid WSDL file, so this may have been the real problem. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4001985#4001985 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4001985

19 years, 2 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBMESSAGING-674 - Propagating changes on ClusteredConnec

by clebert.suconic＠jboss.com

I'm thinking about how to fix this racing condition: I - ClientClusteredConnectionFactoryDelegate has this following failoverMap: Server 1->Server2->Server3->Server 1 II - Server1 is killed III - Now the CF::failoverMap is updated to: Server2->Server3->Server2 IV - A failure happens on a connection directed on Server1. FailoverMap doesn't have the information about Server1 any more. I will keep coding and maybe we will need to have the failoverMap on the Connection instead of ConnectionFactory, and having failover updating these fields on Connection only when a failure happens. As I said I am thinking about how to fix this, and I'm almost sure how to fix this. I wanted to post this just to keep the team informed. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4001983#4001983 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4001983

19 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Soap with Attachments and document/literal

by darran.lofthouse＠jboss.com

That's good, my understanding matches yours - I thought we had full support for attachments and it was just tools that needed enhancing then I found that comment. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4001975#4001975 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4001975

19 years, 2 months

1
0
0 / 0

[Design of POJO Server] - Re: bean/mbean integration issue

by scott.stark＠jboss.org

I added a org.jboss.test.system.controller.integration.test.InstallMCToJMXUnitTestCase and I'm still seeing a CCE in the test: | 647 DEBUG [SimpleSARDeployer] Deployed file:/home/svn/JBossHead/jboss-head/system-jmx/src/resources/tests/org/jboss/test/system/controller/integration/test/InstallMCToJMXUnitTestCase.xml took 146ms | 673 DEBUG [InstallMCToJMXUnitTestCase] Deploying file:/home/svn/JBossHead/jboss-head/system-jmx/src/resources/tests/org/jboss/test/system/controller/integration/test/InstallMCToJMXUnitTestCase-mc.xml | 1134 ERROR [AbstractKernelController] Error installing to Installed: name=Test state=Start | java.lang.ClassCastException: org.jboss.system.microcontainer.ServiceControllerContext | at org.jboss.kernel.plugins.dependency.InstallAction.installActionInternal(InstallAction.java:59) | 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.kernel.plugins.deployment.AbstractKernelDeployer.deployBean(AbstractKernelDeployer.java:302) | at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBeans(AbstractKernelDeployer.java:272) | at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deploy(AbstractKernelDeployer.java:119) | at org.jboss.kernel.plugins.deployment.BasicKernelDeployer.deploy(BasicKernelDeployer.java:64) | at org.jboss.kernel.plugins.deployment.xml.BasicXMLDeployer.deploy(BasicXMLDeployer.java:76) | at org.jboss.kernel.plugins.deployment.xml.BasicXMLDeployer.deploy(BasicXMLDeployer.java:146) | at org.jboss.test.system.controller.integration.test.IntegrationTestDelegate.deployMC(IntegrationTestDelegate.java:219) | at org.jboss.test.system.controller.integration.test.IntegrationTestDelegate.deployMC(IntegrationTestDelegate.java:291) | at org.jboss.test.system.controller.integration.test.IntegrationTestDelegate.setUp(IntegrationTestDelegate.java:73) | at org.jboss.test.AbstractTestSetup.setUp(AbstractTestSetup.java:63) | at org.jboss.test.AbstractTestCaseWithSetup.setUp(AbstractTestCaseWithSetup.java:97) | at org.jboss.test.system.controller.AbstractControllerTest.setUp(AbstractControllerTest.java:77) | at junit.framework.TestCase.runBare(TestCase.java:125) | at junit.framework.TestResult$1.protect(TestResult.java:106) | at junit.framework.TestResult.runProtected(TestResult.java:124) | at junit.framework.TestResult.run(TestResult.java:109) | at junit.framework.TestCase.run(TestCase.java:118) | Can you validate that the mc snapshot includes your changes. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4001971#4001971 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4001971

19 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums January 2007