August 2010 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-6603) cannot create ws and client at once using WTP wizard

by Lukas Jungmann (JIRA)

cannot create ws and client at once using WTP wizard ---------------------------------------------------- Key: JBIDE-6603 URL: https://jira.jboss.org/browse/JBIDE-6603 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.2.0.M1 Reporter: Lukas Jungmann Assignee: Brian Fitzpatrick -create a new dynamic web project -create a new java class with some dummy method there and annotate it with @WebService -invoke WTP Web Service wizard: in the wizard: -set service slider to "Start Service", server runtime to JBoss EAP, ws runtime to JBossWS -set client slider to "Start Client", server runtime to JBoss EAP, ws runtime to JBossWS -finish the wizard => Actual: error popup saying: 'Selection must be WSDL.' appears when client project creation is about to start Expected: no error is shown and service and client are started -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

3
17
0 / 0

[JBoss JIRA] Created: (JBIDE-6390) Cannot create ws from wsdl on JBoss 6M3

by Lukas Jungmann (JIRA)

Cannot create ws from wsdl on JBoss 6M3 --------------------------------------- Key: JBIDE-6390 URL: https://jira.jboss.org/browse/JBIDE-6390 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.2.next Environment: jbdevstudio-eap-linux-gtk-4.0.0.v201005280223N-H334-M1, jboss-6.0.0.20100429-M3/ Reporter: Lukas Jungmann Assignee: Brian Fitzpatrick -create a dynamic web project with JBoss6M3 runtime and use server supplied JBossWS -create a top-down service from http://www.ecubicle.net/iptocountry.asmx?wsdl => Error: Could not import. (use --verbose to see full traces)Error: com/sun/xml/ws/policy/sourcemodel/wspolicy/NamespaceVersion this works fine if JBoss 5.x server runtime is used This looks like a problem in JBossWS included in JBoss6M3 since on the command line it says the same: jlukas@lukas-laptop:/tmp/aaa$ java -version java version "1.6.0_20" Java(TM) SE Runtime Environment (build 1.6.0_20-b02) Java HotSpot(TM) Server VM (build 16.3-b01, mixed mode) jlukas@lukas-laptop:/tmp/aaa$ /space/java/servers/jboss-6.0.0.20100429-M3/bin/wsconsume.sh -k --verbose http://www.ecubicle.net/iptocountry.asmx?wsdl parsing WSDL... Error: Could not import. (use --verbose to see full traces) java.lang.NoClassDefFoundError: com/sun/xml/ws/policy/sourcemodel/wspolicy/NamespaceVersion at com.sun.tools.ws.wsdl.parser.PolicyExtensionHandler.getNamespaceURI(PolicyExtensionHandler.java:57) at com.sun.tools.ws.wsdl.parser.WSDLParser.register(WSDLParser.java:131) at com.sun.tools.ws.wsdl.parser.WSDLParser.<init>(WSDLParser.java:123) at com.sun.tools.ws.processor.modeler.wsdl.WSDLModeler.buildModel(WSDLModeler.java:109) at com.sun.tools.ws.wscompile.WsimportTool.run(WsimportTool.java:185) at org.jboss.ws.tools.jaxws.impl.SunRIConsumerImpl.consume(SunRIConsumerImpl.java:246) at org.jboss.wsf.spi.tools.cmd.WSConsume.importServices(WSConsume.java:240) at org.jboss.wsf.spi.tools.cmd.WSConsume.main(WSConsume.java:86) Caused by: java.lang.ClassNotFoundException: com.sun.xml.ws.policy.sourcemodel.wspolicy.NamespaceVersion at java.net.URLClassLoader$1.run(URLClassLoader.java:202) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:190) at java.lang.ClassLoader.loadClass(ClassLoader.java:307) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) at java.lang.ClassLoader.loadClass(ClassLoader.java:248) ... 8 more jlukas@lukas-laptop:/tmp/aaa$ Where should I file corresponting issue? To JBAS or JBWS project? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

2
5
0 / 0

[JBoss JIRA] Created: (JBDS-1301) Aggregate Drools-IDE upstream build in JBDS instead of rebuilding it

by Nick Boldt (JIRA)

Aggregate Drools-IDE upstream build in JBDS instead of rebuilding it -------------------------------------------------------------------- Key: JBDS-1301 URL: https://jira.jboss.org/browse/JBDS-1301 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: Build Affects Versions: 4.0.0.Beta1 Reporter: Nick Boldt Assignee: Nick Boldt Currently we build drools-ide component as a combination of binaries fetched from maven repo, binaries fetched up upstream maven/pde build, and sources in SVN. However, since there is now a Tycho-based Hudson job for Drools-IDE which accomplishes the above hybrid build, we should aggregate that job's output into JBDS instead of rebuilding it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-2850) Run JUnit tests for relevant Seam Distributions

by Denis Golovin (JIRA)

Run JUnit tests for relevant Seam Distributions ------------------------------------------------ Key: JBIDE-2850 URL: https://jira.jboss.org/jira/browse/JBIDE-2850 Project: Tools (JBoss Tools) Issue Type: Task Components: Build/Releng Affects Versions: 3.0.0.alpha Reporter: Denis Golovin Assignee: Denis Golovin Priority: Blocker Fix For: 3.0.0.beta1 1.2.1.GA with path, 2.0.2.SP1, 1.2.1.GA with patch from JB EAP, 2.0.0 fp form JB EAP and 2.1.0.CR1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

