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

[Design the new POJO MicroContainer] - Re: serializable KernelDeployment

by alesj

"adrian(a)jboss.org" wrote : "alesj" wrote : | | So if our returned MetaData is non-Serializable, we should throw exception (since we want all our MD to be serializable, right?)? | | | | Correct. | Ok, for MetaData there is no problem. What do we do with JavaBeans (which now fail - since with wildcard test's we use plain java.lang.Object)? anonymous wrote : | This is a candidate for AbstractTestCase in the jboss-test project. | | | | /** | | * Check we have the expected type | | * | | * @param <T> the expected type | | * @param o the object | | * @param expectedType the excepted class of the exception | | * @return the expected type | | */ | | protected <T> T assertInstanceOf(Object o, Class<T> expectedType) | | { | | return assertInstanceOf(o, expectedType, true); | | } | | | | /** | | * Check we have the expected type | | * | | * @param <T> the expected type | | * @param o the object | | * @param expectedType the excepted class of the exception | | * @param allowNull whether the object can be null | | * @return the expected type | | */ | | protected <T> T assertInstanceOf(Object o, Class<T> expectedType, boolean allowNull) | | { | | if (expectedType == null) | | fail("Null expectedType"); | | | | if (o == null && allowNull) | | return null; | | | | try | | { | | return expectedType.cast(o); | | } | | catch (ClassCastException e) | | { | | fail("Object " + o + " of class " + o.getClass().getName() + " is not an instanceof " + expectedType.getName()); | | } | | } | | Cool. I added this code to test project. Will use it in MC once I update test snapshot. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4005296#4005296 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4005296

19 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: @PortComponent replacement

by adrian＠jboss.org

"heiko.braun(a)jboss.com" wrote : While working on config issues i realized that the PortComponentAnnotation needed refactoring. It's now split into @WebContext and @EndpointConfig. | The main reason for this was the distinction between client and server side annotations. | This change breaks the EJB3 testsuite | [ejort@warjort ejb3]$ ./build.sh -f build-test.xml | Buildfile: build-test.xml | Overriding previous definition of reference to jboss.test.classpath | | init: | | compile-classes: | [javac] Compiling 1124 source files to /home/ejort/jboss-head/ejb3/output/test-classes | [javac] /home/ejort/jboss-head/ejb3/src/test/org/jboss/ejb3/test/regression/ejbthree440/model/MyResource.java:12: warning: unmappable character for encoding UTF8 | [javac] * @author Ortwin Gl? | [javac] ^ | [javac] /home/ejort/jboss-head/ejb3/src/test/org/jboss/ejb3/test/jaxws/EndpointEJB.java:36: package org.jboss.ws.annotation does not exist | [javac] import org.jboss.ws.annotation.PortComponent; | [javac] ^ | [javac] /home/ejort/jboss-head/ejb3/src/test/org/jboss/ejb3/test/jaxws/unit/ContextEJBTestCase.java:37: package org.jboss.ws.metadata.wsdl does not exist | [javac] import org.jboss.ws.metadata.wsdl.WSDLDefinitions; | [javac] ^ | [javac] /home/ejort/jboss-head/ejb3/src/test/org/jboss/ejb3/test/jaxws/unit/ContextEJBTestCase.java:38: package org.jboss.ws.tools.wsdl does not exist | [javac] import org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory; | [javac] ^ | [javac] /home/ejort/jboss-head/ejb3/src/test/org/jboss/ejb3/test/webservices/jsr181/EJB3Bean.java:25: package org.jboss.ws.annotation does not exist | [javac] import org.jboss.ws.annotation.PortComponent; | [javac] ^ | [javac] /home/ejort/jboss-head/ejb3/src/test/org/jboss/ejb3/test/webservices/jsr181/EndpointInterface.java:24: package org.jboss.ws.annotation does not exist | [javac] import org.jboss.ws.annotation.PortComponent; | [javac] ^ | [javac] /home/ejort/jboss-head/ejb3/src/test/org/jboss/ejb3/test/webservices/unit/JSR181TestCase.java:37: package org.jboss.ws.metadata.wsdl does not exist | [javac] import org.jboss.ws.metadata.wsdl.WSDLDefinitions; | [javac] ^ | [javac] /home/ejort/jboss-head/ejb3/src/test/org/jboss/ejb3/test/webservices/unit/JSR181TestCase.java:38: package org.jboss.ws.tools.wsdl does not exist | [javac] import org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory; | [javac] ^ | [javac] /home/ejort/jboss-head/ejb3/src/test/org/jboss/ejb3/test/jaxws/EndpointEJB.java:39: cannot find symbol | [javac] symbol: class PortComponent | [javac] @PortComponent(contextRoot = "/jaxws-context", urlPattern = "/*") | [javac] ^ | [javac] /home/ejort/jboss-head/ejb3/src/test/org/jboss/ejb3/test/webservices/jsr181/EJB3Bean.java:38: cannot find symbol | [javac] symbol: class PortComponent | [javac] @PortComponent(contextRoot="/jsr181", urlPattern="/*") | [javac] ^ | [javac] /home/ejort/jboss-head/ejb3/src/test/org/jboss/ejb3/test/dd/web/servlets/SubjectFilter.java:76: warning: [deprecation] getActiveSubject() in org.jboss.security.AuthenticationManager has been deprecated | [javac] Subject s0 = mgr.getActiveSubject(); | [javac] ^ | [javac] /home/ejort/jboss-head/ejb3/src/test/org/jboss/ejb3/test/jaxws/unit/ContextEJBTestCase.java:63: cannot find symbol | [javac] symbol : class WSDLDefinitionsFactory | [javac] location: class org.jboss.ejb3.test.jaxws.unit.ContextEJBTestCase | [javac] WSDLDefinitionsFactory factory = WSDLDefinitionsFactory.newInstance(); | [javac] ^ | [javac] /home/ejort/jboss-head/ejb3/src/test/org/jboss/ejb3/test/jaxws/unit/ContextEJBTestCase.java:63: cannot find symbol | [javac] symbol : variable WSDLDefinitionsFactory | [javac] location: class org.jboss.ejb3.test.jaxws.unit.ContextEJBTestCase | [javac] WSDLDefinitionsFactory factory = WSDLDefinitionsFactory.newInstance(); | [javac] ^ | [javac] /home/ejort/jboss-head/ejb3/src/test/org/jboss/ejb3/test/jaxws/unit/ContextEJBTestCase.java:64: cannot find symbol | [javac] symbol : class WSDLDefinitions | [javac] location: class org.jboss.ejb3.test.jaxws.unit.ContextEJBTestCase | [javac] WSDLDefinitions wsdlDefinitions = factory.parse(wsdlURL); | [javac] ^ | [javac] /home/ejort/jboss-head/ejb3/src/test/org/jboss/ejb3/test/standalone/unit/StandardTestCase.java:167: warning: non-varargs call of varargs method with inexact argument type for last parameter; | [javac] cast to java.lang.Object for a varargs call | [javac] cast to java.lang.Object[] for a non-varargs call and to suppress this warning | [javac] Object testCase = constructor.newInstance(constructorParams); | [javac] ^ | [javac] /home/ejort/jboss-head/ejb3/src/test/org/jboss/ejb3/test/standalone/unit/StandardTestCase.java:192: warning: non-varargs call of varargs method with inexact argument type for last parameter; | [javac] cast to java.lang.Object for a varargs call | [javac] cast to java.lang.Object[] for a non-varargs call and to suppress this warning | [javac] Object testCase = constructor.newInstance(constructorParams); | [javac] ^ | [javac] /home/ejort/jboss-head/ejb3/src/test/org/jboss/ejb3/test/webservices/unit/JSR181TestCase.java:106: cannot find symbol | [javac] symbol : class WSDLDefinitionsFactory | [javac] location: class org.jboss.ejb3.test.webservices.unit.JSR181TestCase | [javac] WSDLDefinitionsFactory factory = WSDLDefinitionsFactory.newInstance(); | [javac] ^ | [javac] /home/ejort/jboss-head/ejb3/src/test/org/jboss/ejb3/test/webservices/unit/JSR181TestCase.java:106: cannot find symbol | [javac] symbol : variable WSDLDefinitionsFactory | [javac] location: class org.jboss.ejb3.test.webservices.unit.JSR181TestCase | [javac] WSDLDefinitionsFactory factory = WSDLDefinitionsFactory.newInstance(); | [javac] ^ | [javac] /home/ejort/jboss-head/ejb3/src/test/org/jboss/ejb3/test/webservices/unit/JSR181TestCase.java:107: cannot find symbol | [javac] symbol : class WSDLDefinitions | [javac] location: class org.jboss.ejb3.test.webservices.unit.JSR181TestCase | [javac] WSDLDefinitions wsdlDefinitions = factory.parse(wsdlURL); | [javac] ^ | [javac] Note: Some input files use unchecked or unsafe operations. | [javac] Note: Recompile with -Xlint:unchecked for details. | [javac] 15 errors | [javac] 4 warnings | | BUILD FAILED | /home/ejort/jboss-head/ejb3/build-test.xml:347: Compile failed; see the compiler error output for details. | What is it with the webservices team that they can't resist refactoring code and consequentially continually breaking the JBossAS build? :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4005293#4005293 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4005293

19 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: serializable KernelDeployment

by adrian＠jboss.org

"alesj" wrote : | So if our returned MetaData is non-Serializable, we should throw exception (since we want all our MD to be serializable, right?)? | Correct. This is a candidate for AbstractTestCase in the jboss-test project. | /** | * Check we have the expected type | * | * @param <T> the expected type | * @param o the object | * @param expectedType the excepted class of the exception | * @return the expected type | */ | protected <T> T assertInstanceOf(Object o, Class<T> expectedType) | { | return assertInstanceOf(o, expectedType, true); | } | | /** | * Check we have the expected type | * | * @param <T> the expected type | * @param o the object | * @param expectedType the excepted class of the exception | * @param allowNull whether the object can be null | * @return the expected type | */ | protected <T> T assertInstanceOf(Object o, Class<T> expectedType, boolean allowNull) | { | if (expectedType == null) | fail("Null expectedType"); | | if (o == null && allowNull) | return null; | | try | { | return expected.cast(o); | } | catch (ClassCastException e) | { | fail("Object " + o + " of class " + o.getClass().getName() + " is not an instanceof " + expectedType.getName()); | } | } | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4005260#4005260 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4005260

19 years, 2 months

1
0
0 / 0

[Design of JBoss Portal] - Re: LayouStrategy and StrategyResponse API

by radzish

Hi Julien! Yesterday I evaluated your first version of solution and it worked for me! :) Thank you very much for that. Today I will try annother way you posted, but it will take more time for me because since now I have to build my jboss portal from sources (previous example was just compiled to jar and put to jboss portal's lib). Anyway, I believe it will work. So, once more, thank you very much. I really appreciate your help! This is the best support I have ever had! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4005246#4005246 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4005246

19 years, 2 months

1
0
0 / 0

[Design of POJO Server] - Re: DataSource/ServiceXSLDeployer processing issue

by adrian＠jboss.org

COMPONENTS This is very much a prototype. When I wrote this it was just to get something working and express the idea. Like I said before, this needs revisiting and doing properly. But what I will say is that components are an implementation detail. The profile service should not be interested in the components directly, it is not going to touch their attachments. The components that get constructed from a particular metadata model can change from release to release. The only part the profile service needs to know about these is the context names. i.e. what are the MBean/POJO names so it can map missing dependencies back to the original deployment that caused them. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4005244#4005244 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4005244

19 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: serializable KernelDeployment

by alesj

serialize method in AbstractTestCase class only takes Serializable as parameter. So if our returned MetaData is non-Serializable, we should throw exception (since we want all our MD to be serializable, right?)? ps: this thread was hijacked with property replacement :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4005243#4005243 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4005243

19 years, 2 months

1
0
0 / 0

[Design of POJO Server] - Re: DataSource/ServiceXSLDeployer processing issue

by adrian＠jboss.org

RUNTIME MODE AND PREDETERMINED ATTACHMENTS The parsing deployers are still invoked for these. But they should be written in such a way that if there is a predetermined attachment they don't do the parsing. They still might do other work after the parse! There are complications like the XSL deployer which needs to be changed so you can pass in some form of DOM representation as the predetermined attachment and still do the XSL transform on it, but this is an exceptional case caused by badly written deployers that don't have a proper metadata model. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4005242#4005242 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4005242

19 years, 2 months

1
0
0 / 0

[Design of POJO Server] - Re: DataSource/ServiceXSLDeployer processing issue

by adrian＠jboss.org

DEPLOYMENT PROTOCOL This is something that is not a part of the original prototype but it is a part of the original design. The basic idea is that the deployers can be run in two modes. 1) Runtime - this is what is implemented, it is the full deployment 2) Profile Service - in this case, the "real deployers" create contexts that have stubbed out actions for the MC and JMX layers. That is when it runs in Profile Service mode, it still goes through the full deployment process, creates all the contexts and tries to resolve dependencies, but it doesn't create any objects or invoke any setters or lifecycle methods. NOTE: This is only for the deployments. It does need to do the full work for the deployers and classloaders otherwise they wouldn't be able to do anything. :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4005241#4005241 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4005241

