October 2010 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-6285) Don't invoke code assist automaticly if user inserts <tag></tag>.

by Alexey Kazakov (JIRA)

Don't invoke code assist automaticly if user inserts <tag></tag>. ----------------------------------------------------------------- Key: JBIDE-6285 URL: https://jira.jboss.org/jira/browse/JBIDE-6285 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: jsp/jsf/xml source editing Affects Versions: 3.1.0.GA Reporter: Alexey Kazakov Assignee: Victor Rubezhny Fix For: 3.2.next If user press Ctrl+Space and insert any tag like: <tag attribute="|" /> then CA invokes automaticly for attribute="|". It's ok. For <tag | /> it's ok too. But for <tag>|</tag> it's not ok. Let's just insert a proposal and if cursor placed between inserted tags then don't invoke CA automaticly again. It's not convinient here because in most cases user will want to press Enter after <tag>| but CA automaticly will insert first proposal in this case. -- 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
5
0 / 0

[JBoss JIRA] Created: (JBIDE-6183) Update Richfaces libs to 3.3.3

by Alexey Kazakov (JIRA)

Update Richfaces libs to 3.3.3 ------------------------------ Key: JBIDE-6183 URL: https://jira.jboss.org/jira/browse/JBIDE-6183 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: common, JSF Affects Versions: 3.1.0.GA Reporter: Alexey Kazakov Assignee: Alexey Kazakov Priority: Critical Fix For: 3.1.1 Current ones are 3.3.2SR1 but 3.3.3 has been announced today - http://in.relation.to/Bloggers/RichFaces333FinalIsReleased -- 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
5
0 / 0

[JBoss JIRA] Created: (JBIDE-6025) gettter-/setter- Methods in ContentAssist

by Diego Ramp (JIRA)

gettter-/setter- Methods in ContentAssist ----------------------------------------- Key: JBIDE-6025 URL: https://jira.jboss.org/jira/browse/JBIDE-6025 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Diego Ramp with fix for https://jira.jboss.org/jira/browse/JBIDE-3378 getter- and setter-methods are available in content-assist. this is not very practically if you never want to see them. should be parametrized or detected on precence of SEAM or when ever you need them -- 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

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-6259) Add an option to Preferences to disable/enable code completion for getteres and setters in EL.

by Alexey Kazakov (JIRA)

Add an option to Preferences to disable/enable code completion for getteres and setters in EL. ---------------------------------------------------------------------------------------------- Key: JBIDE-6259 URL: https://jira.jboss.org/jira/browse/JBIDE-6259 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JSF, jsp/jsf/xml source editing Reporter: Alexey Kazakov Assignee: Victor Rubezhny Fix For: 3.2.next Now we show properties as well as corresponding getters and setters. For example if we have public String name; public String getName(){...} public void setName(String name){...} we suggest #{name|getName()|setName()} Let's add it to preferences and user will be albe to enable getteres setters in CA. I think by defualt it whould be disabled because it's not useful in most cases. EL validator should recognize such methods even if CA for them is disabled. Also if we have some method (not setter or getter) we include two proposals: method, method(). Let's have the only method() in CA. Validator should recognize both. -- 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

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-6700) [tester] details section label names in UI should be consistent

by Lukas Jungmann (JIRA)

[tester] details section label names in UI should be consistent --------------------------------------------------------------- Key: JBIDE-6700 URL: https://jira.jboss.org/browse/JBIDE-6700 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.2.0.M2 Reporter: Lukas Jungmann Assignee: Brian Fitzpatrick Priority: Minor -open a WS tester view => Request Details section label are: "Headers", "Parameters", "Body Text" Response Details section label are: "Response Headers", "Response Body" it would be better to use same labels in both sections, ie: "Request Headers", "Request Parameters", "Request Body" and "Response Headers", "Response Body" or "Headers", "Parameters", "Body Text" and "Headers", "Body Text" -- 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
7
0 / 0

[JBoss JIRA] Created: (JBIDE-7024) Verbose messages in Error log after clean JBT installation

