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

[Design of POJO Server] - Re: Regression in testJmsDestinationComponents

by scott.stark＠jboss.org

Its the destination ServiceAnnotationMetaData that is referring to the annotation generated by AnnotationCreator.createAnnotation, so AnnotationProxy has to be Serializable. That requires another microcontainer release. Still looking into the directory deployment issue as I expect its a vfs deployment issue. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4113856#4113856 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4113856

18 years, 3 months

1
0
0 / 0

[Design of EJB 3.0] - Re: metadata

by scott.stark＠jboss.org

"wolfc" wrote : The only reason is the profile service. It can't handle annotations, so it needs meta data. | This does not make sense. The profile service handles whatever a deployment can have as an attachment. @ReturnNonNull does not sound any different from @TransactionAttribute as a piece of method metadata. There is nothing that precludes a deployment metadata from using annotations if that is the proper metadata view. The point of the metadata project is that one has to be able to define a metadata complete view such that a management tool can have a model to modify without having to write back to deployment descriptors. You'll have to explain why @ReturnNonNull cannot fit into a components metadata model of its methods. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4113847#4113847 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4113847

18 years, 3 months

1
0
0 / 0

[Design of POJO Server] - Regression in testJmsDestinationComponents

by scott.stark＠jboss.org

The ProfileServiceUnitTestCase.testJmsDestinationComponents is broken because there is a disconnect between the profile deployment names and MainDeployer.getManagedDeployment(String name). The messaging destinations are being seen as children of the deploy/messaging/ deployment, and this is not a managable deployment. Some deployment processing logic has changed since this test was last working. if I move the messaging deployments to the deploy directory, the managed objects are created, but they are again referencing non-serializable values. This time its an AnnotationProxy that cannot be marshalled: | java.rmi.MarshalException: Failed to communicate. Problem during marshalling/unmarshalling; nested exception is: | java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException: org.jboss.annotation.factory.AnnotationProxy | at org.jboss.remoting.transport.socket.SocketClientInvoker.handleException(SocketClientInvoker.java:122) | at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:669) | at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122) | at org.jboss.remoting.Client.invoke(Client.java:1634) | at org.jboss.remoting.Client.invoke(Client.java:548) | 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:65) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at AOPProxy$1.getComponentsForType(AOPProxy$1.java) | at org.jboss.test.profileservice.test.ProfileServiceUnitTestCase.testJmsDestinationComponents(ProfileServiceUnitTestCase.java:305) | This looks like it should in fact be Serializable as its just a generic annotation implementation. Not sure what is pulling in the AnnotationProxy at this point. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4113844#4113844 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4113844

18 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: ws-security code

by thomas.diesler＠jboss.com

Ok, I see. Since you are the one that best knows what you need, I suggest you isolate that code base yourself. This would possibly be a good home for it https://svn.jboss.org/repos/jbossws/projects View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4113842#4113842 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4113842

18 years, 3 months

1
0
0 / 0

[Design of EJB 3.0] - Re: metadata

by bdecoste

That's where I'm doing it - you had mentioned that before. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4113839#4113839 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4113839

18 years, 3 months

1
0
0 / 0

[Design of JBoss Build System] - Re: outputDirectory is null (activeByDefault is ignored)

by pgier

Ok, I see what's happening. I added a jboss-deploy profile that is being activated, and this is causing the default profile to not be activated because activeByDefault gets turned off if another profile is activated. I will fix this today. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4113836#4113836 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4113836

18 years, 3 months

1
0
0 / 0

[Design of EJB 3.0] - Re: metadata

by wolfc

The only reason is the profile service. It can't handle annotations, so it needs meta data. Any major refactoring should really be done in projects/ejb3. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4113834#4113834 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4113834

18 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: ws-security code

by anil.saldhana＠jboss.com

Hi Thomas. I am referring to the code that Jason wrote. Is it possible to isolate it into a separate maven build or such? This is because any work on ws-trust/ws-fed etc (if ever) we do at JBoss, will have to extend this functionality. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4113832#4113832 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4113832

18 years, 3 months

1
0
0 / 0

[Design of EJB 3.0] - Re: metadata

by bdecoste

I've started on replacing Ejb3AnnotationHandler and Ejb3DescriptorHandler with Ejb3MetadataHandler. If we stick with creating annotations from the new metadata, we can leave the container.resolveAnnotation() calls everywhere as they are. I take it from the last comments that the new metadata lacks the ability to recognize and model unexpected annotations (e.g. @ReturnNonNull). I am starting to wonder what the value of the metadata project is exactly if we go this route - if they are parsing all the annotations and xml, creating an object model, and we are taking that object model and turning it back into annotations, how is this better than what we have now? Sounds considerably slower in fact. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4113826#4113826 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4113826

18 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Contents of the SOAP request

by jpechane＠redhat.com

Hi, thanks for your answers. I have done fast and dirty solution | // Generate the SOAP xml | StringWriter messageString = new StringWriter(); | List<Handler> handlerChain = bindingProvider.getBinding().getHandlerChain(); | handlerChain.add(new org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerClient()); | handlerChain.add(new TestHandler(messageString)); | bindingProvider.getBinding().setHandlerChain(handlerChain); | UserType userType = new UserType(); | userType.setMsg(TEST_MESSAGE); | UserType retObj = hello.echoUserType(userType); | | // Actually call the WS | bindingProvider.getBinding().setHandlerChain(new ArrayList<Handler>()); | ((StubExt) hello).setSecurityConfig("jboss-wsse-client.xml"); | ((StubExt) hello).setConfigName("Standard WSSecurity Client"); | retObj = hello.echoUserType(userType); | This approach worked albeit it is really crude View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4113817#4113817 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4113817

18 years, 3 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 December 2007