November 2006 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-1380) NPE in java2wsdl with no package for SEI

by Thomas Diesler (JIRA)

NPE in java2wsdl with no package for SEI ----------------------------------------- Key: JBWS-1380 URL: http://jira.jboss.com/jira/browse/JBWS-1380 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: wstools Reporter: Thomas Diesler Exception in thread "main" java.lang.NullPointerException at org.jboss.ws.tools.JavaToWSDL.generate(JavaToWSDL.java:303) at org.jboss.ws.tools.helpers.ToolsHelper.handleJavaToWSDLGeneration(ToolsHelper.java:122) at org.jboss.ws.tools.WSTools.process(WSTools.java:132) at org.jboss.ws.tools.WSTools.generate(WSTools.java:120) at org.jboss.ws.tools.WSTools.main(WSTools.java:61) I found the reason behind the Exception. I was not defining the interface in any package. Looks like it is required. So I added package org.myapp; and it started working. -- 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

18 years

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1284) Gracefully handle invalid ImageIO mime types

by Magesh Kumar B (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1284?page=all ] Magesh Kumar B updated JBWS-1284: --------------------------------- Fix Version/s: jbossws-1.0.5 (was: jbossws-1.0.6) I have already completed the coding as part of the patch required by the customer! > Gracefully handle invalid ImageIO mime types > -------------------------------------------- > > Key: JBWS-1284 > URL: http://jira.jboss.com/jira/browse/JBWS-1284 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: binding > Reporter: Jason T. Greene > Assigned To: Magesh Kumar B > Fix For: jbossws-1.0.5 > > > org.jboss.ws.soap.attachment.ImageDataContentHandler.buildFlavors calls ImageIO.getReaderMIMETypes() to determine the list of supported mime types. It has been reported that their are ImagIO plugins in the wild that return invalid mime types. Instead of aborting a warning message should be triggered in this case. -- 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

18 years

1
0
0 / 0

[JBoss JIRA] Commented: (JBWS-1213) Support RESTful web services

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1213?page=comments#action_12347158 ] Thomas Diesler commented on JBWS-1213: -------------------------------------- http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3983940#3983940 "Will Java EE 5 bring REST to Java?": http://blog.noelios.com/2006/05/24/will-java-ee-5-bring-rest-to-java/ > Support RESTful web services > ---------------------------- > > Key: JBWS-1213 > URL: http://jira.jboss.com/jira/browse/JBWS-1213 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jaxws > Reporter: Thomas Diesler > Fix For: jbossws-2.1.0 > > > Blog on howto do this with Sun RI > http://weblogs.java.net/blog/kohlert/archive/2006/01/publishing_a_re.html -- 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