by Jiri Peterka (JIRA)

Verbose messages in Error log after clean JBT installation ---------------------------------------------------------- Key: JBIDE-7024 URL: https://jira.jboss.org/browse/JBIDE-7024 Project: Tools (JBoss Tools) Issue Type: Bug Components: usage Affects Versions: 3.2.0.M2 Environment: JBT 3.2.0.v20100903-2012-H11-M2, Linux 64 Reporter: Jiri Peterka Install and start JBT 3.2.m2 on new workspace See verbose message:(screenshot) ASSERT: Error log should be empty after clean installation -- 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
6
0 / 0

[JBoss JIRA] Created: (JBIDE-6752) [restwizard] provide warning if selected web porject does not have configured runtime

by Lukas Jungmann (JIRA)

[restwizard] provide warning if selected web porject does not have configured runtime ------------------------------------------------------------------------------------- Key: JBIDE-6752 URL: https://jira.jboss.org/browse/JBIDE-6752 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Reporter: Lukas Jungmann Assignee: Brian Fitzpatrick -create some web project and target it to some runtime which does not contain JAX-RS runtime (ie JBoss server 5.1) -invoke and finish the REST service wizard => created project is not buildable we should at least provide a warning if target server does not provide required runtime and/or provide some way for the user so he can configure required stuff from the wizard -- 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
8
0 / 0

[JBoss JIRA] Created: (JBIDE-6495) Generated ws impl class for ws from wsdl should not contain @WebService.name

by Lukas Jungmann (JIRA)

Generated ws impl class for ws from wsdl should not contain @WebService.name ---------------------------------------------------------------------------- Key: JBIDE-6495 URL: https://jira.jboss.org/browse/JBIDE-6495 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.2.0.M1 Reporter: Lukas Jungmann Assignee: Brian Fitzpatrick >From JSR-181, section 3.1: "The implementation bean MAY reference a service endpoint interface by using the @WebService.endpointInterface annotation. If the implementation bean references a service endpoint interface, it MUST implement all the methods on the service endpoint interface. If the implementation bean references a service endpoint interface, that service endpoint interface is used to determine the abstract WSDL contract (portType and bindings). In this case, the service implementation bean MUST NOT include any JSR-181 annotations other than @WebService and @HandlerChain. In addition, the @WebService annotation MUST NOT include the name annotation element. More information on the @WebService.endpointInterface annotation element may be found in 4.1 Annotation: javax.jws.WebService." -- 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
10
0 / 0

[JBoss JIRA] Created: (JBIDE-7106) Implement annotations for JAX-RS in Annotation Properties view

by Brian Fitzpatrick (JIRA)

Implement annotations for JAX-RS in Annotation Properties view -------------------------------------------------------------- Key: JBIDE-7106 URL: https://jira.jboss.org/browse/JBIDE-7106 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Webservices Affects Versions: 3.2.0.Beta Reporter: Brian Fitzpatrick Assignee: Brian Fitzpatrick Fix For: 3.2.0.Beta In a similar pattern to what I did for JBIDE-7055 and JBoss ESB 4.9 annotations, I want to add JAX-RS annotations for RESTful services. -- 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] Closed: (JBIDE-7034) Usage Reporting should report jdk version

by Pavol Srna (JIRA)

[ https://jira.jboss.org/browse/JBIDE-7034?page=com.atlassian.jira.plugin.s... ] Pavol Srna closed JBIDE-7034. ----------------------------- verified on jbosstools-3.2.0.Beta1.aggregate-Update-2010-09-29_23-54-19-H182 > Usage Reporting should report jdk version > ----------------------------------------- > > Key: JBIDE-7034 > URL: https://jira.jboss.org/browse/JBIDE-7034 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: usage > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 3.2.0.Beta1 > > Attachments: screenshot-1.jpg > > > Currently there's no way to gather the jdk version that users use to run JBoss Tools. We shall implement this. -- 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

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 October 2010