October 2007 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-1852) Failed to create a new SAX parser

by Thomas Diesler (JIRA)

Failed to create a new SAX parser --------------------------------- Key: JBWS-1852 URL: http://jira.jboss.com/jira/browse/JBWS-1852 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assigned To: Thomas Diesler Fix For: jbossws-2.0.2 org.jboss.xb.binding.JBossXBRuntimeException: Failed to create a new SAX parser at org.jboss.xb.binding.UnmarshallerFactory$UnmarshallerFactoryImpl.newUnmarshaller(UnmarshallerFactory.java:100) at org.jboss.ws.metadata.config.JBossWSConfigFactory.parse(JBossWSConfigFactory.java:76) at org.jboss.ws.metadata.config.JBossWSConfigFactory.getConfig(JBossWSConfigFactory.java:134) at org.jboss.ws.metadata.umdm.EndpointMetaData.initEndpointConfig(EndpointMetaData.java:704) at org.jboss.ws.metadata.umdm.EndpointMetaData.setConfigNameInternal(EndpointMetaData.java:695) at org.jboss.ws.metadata.umdm.EndpointMetaData.setConfigName(EndpointMetaData.java:679) at org.jboss.ws.metadata.builder.jaxws.JAXWSServerMetaDataBuilder.processEndpointConfig(JAXWSServerMetaDataBuilder.java:76) at org.jboss.ws.metadata.builder.jaxws.JAXWSWebServiceMetaDataBuilder.buildWebServiceMetaData(JAXWSWebServiceMetaDataBuilder.java:137) at org.jboss.ws.tools.jaxws.impl.JBossWSProviderImpl.provide(JBossWSProviderImpl.java:108) at org.jboss.ws.tools.jaxws.impl.JBossWSProviderImpl.provide(JBossWSProviderImpl.java:124) at org.jboss.wsf.spi.tools.ant.WSProvideTask.executeNonForked(WSProvideTask.java:221) at org.jboss.wsf.spi.tools.ant.WSProvideTask.execute(WSProvideTask.java:237) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275) at org.apache.tools.ant.Task.perform(Task.java:364) at org.apache.tools.ant.Target.execute(Target.java:341) at org.apache.tools.ant.Target.performTasks(Target.java:369) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216) at org.apache.tools.ant.Project.executeTarget(Project.java:1185) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40) at org.apache.tools.ant.Project.executeTargets(Project.java:1068) at org.apache.tools.ant.Main.runBuild(Main.java:668) at org.apache.tools.ant.Main.startAnt(Main.java:187) at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246) at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67) Caused by: org.jboss.xb.binding.JBossXBException: Failed to create a new SAX parser at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.<init>(SaxJBossXBParser.java:101) at org.jboss.xb.binding.UnmarshallerImpl.<init>(UnmarshallerImpl.java:55) at org.jboss.xb.binding.UnmarshallerFactory$UnmarshallerFactoryImpl.newUnmarshaller(UnmarshallerFactory.java:96) ... 23 more Caused by: java.lang.UnsupportedOperationException: This parser does not support specification "null" version "null" at javax.xml.parsers.SAXParser.isXIncludeAware(SAXParser.java:511) at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.<init>(SaxJBossXBParser.java:93) ... 25 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 2 months

2
8
0 / 0

[JBoss JIRA] Created: (JBWS-1873) WSDL to Java - Incorrect case of generated type for anonymous type.

by Darran Lofthouse (JIRA)

WSDL to Java - Incorrect case of generated type for anonymous type. ------------------------------------------------------------------- Key: JBWS-1873 URL: http://jira.jboss.com/jira/browse/JBWS-1873 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: tools-jaxrpc Affects Versions: jbossws-2.0.1 Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Fix For: jbossws-2.0.3 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-1870) Improve JAX-WS User Guide about how to secure an endpoint

by Alessio Soldano (JIRA)

Improve JAX-WS User Guide about how to secure an endpoint --------------------------------------------------------- Key: JBWS-1870 URL: http://jira.jboss.com/jira/browse/JBWS-1870 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: productivity Reporter: Alessio Soldano While the legacy JAX-RPC user guide features a "Secure Endpoints", the JAX-WS User Guide only shows the @WebContext and @SecurityContext annotations without any further explanation. Perhaps this might be included in the future productivity documentation enhancements we are thinking about. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-1468) Fix @Resource WebServiceContext for jbossas-4.2

