June 2008 - jbossws-dev - Jboss List Archives

[Design of JBoss Web Services] - Re: JAXWSClientMetaDataBuilder

by thomas.diesler＠jboss.com

The problem with InputStream is, that it cannot deal with with relative imports. So your wsdl cannot reference other wsdls nor external xsd files. You could also use the wsld4j API directly. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156141#4156141 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156141

17 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - verbose logging issue

by thomas.diesler＠jboss.com

There seems to be a logging issue | 01:18:28,391 INFO [NativeServerConfig] JBoss Web Services - Stack Native Core | 01:18:28,391 INFO [NativeServerConfig] 3.0.2-SNAPSHOT | 01:18:29,127 INFO [BareWSFRuntime] null -> RequestHandlerFactory: org.jboss.wsf.stack.jbws.RequestHandlerFactoryImpl@1f86f75 | 01:18:29,127 INFO [BareWSFRuntime] null -> TransportManagerFactory: org.jboss.wsf.container.jboss50.transport.BareTransportManagerFactory@15daaef | 01:18:29,127 INFO [BareWSFRuntime] WebserviceJSERuntime -> DeploymentAspectManager: WSDeploymentAspectManagerJSE :org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl@4b2d10 | 01:18:29,127 INFO [BareWSFRuntime] WebserviceJSERuntime -> EndpointRegistry: org.jboss.wsf.framework.management.ManagedEndpointRegistry@17b84f9 | 01:18:29,128 INFO [BareWSFRuntime] null -> RequestHandlerFactory: org.jboss.wsf.stack.jbws.RequestHandlerFactoryImpl@1f86f75 | 01:18:29,128 INFO [BareWSFRuntime] null -> DeploymentAspectManager: WSDeploymentAspectManagerEndpointAPI :org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl@572554 | 01:18:29,128 INFO [BareWSFRuntime] null -> EndpointRegistry: org.jboss.wsf.framework.management.ManagedEndpointRegistry@17b84f9 | 01:18:29,128 INFO [BareWSFRuntime] null -> TransportManagerFactory: org.jboss.wsf.container.jboss50.transport.BareTransportManagerFactory@153ccbe | 01:18:29,129 INFO [BareWSFRuntime] null -> DeploymentAspectManager: WSDeploymentAspectManagerEJB :org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl@a70e3a | 01:18:29,129 INFO [BareWSFRuntime] WebserviceEJBRuntime -> RequestHandlerFactory: org.jboss.wsf.stack.jbws.RequestHandlerFactoryImpl@1f86f75 | 01:18:29,129 INFO [BareWSFRuntime] WebserviceEJBRuntime -> EndpointRegistry: org.jboss.wsf.framework.management.ManagedEndpointRegistry@17b84f9 | 01:18:29,129 INFO [BareWSFRuntime] WebserviceEJBRuntime -> TransportManagerFactory: org.jboss.wsf.container.jboss50.transport.BareTransportManagerFactory@1970646 | 01:18:30,302 INFO [TomcatDeployment] deploy, ctxPath=/jbossws, vfsUrl=jbossws.sar/jbossws-management.war | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156140#4156140 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156140

17 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JAXWSClientMetaDataBuilder

by maeste

Hi Thomas, probably my explanation is too brief and a little bad. My use case has no relation with soap message, so (I think) it has no opportunities to read something from the context. What DNA would basically do, is to read a wsdl from some sources (often from uddi), and store this wsdl in a JCR. Then (potentially at different time), reading it and parse it to extract metadata and store them too in JCR. I think I have to use some wsdl parser to extract these metadatas from the xml. Am I wrong? In fact Alessio seems to be right, I would need just wsdl metadata instead of umdm, so I would have to modify org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory to parse wsdl directly by an InputStream. Am I misunderstanding you? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155645#4155645 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4155645

17 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JAXWSClientMetaDataBuilder

by thomas.diesler＠jboss.com

There is standard access to the generated wsdl via MessageContext.WSDL_DESCRIPTION This is related http://jira.jboss.org/jira/browse/JBWS-2013 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155576#4155576 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4155576

17 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JAXWSClientMetaDataBuilder

by alessio.soldano＠jboss.com

Hi Stefano, my only concern right now is whether the org.jboss.ws.metadata.umdm metadata is really what you want to save in the repository. Those metadata might be too jbossws-native specific. Are the org.jboss.ws.metadata.wsdl metadata enough for you instead? You can easily get them through org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory which of course you might want to extend to use a pre-existing input stream. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155552#4155552 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4155552

17 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: sub-tasks of JBAS-5384

by alex.loubyansky＠jboss.com

Thanks for pointing out what? The error message from the jira issue you created? "JBAS-5388" wrote : Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Missing value for the required attribute strAttr of element {http://org.jboss.test.ws/jbws720/types}getProperty That's exactly why we are having these discussions. Before creating issues and talking about infinite complexity make an effort to read the error message. Next time you are going to be "brave" and show that your code is doing everything right. That's not too much. That's how other guys work. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155504#4155504 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4155504

17 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBMETA-44, ws annotation processing for references

by thomas.diesler＠jboss.com

yes, getAnnotatedElement() should be pointing to the client field View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155103#4155103 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4155103

17 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: sub-tasks of JBAS-5384

by thomas.diesler＠jboss.com

Thanks for pointing that out. Let me see .... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155088#4155088 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4155088

17 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: sub-tasks of JBAS-5384

by alex.loubyansky＠jboss.com

Or maybe you have an inval test. The schema says the strAttr attribute is required but in the test its value is null. Hence, the error. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155046#4155046 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4155046

17 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - JAXWSClientMetaDataBuilder

by maeste

Hi folks, long time since my last post here ;) How are you? I'm fine, and I'm now involved t some level in JBoss DNA development. There we need to parse wsdls to extract metadata and store them in a JSR-170 repository to analyse and query them: http://jira.jboss.org/jira/browse/DNA-33 I took a look to org.jboss.ws.metadata.builder.jaxws.JAXWSClientMetaDataBuilder in native stack, and it seems to do all I need. I have just a trouble with it since it use a URL pointing to wsdl location which is passed to ServiceMetaData and finally to WSDLDefinitionsFactory where you open an InputStream of this URL. Well I have an InputStream directly from JCR and I would ask if you can see some problem adding a set of methods working directly with inputStream, adding them at current classes. Of course, if you agree, I can manage myself the task opening a Jira Issue and committing changes on a branch. Do you have any problem with this idea? Am I wrong in some part? thanks a lot View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155031#4155031 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4155031

17 years, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-dev June 2008