January 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2450) No Error reported when WS Client code generation fails

by Mustafa Musaji (JIRA)

[ https://issues.jboss.org/browse/JBDS-2450?page=com.atlassian.jira.plugin.... ] Mustafa Musaji updated JBDS-2450: --------------------------------- Attachment: echoService.wsdl I'm attaching a sample WSDL to reproduce this issue with. It contains the following <xs:element name='DUPLICATESTRING' type='xs:string'/> <xs:element name='DUPLICATE_STRING' type='xs:string'/> JAXB by default removes "_" (underscores) and thus the names cause a collision when generating client stubs. This isn't picked up if you have WSDL validation turned on because it's valid XML. > No Error reported when WS Client code generation fails > ------------------------------------------------------ > > Key: JBDS-2450 > URL: https://issues.jboss.org/browse/JBDS-2450 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Error Reporting > Affects Versions: 6.0.0.GA > Reporter: Mustafa Musaji > Labels: web_service_client > Attachments: echoService.wsdl > > > If you have a WSDL which would normally fail because of JAXB collision. From command line you would get an error like this: > Failed to invoke WSDLToJava > org.apache.cxf.tools.common.ToolException: Thrown by JAXB: > Thrown by JAXB: > Two declarations cause a collision in the ObjectFactory class. > ... > However, in JBDS you don't get any error. It just doesn't create any sources and there is no indication of what the issue is. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2450) No Error reported when WS Client code generation fails

by Mustafa Musaji (JIRA)

Mustafa Musaji created JBDS-2450: ------------------------------------ Summary: No Error reported when WS Client code generation fails Key: JBDS-2450 URL: https://issues.jboss.org/browse/JBDS-2450 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: Error Reporting Affects Versions: 6.0.0.GA Reporter: Mustafa Musaji If you have a WSDL which would normally fail because of JAXB collision. From command line you would get an error like this: Failed to invoke WSDLToJava org.apache.cxf.tools.common.ToolException: Thrown by JAXB: Thrown by JAXB: Two declarations cause a collision in the ObjectFactory class. ... However, in JBDS you don't get any error. It just doesn't create any sources and there is no indication of what the issue is. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12190) enable API Tooling for JBoss Tools components

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12190?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-12190: ---------------------------------------- I made some good progress on this topic. One can now use some mojos to create API reports and enhance bundles with apidescription. See description on https://github.com/mickaelistria/apitooling . It relies on Rob's effort to make API Tools and task less constraining. > enable API Tooling for JBoss Tools components > --------------------------------------------- > > Key: JBIDE-12190 > URL: https://issues.jboss.org/browse/JBIDE-12190 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng > Affects Versions: 4.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.1.0.Alpha1 > > Attachments: JBIDE12190-1.png, JBIDE12190-2.png, JBIDE12190-3.png > > > We should enable API Tooling support in projects so that we can get immediate feedback when someone forgets to upversion their plugins or breaks API. > http://wiki.eclipse.org/Version_Numbering > http://www.eclipse.org/pde/pde-api-tools/ > http://wiki.eclipse.org/PDE/API_Tools/User_Guide > http://www.ibm.com/developerworks/opensource/library/os-eclipse-api-tools > http://grepcode.com/file/repository.grepcode.com/java/eclipse.org/3.7/org... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13316) Improve versioning for TP using standard Maven way (no SNAPSHOT for stable and tags)

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13316?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-13316: ----------------------------------- Summary: Improve versioning for TP using standard Maven way (no SNAPSHOT for stable and tags) (was: Improve versioning for TP using standard Maven way) > Improve versioning for TP using standard Maven way (no SNAPSHOT for stable and tags) > ------------------------------------------------------------------------------------ > > Key: JBIDE-13316 > URL: https://issues.jboss.org/browse/JBIDE-13316 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.1.0.Alpha1 > > > Currently, we deal with explicit versions in folder names that make it confusing to understand how target-platforms are versioned. > Instead, we should use usual Maven way and Git branches: one Git branch for each version of TPs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13386) Create dedicated Git rep for target platforms

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13386?page=com.atlassian.jira.plugi... ] Mickael Istria reassigned JBIDE-13386: -------------------------------------- Assignee: Max Rydahl Andersen (was: Mickael Istria) Assigning to [~maxandersen] since he's the one who can clone repo to jbosstools GitHub account. Repo to clone is https://github.com/nickboldt/jbosstools-target-platforms/ , with all branches and tags. > Create dedicated Git rep for target platforms > --------------------------------------------- > > Key: JBIDE-13386 > URL: https://issues.jboss.org/browse/JBIDE-13386 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform > Reporter: Mickael Istria > Assignee: Max Rydahl Andersen > Fix For: 4.1.0.Alpha1 > > > Since target platforms follow their own schedule, independently of JBT/JBDS and we maintain many streams, it would be more convenient to have them in their own Git repo. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13398) Document AS adapter main architecture

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13398?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-13398: -------------------------------- Attachment: astools api.png > Document AS adapter main architecture > ------------------------------------- > > Key: JBIDE-13398 > URL: https://issues.jboss.org/browse/JBIDE-13398 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: JBossAS/Servers > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Attachments: astools api.gliffy, astools api.png, launch a server.gliffy, launch a server.png, New Server Workflow.gliffy, New Server Workflow.png, runtime workflow.gliffy, runtime workflow.png > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2449) Report a better error when using wrong project type to create WS Client