by Thomas Diesler (JIRA)

Fix @Resource WebServiceContext for jbossas-4.2 ----------------------------------------------- Key: JBWS-1468 URL: http://jira.jboss.com/jira/browse/JBWS-1468 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jaxws Reporter: Thomas Diesler Assigned To: Thomas Diesler Priority: Critical Fix For: jbossws-1.2.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 2 months

3
5
0 / 0

[JBoss JIRA] Commented: (JBWS-1841) WebServiceRef injection from DD doesn't work

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1841?page=comments#action_12384119 ] Thomas Diesler commented on JBWS-1841: -------------------------------------- In information exposed by jbossws should be the same as in AS5.0 where these tests are not excluded i.e they pass # EJB3/Injection excludes org/jboss/test/ws/jaxws/samples/webserviceref/** org/jboss/test/ws/jaxws/webserviceref/** > WebServiceRef injection from DD doesn't work > -------------------------------------------- > > Key: JBWS-1841 > URL: http://jira.jboss.com/jira/browse/JBWS-1841 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: jbossws-2.0.1 > Reporter: Carlo de Wolf > Assigned To: Thomas Diesler > Fix For: jbossws-2.0.3 > > > Specifying a service-ref in ejb-jar.xml like this doesn't work. > <?xml version="1.0" encoding="UTF-8"?> > <ejb-jar > xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://java.sun.com/xml/ns/javaee > http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd" > version="3.0"> > <description>jBoss test application </description> > <display-name>Test</display-name> > <enterprise-beans> > <session> > <ejb-name>StatelessBean</ejb-name> > <service-ref> > <service-ref-name>service/Endpoint3</service-ref-name> > <service-interface>org.jboss.ejb3.test.webservices.jsr181.EndpointInterface</service-interface> > <mapped-name>jbossws-client/service/TestService</mapped-name> > <injection-target> > <injection-target-class>org.jboss.ejb3.test.webservices.jsr181.StatelessBean</injection-target-class> > <injection-target-name>endpoint3</injection-target-name> > </injection-target> > </service-ref> > </session> > </enterprise-beans> > </ejb-jar> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1855) Different endpoints share the same metrics

by Alessio Soldano (JIRA)

Different endpoints share the same metrics ------------------------------------------ Key: JBWS-1855 URL: http://jira.jboss.com/jira/browse/JBWS-1855 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: productivity Affects Versions: jbossws-2.0.0 Environment: 4.2.0.GA Jboss App server, JBossWS 2.0.0.GA Reporter: Alessio Soldano Assigned To: Alessio Soldano Different endpoints seem to share the metrics. See http://www.jboss.com/index.html?module=bb&op=viewtopic&t=120732 . -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 2 months

1
1
0 / 0

[JBoss JIRA] Commented: (JBWS-926) JBoss to JBoss binary optimiztion