2
19
0 / 0

[JBoss JIRA] Created: (JBIDE-6613) Can't create ODE Deployment Descriptor

by Jeff DeLong (JIRA)

Can't create ODE Deployment Descriptor -------------------------------------- Key: JBIDE-6613 URL: https://jira.jboss.org/browse/JBIDE-6613 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.1.1 Environment: Mac Eclipse 3.5SR2, JB Tools 3.1.1 Reporter: Jeff DeLong When attempting to create a new Apache ODE Deployment Descriptor I see the following when I hit the Finish button: Popup error box with red exclamation mark and an OK button. With the same process definition in Eclipse 3.6 / JB Tools 3.2, the bpel-deploy file is created, but only one Partner Link in the Inbound Interfaces and one Partner Link in the Outbound interfaces can be easily edited. To edit the other Partner Links I had to click around the Associated Port entry ( -- none -- ) several times before I could get it to edit. I then copied the bpel-deploy.xml file back to the Eclipse 3.5 / JB Tools workspace, and attempted to open the file in the BPEL Editor. It would not open (although the file looks fine). I then deployed the process using the Servers -> Full Publish and it deployed successfully and I was able to start a process instance. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

4
21
0 / 0

[JBoss JIRA] Created: (JBIDE-6386) OpenOn for injection point should work on field's/parameter's type declaration

by Daniel Azarov (JIRA)

OpenOn for injection point should work on field's/parameter's type declaration ------------------------------------------------------------------------------ Key: JBIDE-6386 URL: https://jira.jboss.org/browse/JBIDE-6386 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: cdi (jsr-299) Reporter: Daniel Azarov Assignee: Daniel Azarov Fix For: 3.2.next -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

3
4
0 / 0

[JBoss JIRA] Created: (JBDS-1303) Include Usage component in JBDS build

by Denis Golovin (JIRA)

Include Usage component in JBDS build ------------------------------------- Key: JBDS-1303 URL: https://jira.jboss.org/browse/JBDS-1303 Project: Developer Studio (JBoss Developer Studio) Issue Type: Task Reporter: Denis Golovin -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

5
15
0 / 0

[JBoss JIRA] Created: (JBIDE-6351) Tools Core: org.hibernate.cfg.reveng.JDBCReader processTables() should support mixed-case names for TableTypes

by Michael Walker (JIRA)

Tools Core: org.hibernate.cfg.reveng.JDBCReader processTables() should support mixed-case names for TableTypes -------------------------------------------------------------------------------------------------------------- Key: JBIDE-6351 URL: https://jira.jboss.org/browse/JBIDE-6351 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Hibernate Affects Versions: 3.1.0.GA Reporter: Michael Walker Assignee: Max Rydahl Andersen Attachments: JDBCReader.java A particular database (MetaMatrix/JBoss Enterprise Data Services Platform) returns mixed-case values from the JDBC call DatabaseMetadata.getTableTypes(), specifically: "Table", "View". However, line 539 of org.hibernate.cfg.reveng.JDBCReader expects these values to always be upper-case: if ( ("TABLE".equals(tableType) || "VIEW".equals(tableType) ... Upper-case values are typically expected here (see http://java.sun.com/j2se/1.4.2/docs/api/java/sql/DatabaseMetaData.html#ge...), but not required per the JDBC specification AFAIK. Changing this logic to match on case-insensitive names allows Hibernate Tools to successfully work with MetaMatrix. For example: if ( ("TABLE".equalsIgnoreCase(tableType) || "VIEW".equalsIgnoreCase(tableType) /*|| "SYNONYM".equals(tableType) */) ) { //|| See the forum thread for more info. I'll attach example code that was used to rebuild hibernate-tools.jar successfully, which contains only the change described above, in case it is useful. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

4
11
0 / 0

[JBoss JIRA] Created: (JBIDE-5109) Allow regular jboss servers to use remote deployment as well (instead of just SSH Server)

by Rob Stryker (JIRA)

Allow regular jboss servers to use remote deployment as well (instead of just SSH Server) ----------------------------------------------------------------------------------------- Key: JBIDE-5109 URL: https://jira.jboss.org/jira/browse/JBIDE-5109 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS Affects Versions: 3.1.0.M3 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.1.0.CR1 5) Expand this logic to be accessible from standard JBoss server types. See JBIDE-5048 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

4
7
0 / 0

[JBoss JIRA] Created: (JBIDE-6634) Validate dependencies for injection point

by Pete Muir (JIRA)

Validate dependencies for injection point ----------------------------------------- Key: JBIDE-6634 URL: https://jira.jboss.org/browse/JBIDE-6634 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: cdi (jsr-299) Reporter: Pete Muir Assignee: Max Rydahl Andersen For example, if an injection point is defined, but there is nothing to inject, a warning should be raised (see unsatisfied resolution in the spec). Also, if multiple beans resolve to an injection point, a warning should be raised (see ambiguous resolution in the spec) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

5
8
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 August 2010