September 2010 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-3971) Add option to transform a POJO into a WebService

by Joao Paulo Viragine (JIRA)

Add option to transform a POJO into a WebService ------------------------------------------------ Key: JBIDE-3971 URL: https://jira.jboss.org/jira/browse/JBIDE-3971 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Webservices Affects Versions: 3.0.0.CR2 Environment: JBDS 2.0.0.CR2 Reporter: Joao Paulo Viragine Priority: Minor It would be nice if we could add WebServices annotations to an existing POJO (as we have the option to add Hibernate/JPA annotations to an existing POJO) A wizard could expose the methods in the POJO, so we could choose which methods will be exposed as a "WebMethod". Further, JBDS could update the web.xml to map the class as a Servlet. -- 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

6
14
0 / 0

[JBoss JIRA] Created: (JBIDE-7173) Support for <literal> in Docbook preview

by Pete Muir (JIRA)

Support for <literal> in Docbook preview ---------------------------------------- Key: JBIDE-7173 URL: https://jira.jboss.org/browse/JBIDE-7173 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Visual Page Editor Templates Affects Versions: 3.2.0.M2 Reporter: Pete Muir Assignee: Maxim Areshkau Support <literal> -- http://www.docbook.org/tdg/en/html/literal.html -- typically formatted as a fixed-width element similar to <code> -- 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
3
0 / 0

[JBoss JIRA] Created: (JBIDE-6257) Remove Wizards wich dublicate WTP wizards

by Maxim Areshkau (JIRA)

Remove Wizards wich dublicate WTP wizards ----------------------------------------- Key: JBIDE-6257 URL: https://jira.jboss.org/jira/browse/JBIDE-6257 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: jsp/jsf/xml source editing Reporter: Maxim Areshkau Assignee: Maxim Areshkau Fix For: 3.2.next Remove Wizards wich dublicate WTP wizards. For example WTP provide dublicate wizard and we provide such wizard too. So it's duplicated. -- 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

6
19
0 / 0

[JBoss JIRA] Created: (JBIDE-6353) Changing SoapAction in Process service WSDL causes BPEL Validator to report an error

by Jeff DeLong (JIRA)

Changing SoapAction in Process service WSDL causes BPEL Validator to report an error ------------------------------------------------------------------------------------ Key: JBIDE-6353 URL: https://jira.jboss.org/browse/JBIDE-6353 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: bpm Environment: latest JB Tools Nightly Build on Mac Reporter: Jeff DeLong Changing SoapAction value in Process service WSDL causes BPEL Validator to report an error. Description Resource Path Location Type <bpel:receive> activity "ReceivePolicyQuoteRequest" specifies a portType "orchws:PolicyQuoteProcessServicePortType", yet this portType does not match the portType derived from "myRole" of partnerLink "PolicyQuoteProcessService" defined in WSDL "platform:/resource/PolicyQuoteProcessService/bpelContent/PolicyQuoteProcessService.wsdl" PolicyQuoteProcess.bpel /PolicyQuoteProcessService/bpelContent line 61 BPEL Validation Marker Description Resource Path Location Type variable "PolicyQuoteRequest" of type "<wsdl:message "PolicyQuoteProcessServiceReq">" is not compatible with WSDL message "<wsdl:message "PolicyQuoteProcessServiceReq">". PolicyQuoteProcess.bpel /PolicyQuoteProcessService/bpelContent line 61 BPEL Validation Marker Rebuilding the project does not make the error go away. The BPEL Validator appears to be too sensitive to changes in the WSDL. The SoapAction is not relevant to the BPEL process definition, changing it should not cause errors. In particular, the PortType did not change (the binding changed). -- 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
7
0 / 0

[JBoss JIRA] Created: (JBIDE-7103) Open EmployeesEdit.xhtml with VPE and click some item -> "Error initializing facelet registry entry" exception

by Vitali Yemialyanchyk (JIRA)