18 years

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1377) Cannot find jaxrpc-mapping for type: {http://www.w3.org/2001/XM

by Thomas Diesler (JIRA)

Cannot find jaxrpc-mapping for type: {http://www.w3.org/2001/XMLSchema}string MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk Cannot find jaxrpc-mapping for type: {http://www.w3.org/2001/XM Cannot find jaxrpc-mapping for type: {http://www.w3.org/2001/XMLSchema}string ---------------------------------------------------------------------------------------------------------------------------------------------- Key: JBWS-1377 URL: http://jira.jboss.com/jira/browse/JBWS-1377 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jaxrpc Reporter: Thomas Diesler Assigned To: Thomas Diesler Fix For: jbossws-1.0.5 -- 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

18 years

1
0
0 / 0

[JBoss JIRA] Commented: (JBWS-1297) Implement JAXB Fault Marshalling

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1297?page=comments#action_12347155 ] Alejandro Guizar commented on JBWS-1297: ---------------------------------------- one-test: [junit] Running org.jboss.test.ws.jaxrpc.samples.exception.ExceptionTestCase [junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 11.328 sec 6 tests had been disabled due to this issue. > Implement JAXB Fault Marshalling > -------------------------------- > > Key: JBWS-1297 > URL: http://jira.jboss.com/jira/browse/JBWS-1297 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jaxws > Reporter: Jason T. Greene > Assigned To: Alejandro Guizar > Fix For: jbossws-2.0.0.CR2 > > > Currently the marshalling layer tries to pass the exception class to JAXB. Instead it needs to pass the fault bean, and then copy the properties to/from the actual exception -- 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

18 years

1
0
0 / 0

[JBoss JIRA] Commented: (JBWS-1297) Implement JAXB Fault Marshalling

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1297?page=comments#action_12347154 ] Alejandro Guizar commented on JBWS-1297: ---------------------------------------- prepare: [echo] ----------------------------------------------- [echo] jboss.home = C:/dev/jboss/trunk/build/output/jboss-5.0.0.Beta [echo] tomcat.home = ${tomcat.home} [echo] java.home = C:\dev\jdk1.5.0_07\jre [echo] ----------------------------------------------- one-test: [junit] Running org.jboss.test.ws.jaxrpc.encoded.marshalltest.MarshallTestCase [junit] FIXME: [JBWS-485] SOAP encoded arrays as bean properties [junit] FIXME: [JBWS-485] SOAP encoded arrays as bean properties [junit] Tests run: 48, Failures: 0, Errors: 0, Time elapsed: 42.125 sec testMyServiceExceptionTest had been disabled due to this issue. > Implement JAXB Fault Marshalling > -------------------------------- > > Key: JBWS-1297 > URL: http://jira.jboss.com/jira/browse/JBWS-1297 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jaxws > Reporter: Jason T. Greene > Assigned To: Alejandro Guizar > Fix For: jbossws-2.0.0.CR2 > > > Currently the marshalling layer tries to pass the exception class to JAXB. Instead it needs to pass the fault bean, and then copy the properties to/from the actual exception -- 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

18 years

1
0
0 / 0

[JBoss JIRA] Commented: (JBWS-807) A handler's handleFault() method is never called.

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-807?page=comments#action_12347144 ] Alejandro Guizar commented on JBWS-807: --------------------------------------- A test in this case had been disabled due to JBWS-1297: prepare: [echo] ----------------------------------------------- [echo] jboss.home = C:/dev/jboss/trunk/build/output/jboss-5.0.0.Beta [echo] tomcat.home = ${tomcat.home} [echo] java.home = C:\dev\jdk1.5.0_07\jre [echo] ----------------------------------------------- one-test: [junit] Running org.jboss.test.ws.jaxrpc.jbws807.JBWS807TestCase [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 11.547 sec Note: the resolution of JBWS-1297 only modified JAX-WS behavior. This test is unaffected by that issue. > A handler's handleFault() method is never called. > ------------------------------------------------- > > Key: JBWS-807 > URL: http://jira.jboss.com/jira/browse/JBWS-807 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jaxrpc > Affects Versions: jbossws-1.0.0.CR4 > Environment: JBoss4.0.4-RC2 > Reporter: Dave Head-Rapson > Assigned To: Heiko Braun > Fix For: jbossws-1.0.0 > > Attachments: JAXRPCServerExceptionHandler.java, standard-jbossws-endpoint-config.xml > > > For a handler deployed under jbossws, the handleFault() method is only called when a known exception is thrown. > That is, for exceptions thrown from behind a web service, that have no jaxrpc mapping, the handleFault() method of web service handlers is never executied. > To replicate: > * I've attached a simple handler class, and the standard-jbossws-endpoint-config.xml file I've been using to set the handler to the chain. > * Compile & install the handler class onto the classpath, then deploy any web service on the server. > * Change the server config so that when it's called it will throw some unexpected runtime exception - perhaps you could remove datasource or some other resource required by the service. > * The call the web service > * The output will contain some debug from the handleRequest() method of the JAXRPCServerExceptionHandler > * The output will not contain any debug messages from the JAXRPCServerExceptionHandler -- 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

18 years

1
0
0 / 0

[JBoss JIRA] Commented: (JBWS-1297) Implement JAXB Fault Marshalling

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1297?page=comments#action_12347134 ] Alejandro Guizar commented on JBWS-1297: ---------------------------------------- one-test: [junit] Running org.jboss.test.ws.jaxws.exception.ExceptionTestCase [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 16.421 sec > Implement JAXB Fault Marshalling > -------------------------------- > > Key: JBWS-1297 > URL: http://jira.jboss.com/jira/browse/JBWS-1297 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jaxws > Reporter: Jason T. Greene > Assigned To: Alejandro Guizar > Fix For: jbossws-2.0.0.CR2 > > > Currently the marshalling layer tries to pass the exception class to JAXB. Instead it needs to pass the fault bean, and then copy the properties to/from the actual exception -- 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

18 years

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1358) JAXWSDeployerJSE has hard-coded relativeOrder

by Scott M Stark (JIRA)

JAXWSDeployerJSE has hard-coded relativeOrder --------------------------------------------- Key: JBWS-1358 URL: http://jira.jboss.com/jira/browse/JBWS-1358 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jaxws Affects Versions: jbossws-2.0.0.CR2 Reporter: Scott M Stark The JAXWSDeployerJSE currently has a hard-coded relative order value: // The default relative order after the JBossWebAppParsingDeployer public int getRelativeOrder() { return PARSER_DEPLOYER + 3; } This needs to be changed to: public JAXWSDeployerJSE() { // Set the default relative order setRelativeOrder(...); } The PARSER_DEPLOYER + 3 as a default is also incorrect, but just allowing the relativeOrder to be externalized is enough for now. -- 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

18 years

3
2
0 / 0

[JBoss JIRA] Updated: (JBWS-1195) jboss-4.0.5.GA (jdk1.4)

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1195?page=all ] Thomas Diesler updated JBWS-1195: --------------------------------- Comment: was deleted > jboss-4.0.5.GA (jdk1.4) > ----------------------- > > Key: JBWS-1195 > URL: http://jira.jboss.com/jira/browse/JBWS-1195 > Project: JBoss Web Services > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: jaxrpc > Reporter: Thomas Diesler > Assigned To: Prabhat Jha > Fix For: jbossws-1.0.4 > > > Run these tests with jdk1.4 > Make sure you have the bouncy castle security provider installed. > http://labs.jboss.com/portal/jbossws/user-guide/en/html/wssecurity.htmltd... > /home/tdiesler/svn/jbossws/branches/jbossws-1.0/src/test > $ ant tests > [PASS] > tdiesler@tdvaio /home/tdiesler/svn/jbossws/branches/jbossws-1.0/output/jbossws-samples-1.0.x.GA > $ ant tests > [PASS] > tdiesler@tdvaio /home/tdiesler/svn/jbossas/tags/JBoss_4_0_5_GA/testsuite > $ ant tests-webservice > [PASS] -- 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

18 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues November 2006