19 years, 2 months

1
0
0 / 0

[Design of POJO Server] - Re: DataSource/ServiceXSLDeployer processing issue

by adrian＠jboss.org

This seems to be getting very confused? ATTACHMENTS The original design was the following: You have two types of attachment: 1) Transient - these are created by the parsing deployers from the raw xml inside the deployments 2) Predetermined - these are what the profile service (or some other invoker of the deployers) passes in to override what is in the deployment. The Predetermined attachments are a sort of alt-dd but done programmatically. I can see an argument for having a third type of attachment which is internal state related to the deployment but it is stuff that we don't want the profile service/management layer to override. It will always be constructed at runtime. However, this can also be trivially dealt with by the ManagedObjectBuilder NOT creating a ManagedObject for that attachment type. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4005239#4005239 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4005239

19 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Case sensitivity in injecting a bean's property

by adrian＠jboss.org

Ok, so first of all, we need a test for this in system-jmx. The only test for cross injection just uses the object, it does not test accessing a "property" of an MBean. org.jboss.test.system.controller.integration.test.ConfigureMCFromJMXTestCase-mc.xml | <deployment xmlns="urn:jboss:bean-deployer:2.0"> | <bean name="Test" class="org.jboss.test.system.controller.integration.support.SimpleBean"> | <property name="simple"><inject bean="jboss.test:type=test"/></property> | </bean> | </deployment> | Previously, this just treated the MBean like a javabean (i.e. the property name was port) looking directly at the MBean object. But now it has been changed to go through the JMX api (so it needs to use the JMX attribute name Port). Alternatively, we could do as Scott says and try both in ServiceControllerContext | public Object get(String name) throws Throwable | { | try | { | return getMBeanServer().getAttribute(objectName, name); | } | catch (AttributeNotFoundException orignal) | { | try | { | name = switchToUpperOrLowerCase(name); | return getMBeanServer().getAttribute(objectName, name); | } | catch (AttributeNotFoundException e) | { | throw original; | } | } | } | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4005232#4005232 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4005232

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