by Levi Purvis (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-926?page=comments#action_12383940 ] Levi Purvis commented on JBWS-926: ---------------------------------- Consider just supporting XML Fast InfoSet as your binary optimization. It will then still interoperate with other servers (Sun, Microsoft) and still be highly optimized. My tests with Sun's JAXB/JAXWS stack shows that using Fast InfoSet performed very close to RMI (with out taking any effort to optimize). Why reinvent the wheel when you can use a standard with a quality parser / serializer that is already available? The Fast InfoSet API conforms to the three standard XML API's, so it should be easy to plug in. https://fi.dev.java.net/ > JBoss to JBoss binary optimiztion > --------------------------------- > > Key: JBWS-926 > URL: http://jira.jboss.com/jira/browse/JBWS-926 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-jaxws > Reporter: Thomas Diesler > Fix For: jbossws-2.1.1 > > > With WS the client and server are fundamentally disconnected and exchange XML documents that are valid in the context of the abstract contract defined in WSDL. Having said that, client/server implementations might not care about the abstract contract as long as there are no handlers involved that work on the SAAJ/DOM API. Currently all transport concerns are delegated to jboss-remoting. It would therefore be possible to implement a binary transfer of the SOAPMessage that is linked to a remoting protocol other than HTTP. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1842) JAXB based ServiceRef meta data

by Thomas Diesler (JIRA)

JAXB based ServiceRef meta data ------------------------------- Key: JBWS-1842 URL: http://jira.jboss.com/jira/browse/JBWS-1842 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-jaxrpc, jbossws-jaxws Reporter: Thomas Diesler Assigned To: Thomas Diesler Fix For: jbossws-2.0.2 It looks like the only integration point for creation of a ObjectModelFactory based impl that hands off to a ServiceRefHandler impl from the ws spi. Can we get the ws spi to provide a jaxb annotated element ala this from the metadata project instead? Code: package org.jboss.metadata.javaee.spec; import javax.xml.bind.annotation.XmlElement; import javax.xml.bind.annotation.XmlType; import javax.xml.namespace.QName; import org.jboss.metadata.javaee.support.ResourceInjectionMetaDataWithDescriptionGroup; /** * ServiceReferenceMetaData. * * @author <a href="adrian(a)jboss.com">Adrian Brock</a> * @version $Revision: 1.1 $ */ @XmlType(name="service-refType") public class ServiceReferenceMetaData extends ResourceInjectionMetaDataWithDescriptionGroup { /** The serialVersionUID */ private static final long serialVersionUID = 5693673588576610322L; /** The service interface */ private String serviceInterface; /** The service reference type */ private String serviceRefType; /** The wsdl file */ private String wsdlFile; /** The jaxrpc mapping file */ private String jaxrpcMappingFile; /** The service qname */ private QName serviceQname; /** The handlers */ private ServiceReferenceHandlersMetaData handlers; /** The handler chains */ private ServiceReferenceHandlerChainsMetaData handlerChains; /** * Create a new ServiceReferenceMetaData. */ public ServiceReferenceMetaData() { // For serialization } /** * Get the serviceRefName. * * @return the serviceRefName. */ public String getServiceRefName() { return getName(); } /** * Set the serviceRefName. * * @param serviceRefName the serviceRefName. * @throws IllegalArgumentException for a null serviceRefName */ public void setServiceRefName(String serviceRefName) { setName(serviceRefName); } /** * Get the jaxrpcMappingFile. * * @return the jaxrpcMappingFile. */ public String getJaxrpcMappingFile() { return jaxrpcMappingFile; } /** * Set the jaxrpcMappingFile. * * @param jaxrpcMappingFile the jaxrpcMappingFile. * @throws IllegalArgumentException for a null jaxrpcMappingFile */ public void setJaxrpcMappingFile(String jaxrpcMappingFile) { if (jaxrpcMappingFile == null) throw new IllegalArgumentException("Null jaxrpcMappingFile"); this.jaxrpcMappingFile = jaxrpcMappingFile; } /** * Get the serviceInterface. * * @return the serviceInterface. */ public String getServiceInterface() { return serviceInterface; } /** * Set the serviceInterface. * * @param serviceInterface the serviceInterface. * @throws IllegalArgumentException for a null serviceInterface */ public void setServiceInterface(String serviceInterface) { if (serviceInterface == null) throw new IllegalArgumentException("Null serviceInterface"); this.serviceInterface = serviceInterface; } /** * Get the serviceQname. * * @return the serviceQname. */ public QName getServiceQname() { return serviceQname; } /** * Set the serviceQname. * * @param serviceQname the serviceQname. * @throws IllegalArgumentException for a null serviceQname */ public void setServiceQname(QName serviceQname) { if (serviceQname == null) throw new IllegalArgumentException("Null serviceQname"); this.serviceQname = serviceQname; } /** * Get the serviceRefType. * * @return the serviceRefType. */ public String getServiceRefType() { return serviceRefType; } /** * Set the serviceRefType. * * @param serviceRefType the serviceRefType. * @throws IllegalArgumentException for a null serviceRefType */ //@SchemaProperty(mandatory=false) @XmlElement(required=false) public void setServiceRefType(String serviceRefType) { if (serviceRefType == null) throw new IllegalArgumentException("Null serviceRefType"); this.serviceRefType = serviceRefType; } /** * Get the wsdlFile. * * @return the wsdlFile. */ public String getWsdlFile() { return wsdlFile; } /** * Set the wsdlFile. * * @param wsdlFile the wsdlFile. * @throws IllegalArgumentException for a null wsdlFile */ public void setWsdlFile(String wsdlFile) { if (wsdlFile == null) throw new IllegalArgumentException("Null wsdlFile"); this.wsdlFile = wsdlFile; } /** * Get the handlers. * * @return the handlers. */ public ServiceReferenceHandlersMetaData getHandlers() { return handlers; } /** * Set the handlers. * * @param handlers the handlers. * @throws IllegalArgumentException for a null handlers */ @XmlElement(name="handler") public void setHandlers(ServiceReferenceHandlersMetaData handlers) { if (handlers == null) throw new IllegalArgumentException("Null handlers"); this.handlers = handlers; } /** * Get the handlerChains. * * @return the handlerChains. */ public ServiceReferenceHandlerChainsMetaData getHandlerChains() { return handlerChains; } /** * Set the handlerChains. * * @param handlerChains the handlerChains. * @throws IllegalArgumentException for a null handlerChains */ //@SchemaProperty(mandatory=false) @XmlElement(required=false) public void setHandlerChains(ServiceReferenceHandlerChainsMetaData handlerChains) { if (handlerChains == null) throw new IllegalArgumentException("Null handlerChains"); this.handlerChains = handlerChains; } } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 2 months

1
4
0 / 0

[JBoss JIRA] Commented: (JBWS-925) Add support for FastInfoset

by Alexander Philippou (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-925?page=comments#action_12383398 ] Alexander Philippou commented on JBWS-925: ------------------------------------------ Fast Infoset can also be used on .NET as a message encoding for WCF-based Web Services. If you are not convinced yet, check out the size comparisons at http://www.noemax.com/products/fastinfoset/size_comparisons.html. The point is that you can get a good reduction of message size without processing performance penalties. Fast Infoset is also used as a stateful message encoding in the new SOAP/TCP transport, which is already available for GlassFish and WCF. > Add support for FastInfoset > --------------------------- > > Key: JBWS-925 > URL: http://jira.jboss.com/jira/browse/JBWS-925 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-jaxws > Reporter: Thomas Diesler > Fix For: jbossws-2.1.1 > > > A standard way of doing binary WS is FastInfoset > http://java.sun.com/developer/technicalArticles/xml/fastinfoset/ > The Fast Infoset standard draft (currently being developed as joint work by ISO/IEC JTC 1 and ITU-T) specifies a binary format for XML infosets that is an efficient alternative to XML. An instance of this binary format is called a fast infoset document. Fast infoset documents are analogous to XML documents. Each has a physical form and an XML infoset. Fast infoset documents are, given the results presented, faster to serialize and parse, and smaller in size, than the equivalent XML documents. Thus, fast infoset documents may be used whenever the size and processing time of XML documents is an issue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBWS-925) Add support for FastInfoset

by Justin Bertram (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-925?page=comments#action_12383338 ] Justin Bertram commented on JBWS-925: ------------------------------------- The referenced document (http://java.sun.com/developer/technicalArticles/xml/fastinfoset/) is over four years old. Since the time it was published several of your open source competitors have integrated Fast Infoset into their stacks. This includes Apache's Axis2 (http://wso2.org/library/2686) which is used by Geronimo (http://geronimo.apache.org/) and Jonas (http://jonas.objectweb.org/). It also includes Sun's reference implementation of JAX-WS (https://jax-ws.dev.java.net/) which is the basis of the Metro Web Service Stack (https://metro.dev.java.net/) used by Glassfish (https://glassfish.dev.java.net/). I don't know anything about commercial vendors, but I assume coverage is good there as well. The reason I bring this up is because I am endeavoring to write the highest performing web service possible with open source software. Right now, we have standardized on JBoss, but the benefits of Fast Infoset look large enough that they might justify changing application servers. Is there any possibility Fast Infoset could be integrated into the 2.0.x codebase rather than the 2.1.x codebase? > Add support for FastInfoset > --------------------------- > > Key: JBWS-925 > URL: http://jira.jboss.com/jira/browse/JBWS-925 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-jaxws > Reporter: Thomas Diesler > Fix For: jbossws-2.1.1 > > > A standard way of doing binary WS is FastInfoset > http://java.sun.com/developer/technicalArticles/xml/fastinfoset/ > The Fast Infoset standard draft (currently being developed as joint work by ISO/IEC JTC 1 and ITU-T) specifies a binary format for XML infosets that is an efficient alternative to XML. An instance of this binary format is called a fast infoset document. Fast infoset documents are analogous to XML documents. Each has a physical form and an XML infoset. Fast infoset documents are, given the results presented, faster to serialize and parse, and smaller in size, than the equivalent XML documents. Thus, fast infoset documents may be used whenever the size and processing time of XML documents is an issue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 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-issues October 2007