Open EmployeesEdit.xhtml with VPE and click some item -> "Error initializing facelet registry entry" exception -------------------------------------------------------------------------------------------------------------- Key: JBIDE-7103 URL: https://jira.jboss.org/browse/JBIDE-7103 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.2.0.M2 Reporter: Vitali Yemialyanchyk Assignee: Alexey Kazakov java.io.FileNotFoundException: D:\Bin\jbdevstudio_4.0_M2\eclipse\META-INF\facelet-taglib_1_0.dtd (The system cannot find the path specified) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.<init>(Unknown Source) at org.eclipse.emf.ecore.resource.impl.FileURIHandlerImpl.createInputStream(FileURIHandlerImpl.java:105) at org.eclipse.emf.ecore.resource.impl.ExtensibleURIConverterImpl.createInputStream(ExtensibleURIConverterImpl.java:301) at org.eclipse.emf.ecore.xmi.impl.XMLHandler.resolveEntity(XMLHandler.java:810) at com.sun.org.apache.xerces.internal.util.EntityResolverWrapper.resolveEntity(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.resolveEntityAsPerStax(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$DTDDriver.dispatch(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$DTDDriver.next(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Unknown Source) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at javax.xml.parsers.SAXParser.parse(Unknown Source) at org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl.java:181) at org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doLoad(XMLResourceImpl.java:180) at org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(ResourceImpl.java:1494) at org.eclipse.jst.jsf.facelet.core.internal.registry.taglib.TagModelLoader.loadFromInputStream(TagModelLoader.java:100) at org.eclipse.jst.jsf.facelet.core.internal.registry.taglib.JarFileFaceletTaglibLocator.processJar(JarFileFaceletTaglibLocator.java:237) at org.eclipse.jst.jsf.facelet.core.internal.registry.taglib.JarFileFaceletTaglibLocator.start(JarFileFaceletTaglibLocator.java:126) at org.eclipse.jst.jsf.facelet.core.internal.registry.taglib.JarFileFaceletTaglibLocator.start(JarFileFaceletTaglibLocator.java:1) at org.eclipse.jst.jsf.facelet.core.internal.registry.taglib.ProjectTaglibDescriptor$1.run(ProjectTaglibDescriptor.java:82) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.jst.jsf.facelet.core.internal.registry.taglib.ProjectTaglibDescriptor.initialize(ProjectTaglibDescriptor.java:71) at org.eclipse.jst.jsf.facelet.core.internal.registry.taglib.ProjectTaglibDescriptor.getTagLibraries(ProjectTaglibDescriptor.java:117) at org.eclipse.jst.jsf.facelet.core.internal.registry.FaceletTagRegistry.initialize(FaceletTagRegistry.java:155) at org.eclipse.jst.jsf.facelet.core.internal.registry.FaceletTagRegistry.getAllTagLibraries(FaceletTagRegistry.java:110) at org.eclipse.jst.jsf.facelet.core.internal.registry.FaceletTagRegistry.getTagLibrary(FaceletTagRegistry.java:201) at org.eclipse.jst.jsf.facelet.core.internal.cm.FaceletDocumentFactory.getOrCreateCMDocument(FaceletDocumentFactory.java:160) at org.eclipse.jst.jsf.facelet.core.internal.cm.FaceletDocumentFactory.createCMDocumentForContext(FaceletDocumentFactory.java:56) at org.eclipse.jst.jsf.facelet.core.internal.cm.FaceletDocumentFactory.createCMElementDeclaration(FaceletDocumentFactory.java:78) at org.eclipse.jst.jsf.facelet.ui.internal.hover.FaceletHover$MyHTMLTagInfoHoverProcessor.getCMElementDeclaration(FaceletHover.java:132) at org.eclipse.wst.xml.ui.internal.taginfo.XMLTagInfoHoverProcessor.computeTagAttValueHelp(XMLTagInfoHoverProcessor.java:131) at org.eclipse.wst.xml.ui.internal.taginfo.XMLTagInfoHoverProcessor.computeRegionHelp(XMLTagInfoHoverProcessor.java:111) at org.eclipse.wst.xml.ui.internal.taginfo.XMLTagInfoHoverProcessor.computeHoverHelp(XMLTagInfoHoverProcessor.java:86) at org.eclipse.wst.xml.ui.internal.taginfo.XMLTagInfoHoverProcessor.getHoverInfo(XMLTagInfoHoverProcessor.java:257) at org.eclipse.jst.jsf.facelet.ui.internal.hover.FaceletHover.getHoverInfo(FaceletHover.java:58) at org.jboss.tools.jst.jsp.jspeditor.info.ChainTextHover.getHoverInfo(ChainTextHover.java:121) at org.eclipse.jface.text.TextViewerHoverManager$4.run(TextViewerHoverManager.java:168) -- 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
12
0 / 0

