June 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-14763) GateIn 3.6 goes to stacks.yaml

by Peter Palaga (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14763?page=com.atlassian.jira.plugi... ] Peter Palaga commented on JBIDE-14763: -------------------------------------- Hi Rob, there is no such patch to stacks.yaml yet as I am busy with other things. I'll let you know when it is ready. > GateIn 3.6 goes to stacks.yaml > ------------------------------ > > Key: JBIDE-14763 > URL: https://issues.jboss.org/browse/JBIDE-14763 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, server > Reporter: Peter Palaga > Assignee: Rob Stryker > Priority: Blocker > > It should be checked which consequences will it have for JBoss Tools if GateIn 3.6 appears in {{stacks.yaml}}. Filling this as recommended by [~maxandersen]. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14763) GateIn 3.6 goes to stacks.yaml

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14763?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-14763: ------------------------------------- Is there any proposed patch to stacks.yaml or topic branch for me to test? > GateIn 3.6 goes to stacks.yaml > ------------------------------ > > Key: JBIDE-14763 > URL: https://issues.jboss.org/browse/JBIDE-14763 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, server > Reporter: Peter Palaga > Assignee: Rob Stryker > Priority: Blocker > > It should be checked which consequences will it have for JBoss Tools if GateIn 3.6 appears in {{stacks.yaml}}. Filling this as recommended by [~maxandersen]. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14546) Could not import maven project when creating jbossews apps (WATCHER ISSUE)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14546?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBIDE-14546: ------------------------------------------------- Dan McPherson <dmcphers(a)redhat.com> changed the Status of [bug 965591|https://bugzilla.redhat.com/show_bug.cgi?id=965591] from VERIFIED to CLOSED > Could not import maven project when creating jbossews apps (WATCHER ISSUE) > -------------------------------------------------------------------------- > > Key: JBIDE-14546 > URL: https://issues.jboss.org/browse/JBIDE-14546 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Alpha2 > Environment: JBDS 7.0.0 Alpha2 > int.openshift.redhat.com(devenv_3250) > Reporter: jing zh > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.1.0.Beta2 > > Attachments: import-fails-null.png, jboss-ews2.png, jbossews_JBT.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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-337) Review: Devs to review Forge Tools chapter for JBDS 7.0.

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-337?page=com.atlassian.jira.plug... ] Michelle Murray resolved TOOLSDOC-337. -------------------------------------- Resolution: Done Marking JIRA as done as all info received and incorporated into doc. > Review: Devs to review Forge Tools chapter for JBDS 7.0. > -------------------------------------------------------- > > Key: TOOLSDOC-337 > URL: https://issues.jboss.org/browse/TOOLSDOC-337 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Security Level: Public(Everyone can see) > Components: User Guide - Forge Tools > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.1.0 > > Attachments: UserGuide_Forge.pdf > > > Please review the content of the Forge Tools chapter from a technical viewpoint: > 1) Are features correctly documented? > 2) Are there any features that are missing? > Screenshots are currently missing and will be added closer to GA. > For ease of tracking by docs, please give feedback as comments in this JIRA. > The chapter is available here as a pdf. The pdf has some layout issues so please disregard these and only comment on the technical content. > Alternatively, the complete user guide to date is also available form: > * http://documentation-devel.engineering.redhat.com/docs/en-US/JBoss_Develo... > * https://github.com/jbosstools/jbosstools-documentation/tree/master/docs/J... (build with: mvn compile) -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14292) Link under 'Other resources' on JBoss Central is incorrect for JBDS

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14292?page=com.atlassian.jira.plugi... ] Michelle Murray edited comment on JBIDE-14292 at 6/10/13 11:15 PM: ------------------------------------------------------------------- Reopening JIRA as new JBDS link verified so task can now be completed. was (Author: mmurray): New JBDS link verified so task can now be completed. > Link under 'Other resources' on JBoss Central is incorrect for JBDS > ------------------------------------------------------------------- > > Key: JBIDE-14292 > URL: https://issues.jboss.org/browse/JBIDE-14292 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.0.Alpha2 > Reporter: Michelle Murray > Assignee: Fred Bricon > Fix For: 4.1.0.Beta2 > > > I realise that JBoss Central is still under development but I wanted to point out an issue. Under 'Other resources' there is a link titled 'Product documentation' that links to http://docs.jboss.org/tools/latest/. > 1. Is this the right link for community docs? /tools/latest will store documentation under development for the next release. Should this link point to the community docs for the version of JBT installed (for example, tools/4.1.0 for JBT 4.1.0)? There is ongoing debate about what exactly the link will be - see TOOLSDOC-310. > 2. This link does not point to the right place for JBDS users. JBDS documentation is stored here: https://access.redhat.com/site/documentation/JBoss_Developer_Studio/ So how can the issue of two separate documentation locations for JBT and JBDS be got around? -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14292) Link under 'Other resources' on JBoss Central is incorrect for JBDS

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14292?page=com.atlassian.jira.plugi... ] Michelle Murray commented on JBIDE-14292: ----------------------------------------- [~fbricon], the product name change is now in effect for documentation. The JBDS link for central is https://access.redhat.com/site/documentation/Red_Hat_JBoss_Developer_Studio/ > Link under 'Other resources' on JBoss Central is incorrect for JBDS > ------------------------------------------------------------------- > > Key: JBIDE-14292 > URL: https://issues.jboss.org/browse/JBIDE-14292 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.0.Alpha2 > Reporter: Michelle Murray > Assignee: Fred Bricon > Fix For: 4.1.0.Beta2 > > > I realise that JBoss Central is still under development but I wanted to point out an issue. Under 'Other resources' there is a link titled 'Product documentation' that links to http://docs.jboss.org/tools/latest/. > 1. Is this the right link for community docs? /tools/latest will store documentation under development for the next release. Should this link point to the community docs for the version of JBT installed (for example, tools/4.1.0 for JBT 4.1.0)? There is ongoing debate about what exactly the link will be - see TOOLSDOC-310. > 2. This link does not point to the right place for JBDS users. JBDS documentation is stored here: https://access.redhat.com/site/documentation/JBoss_Developer_Studio/ So how can the issue of two separate documentation locations for JBT and JBDS be got around? -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14804) Uninstall from jboss central

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14804?page=com.atlassian.jira.plugi... ] Michelle Murray commented on JBIDE-14804: ----------------------------------------- +1, I was thinking exactly the same thing. After installing something, I was then thinking 'right, now how do I uninstall it?' Including uninstall would be great. > Uninstall from jboss central > ---------------------------- > > Key: JBIDE-14804 > URL: https://issues.jboss.org/browse/JBIDE-14804 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Max Rydahl Andersen > > since I can install from central, shouldn't we also provide an uninstall button for our connectors? -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-359) Delete old guides from git

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-359?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-359: ------------------------------------------ Thanks [~nickboldt]. I think it is all pretty much as you said. Regards Jenkins jobs, as I see it: * Not sure how often 4.0 will need to be rebuilt. The docs are so flawed that I am just leaving them alone. But having a jenkins job won't do any harm for the eventuality that something does need fixing or someone else is wanting to take on the job of fixing (as in TOOLSDOC-316). * Will need a job for developing docs (from master). As soon as 4.1 is released then this branch will be developing towards 4.2. * Once 4.1 is released and branch 4.1 created, will need a job for this so we can fix bugs in docs and applying changes that I didn't get time for prior to GA. Creating the 4.1.x branch should coincide with GA rather than be done in advance, since as far as I can see docs doesn't need stabilized docs for Betas and leaving until GA negates the need to apply changes to master and 4.1 branch continually. > Delete old guides from git > -------------------------- > > Key: TOOLSDOC-359 > URL: https://issues.jboss.org/browse/TOOLSDOC-359 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Security Level: Public(Everyone can see) > Components: General documentation issues > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > > 4.1.x onwards docs: https://github.com/jbosstools/jbosstools-documentation/tree/master/docs > 4.0.x & prior docs: https://github.com/jbosstools/jbosstools-documentation/tree/master/guides > The older guides are also located in 4.0.x branch. > 1. I propose deleting the guides dir in master branch to avoid future confusion about which docs are current. > 2. Removing the guides dir from master will break https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-docs-nigh.... > * In short term can probably solve this easily by redirecting the jenkins job to the 4.0x branch. > * In long term, need to revise jenkins job to only build the JBT user guide https://github.com/jbosstools/jbosstools-documentation/tree/master/docs/J.... -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14739) Generated JBoss WS SOAP message is invalid

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14739?page=com.atlassian.jira.plugi... ] Alessio Soldano commented on JBIDE-14739: ----------------------------------------- I believe I've fixed this in WISE-202. Will cut a 2.0.2.Final release soon. > Generated JBoss WS SOAP message is invalid > ------------------------------------------ > > Key: JBIDE-14739 > URL: https://issues.jboss.org/browse/JBIDE-14739 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Webservices > Affects Versions: 4.1.0.Beta1 > Reporter: Jaroslav Jankovič > Assignee: Brian Fitzpatrick > Fix For: 4.1.0.Beta2 > > > STEP: create dynamic web project and register web.xml (to be able to create simple soap web service) > STEP: create simple web service (File -> New -> Other -> JBoss Tools -> Simple Web Service with default settings > STEP: run a server, deploy a project > STEP: open Web Service Tester, enter url of web service and try to invoke its default method (sayHello) > STEP: open the generated web service class (HelloWorld.java) > STEP: add a new web method like this: > {code} > @WebMethod() > public String echo() { > return "Hello World"; > } > {code} redeploy the project > STEP: open web service tester again, url should be still set on text box, so click on the "Get from WSDL" > STEP: in opened dialog, choose the new method "echo", and press OK > ASSERT: generated request message has valid format > {code} > <?xml version="1.0" encoding="UTF-8" standalone="no"?> > <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> > <soap:Header/> > <soap:Body> > <ns2:echo xmlns:ns2="http://webservices.samples.jboss.org/"/> > </soap:Body> > </soap:Envelope> > {code} > ASSERT: invoking the generated message tends to valid response > FAIL: generated request message has invalid format > {code} > <?xml version="1.0" encoding="utf-8" standalone="yes" ?> > <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" > > <soap:Header> > </soap:Header> > <soap:Body> > </soap:Body> > </soap:Envelope> > {code} > FAIL: invoking the message throws a SOAPFaultException: > {code} > java.lang.Exception: javax.xml.ws.soap.SOAPFaultException: Fault occurred while processing. > at org.jboss.tools.ws.ui.utils.JAXWSTester2.doTest(JAXWSTester2.java:205) > at org.jboss.tools.ws.ui.views.JAXRSWSTestView2.handleWSTest(JAXRSWSTestView2.java:1823) > at org.jboss.tools.ws.ui.views.JAXRSWSTestView2.access$34(JAXRSWSTestView2.java:1809) > at org.jboss.tools.ws.ui.views.JAXRSWSTestView2$21.run(JAXRSWSTestView2.java:1726) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) > Caused by: javax.xml.ws.soap.SOAPFaultException: Fault occurred while processing. > at com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:178) > at com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:111) > at com.sun.xml.internal.ws.client.dispatch.DispatchImpl$DispatchAsyncInvoker$1.onCompletion(DispatchImpl.java:450) > at com.sun.xml.internal.ws.client.Stub$1.onCompletion(Stub.java:381) > at com.sun.xml.internal.ws.api.pipe.Fiber.completionCheck(Fiber.java:502) > at com.sun.xml.internal.ws.api.pipe.Fiber.run(Fiber.java:420) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:722) > {code} > This issue occurs only the first time. After the first try, other tries are successful in words of SOAP message generation. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14709) Error in server log when redeploying datasource

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14709?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-14709: ----------------------------------- Fix Version/s: LATER (was: 4.1.x) > Error in server log when redeploying datasource > ------------------------------------------------ > > Key: JBIDE-14709 > URL: https://issues.jboss.org/browse/JBIDE-14709 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Seam 2, upstream > Affects Versions: 4.1.0.Beta1 > Environment: JBDS 7.0.0.Beta1, EAP 6.1.0.GA > Reporter: Tomas Remes > Assignee: Alexey Kazakov > Fix For: LATER > > > I am not sure, if this problem is related to JBT, but is best reproducible by this way. Steps to reproduce: > 1. Create and run EAP 6.1.0 server > 2. Create Seam Web Project (I used MySQL datasource) > 3. Try to edit newly created datasource file in the project and save it. > 4. Redeploy is triggered. > 5. However the datasource is redeployed, notice the following exception in the server.log: > {noformat} > 11:07:34,057 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.naming.context.java.testProjectEntityManagerFactory: org.jboss.msc.service.StartException in service jboss.naming.context.java.testProjectEntityManagerFactory: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17] > Caused by: org.jboss.msc.inject.InjectionException: Value already set for this injector > at org.jboss.msc.inject.RetainingInjector.inject(RetainingInjector.java:50) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] > at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler$1.inject(PersistenceUnitServiceHandler.java:386) > at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler$1.inject(PersistenceUnitServiceHandler.java:382) > at org.jboss.msc.inject.CastingInjector.inject(CastingInjector.java:55) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] > at org.jboss.msc.service.ServiceControllerImpl.doInject(ServiceControllerImpl.java:1549) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] > at org.jboss.msc.service.ServiceControllerImpl.access$1900(ServiceControllerImpl.java:49) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.performInjections(ServiceControllerImpl.java:1780) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1741) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] > ... 3 more > {noformat} -- 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

12 years, 10 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 June 2013