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

[Design of JBoss Web Services] - Re: JBWS-1858 + JBWS-1797: when to generate wsdl?

by richard.opalka＠jboss.com

"alessio.soldano(a)jboss.com" wrote : | Thus according to me the main point here is not moving the wsdl generation later, it's instead reading the servlet context-params earlier, during the deployment. Of course we could do both the changes, but having those params available (for example as properties in the DeploymentInfo) before the UMDM is generated would be enough (and is required before the EndpointLifeCycleDeploymentAspect is run). | What do you think about this? Hi Alessio, this is the cite from JBWS-1799 (Thomas investigation about this issue): In AS42 the servlet context params are not exposed through the AS WebMetaData and are hence not available when during deploy time the wsdl is generated. For these containers and maybe generally it needs to be investigated whether we can generate the wsdl at Endpoint.start(). At that point the config-name has been corrected in ServerEndpointMetaData according to this you should first investigate whether you are able to access context parameters during the deployment phase (using JBossAS deployment metadata objects). If it is doable, you will have no problems ;-) Richard View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4113296#4113296 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4113296

18 years, 3 months

1
0
0 / 0

[Design of JBoss Build System] - Re: NPE unless clean done first

by pgier

Usually the only time I see things like this is if I do an svn update and then a mvn install without cleaning. I'm guessing some of the classes that should be recompiled are not, and a clean usually fixes it. Maybe there is a bug in the compiler plugin that does not correctly determine out of date classes. In your case, maybe one of the tests was removed or renamed? And now surefire can't find something it's looking for? That's all I can think of that could cause an error like that. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4113264#4113264 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4113264

18 years, 3 months

1
0
0 / 0

[Design of JBoss Build System] - Re: assembly manifest entries

by pgier

Ok, just copy and paste the url, because I can't seem to forum post correctly tonight :( http://jira.codehaus.org/browse/MASSEMBLY-121 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4113262#4113262 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4113262

18 years, 3 months

1
0
0 / 0

[Design of POJO Server] - Serialization, NoSuchMethodException in ProfileServiceUnitTe

by scott.stark＠jboss.org

I'm seeing this failure on most of the ProfileServiceUnitTestCase tests currently. Are you seeing these Alexey? | Caused by: java.lang.NoSuchMethodException: class java.lang.ClassLoader.defineClass - [class [Ljava.lang.Object;, int, int] | at org.jboss.reflect.plugins.introspection.ReflectionUtils.findExactMethod(ReflectionUtils.java:240) | at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.readObject(ReflectMethodInfoImpl.java:129) | at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:946) | ... 145 more | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4113261#4113261 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4113261

18 years, 3 months

1
0
0 / 0

[Design of JBoss Build System] - Re: assembly manifest entries

by pgier

Oops, here's a not broken link: http://jira.codehaus.org/browse/MASSEMBLY-121[/url] View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4113260#4113260 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4113260

18 years, 3 months

1
0
0 / 0

[Design of JBoss Build System] - Re: assembly manifest entries

by pgier

It is supposed to work that way, but it's a bug in the current version. It's fixed in the current snapshot (http://jira.codehaus.org/browse/MASSEMBLY-121). If you want, I can copy the source and set up our own copy of the assembly plugin until the fix is released. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4113259#4113259 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4113259

18 years, 3 months

1
0
0 / 0

[Design of POJO Server] - Re: vfs issue?

by scott.stark＠jboss.org

The test should be checking that the war is available based on http requests. The deployment context info is not a sufficient check, and I don't know that it should even be accessible from a remote client in general. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4113249#4113249 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4113249

18 years, 3 months

1
0
0 / 0

[Design of POJO Server] - Re: vfs issue?

by alesj

"alesj" wrote : | What do you mean by 'can be accessed'? | You mean just using assertTrue(isDeployed(topLevelDeployment))? And not pulling the whole DeploymentUnit --> DeploymentContext to the client. Can you check other two examples as well - numberguess and dvd? The last time I remember NumberGuess needed Facelets library to deploy, even though the app itself doesn't use Facelets. I think it was the AnnotationMetaDataDeployer who was picking it up, and requiring some Facelets class. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4113248#4113248 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4113248

18 years, 3 months

1
0
0 / 0

[Design of POJO Server] - Re: vfs issue?

by alesj

"scott.stark(a)jboss.org" wrote : The SeamBookingExampleTestCase is still failing because of how the test is trying to obtain a deployment context. There is no reason for that. The test needs to be validating the deployed war can be accessed. | This is how all other deployers tests were trying to obtain deployment context. Unless this is also obsolete - like most of deployers tests. What do you mean by 'can be accessed'? btw: You mean ear not just war? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4113247#4113247 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4113247

18 years, 3 months

1
0
0 / 0

[Design of POJO Server] - Re: vfs issue?

by scott.stark＠jboss.org

Ok, I have fixed the classpath issue. It was an error in how the lib jars were being checked for META-INF/persistence.xml descriptors that was preventing all jars from being added to the classpath. The SeamBookingExampleTestCase is still failing because of how the test is trying to obtain a deployment context. There is no reason for that. The test needs to be validating the deployed war can be accessed. | java.io.InvalidClassException: org.jboss.deployers.vfs.plugins.structure.AbstractVFSDeploymentContext; unable to create instance | at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1706) | at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305) | at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348) | at org.jboss.deployers.structure.spi.helpers.AbstractDeploymentUnit.readExternal(AbstractDeploymentUnit.java:449) | at org.jboss.deployers.vfs.plugins.structure.AbstractVFSDeploymentUnit.readExternal(AbstractVFSDeploymentUnit.java:126) | at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1755) | at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1717) | at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305) | at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348) | at java.rmi.MarshalledObject.get(MarshalledObject.java:135) | at org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:134) | at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:244) | at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:181) | at org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66) | at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:86) | at org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74) | at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101) | at $Proxy1.invoke(Unknown Source) | at org.jboss.test.deployers.AbstractDeploymentTest.invokeMainDeployer(AbstractDeploymentTest.java:79) | at org.jboss.test.deployers.AbstractDeploymentTest.getDeploymentUnit(AbstractDeploymentTest.java:110) | at org.jboss.test.deployers.AbstractDeploymentTest.assertDeployed(AbstractDeploymentTest.java:85) | at org.jboss.test.deployers.AbstractDeploymentTest.assertDeployed(AbstractDeploymentTest.java:92) | at org.jboss.test.deployers.seam.test.SeamExampleTestCase.testExample(SeamExampleTestCase.java:91) | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4113246#4113246 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4113246

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