[JBoss JIRA] Created: (JBIDE-3875) Provide content assist for faset@name attribute based on parent JSF tag metadata

by Denis Golovin (JIRA)

Provide content assist for faset@name attribute based on parent JSF tag metadata -------------------------------------------------------------------------------- Key: JBIDE-3875 URL: https://jira.jboss.org/jira/browse/JBIDE-3875 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JSF Affects Versions: 3.0.0.GA Reporter: Denis Golovin Assignee: Alexey Kazakov Fix For: 3.1.0 -- 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
19
0 / 0

[JBoss JIRA] Created: (JBIDE-7001) "Set Seam properties" quick fix should not appear on every seam error markers

by Daniel Azarov (JIRA)

"Set Seam properties" quick fix should not appear on every seam error markers ----------------------------------------------------------------------------- Key: JBIDE-7001 URL: https://jira.jboss.org/browse/JBIDE-7001 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.2.0.M2 Reporter: Daniel Azarov Assignee: Daniel Azarov Fix For: 3.2.0.Beta It should appear only on error markers related with wrong setting of seam properties to offer to correct them -- 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
2
0 / 0

[JBoss JIRA] Created: (JBIDE-4064) Quick Fix for Seam validation problems.

by Alexey Kazakov (JIRA)

Quick Fix for Seam validation problems. --------------------------------------- Key: JBIDE-4064 URL: https://jira.jboss.org/jira/browse/JBIDE-4064 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Seam Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.1.0 -- 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
10
0 / 0

[JBoss JIRA] Created: (JBIDE-6877) Quick Fix for "Only component class can have @Create/@Unwrap/@Observer method" error markers

by Daniel Azarov (JIRA)

Quick Fix for "Only component class can have @Create/@Unwrap/@Observer method" error markers -------------------------------------------------------------------------------------------- Key: JBIDE-6877 URL: https://jira.jboss.org/browse/JBIDE-6877 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Seam Affects Versions: 3.2.0.M2 Reporter: Daniel Azarov Assignee: Daniel Azarov Fix For: 3.2.x We can do two quick fixes here 1. Quick Fix which offers to add @Name annotation to class 2. Quick Fix which offers to delete @Create/@Unwrap/@Observer annotation from method -- 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
5
0 / 0

[JBoss JIRA] Created: (JBIDE-7178) Not all AMIs displayed

by Pete Muir (JIRA)

Not all AMIs displayed ---------------------- Key: JBIDE-7178 URL: https://jira.jboss.org/browse/JBIDE-7178 Project: Tools (JBoss Tools) Issue Type: Bug Components: deltacloud, Help Reporter: Pete Muir I'm trying to start an EC2 instance using the JBT Deltacloud tooling, but the AMI I want doesn't appear in the list. It also doesn't appear in http://localhost:3001/api/images unless I restrict it by owner - so I guess deltacloud has some limit that means it doesn't show all 5000ish instances I can start. Any ideas on how to make it appear in the list? e.g. can I make deltacloud display more? or can I make JBDS filter on owner id? or can I make AWS return fewer images? -- 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
3
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 September 2010