by Mustafa Musaji (JIRA)

[ https://issues.jboss.org/browse/JBDS-2449?page=com.atlassian.jira.plugin.... ] Mustafa Musaji updated JBDS-2449: --------------------------------- Description: If you try and use a standard Java Project to create WS Client from a WSDL, you get a NPE thrown. But an error stating that the project type expected is a Dynamic Web Project would be much more appropriate. !Screenshot_error.png|thumbnail! was: If you try and use a standard Java Project to create WS Client from a WSDL, you get a NPE thrown. But an error stating that the project type expected is a Dynamic Web Project would be much more appropriate. !Screenshot_error.png! > Report a better error when using wrong project type to create WS Client > ----------------------------------------------------------------------- > > Key: JBDS-2449 > URL: https://issues.jboss.org/browse/JBDS-2449 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Error Reporting > Affects Versions: 6.0.0.GA > Reporter: Mustafa Musaji > Attachments: Screenshot_error.png > > > If you try and use a standard Java Project to create WS Client from a WSDL, you get a NPE thrown. But an error stating that the project type expected is a Dynamic Web Project would be much more appropriate. > !Screenshot_error.png|thumbnail! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13398) Document AS adapter main architecture

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13398?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-13398: -------------------------------- Attachment: astools api.png > Document AS adapter main architecture > ------------------------------------- > > Key: JBIDE-13398 > URL: https://issues.jboss.org/browse/JBIDE-13398 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: JBossAS/Servers > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Attachments: astools api.gliffy, astools api.png, launch a server.gliffy, launch a server.png, New Server Workflow.gliffy, New Server Workflow.png, runtime workflow.gliffy, runtime workflow.png > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2449) Report a better error when using wrong project type to create WS Client

by Mustafa Musaji (JIRA)

[ https://issues.jboss.org/browse/JBDS-2449?page=com.atlassian.jira.plugin.... ] Mustafa Musaji updated JBDS-2449: --------------------------------- Issue Type: Enhancement (was: Bug) > Report a better error when using wrong project type to create WS Client > ----------------------------------------------------------------------- > > Key: JBDS-2449 > URL: https://issues.jboss.org/browse/JBDS-2449 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Error Reporting > Affects Versions: 6.0.0.GA > Reporter: Mustafa Musaji > Attachments: Screenshot_error.png > > > If you try and use a standard Java Project to create WS Client from a WSDL, you get a NPE thrown. But an error stating that the project type expected is a Dynamic Web Project would be much more appropriate. > !Screenshot_error.png|thumbnail! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2449) Report a better error when using wrong project type to create WS Client

by Mustafa Musaji (JIRA)

[ https://issues.jboss.org/browse/JBDS-2449?page=com.atlassian.jira.plugin.... ] Mustafa Musaji updated JBDS-2449: --------------------------------- Description: If you try and use a standard Java Project to create WS Client from a WSDL, you get a NPE thrown. But an error stating that the project type expected is a Dynamic Web Project would be much more appropriate. !Screenshot_error.png! was:If you try and use a standard Java Project to create WS Client from a WSDL, you get a NPE thrown. But an error stating that the project type expected is a Dynamic Web Project would be much more appropriate. > Report a better error when using wrong project type to create WS Client > ----------------------------------------------------------------------- > > Key: JBDS-2449 > URL: https://issues.jboss.org/browse/JBDS-2449 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Error Reporting > Affects Versions: 6.0.0.GA > Reporter: Mustafa Musaji > Attachments: Screenshot_error.png > > > If you try and use a standard Java Project to create WS Client from a WSDL, you get a NPE thrown. But an error stating that the project type expected is a Dynamic Web Project would be much more appropriate. > !Screenshot_error.png! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 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

jbosstools-issues January 2013