November 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-16028) Update Forge Embedded Runtime to 1.4.3.Final

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16028?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-16028: ------------------------------- Labels: respin-a (was: ) > Update Forge Embedded Runtime to 1.4.3.Final > -------------------------------------------- > > Key: JBIDE-16028 > URL: https://issues.jboss.org/browse/JBIDE-16028 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Affects Versions: 4.1.1.CR1 > Reporter: Pavol Srna > Assignee: Koen Aers > Labels: respin-a > Fix For: 4.1.1.CR1 > > -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15859) Update Forge Embedded Runtime to 1.4.2.Final

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15859?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-15859. ------------------------------ Verified in JBT 4.1.1.CR1 build. > Update Forge Embedded Runtime to 1.4.2.Final > -------------------------------------------- > > Key: JBIDE-15859 > URL: https://issues.jboss.org/browse/JBIDE-15859 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Affects Versions: 4.1.1.Beta1 > Reporter: Pavol Srna > Assignee: Koen Aers > Priority: Blocker > Fix For: 4.1.1.CR1 > > -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16028) Update Forge Embedded Runtime to 1.4.3.Final

by Pavol Srna (JIRA)

Pavol Srna created JBIDE-16028: ---------------------------------- Summary: Update Forge Embedded Runtime to 1.4.3.Final Key: JBIDE-16028 URL: https://issues.jboss.org/browse/JBIDE-16028 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: forge Affects Versions: 4.1.1.CR1 Reporter: Pavol Srna Assignee: Koen Aers Fix For: 4.1.1.CR1 -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16027) Build Error when using DS security module and @Secured @Stereotype annotation

by Rainer Schön (JIRA)

Rainer Schön created JBIDE-16027: ------------------------------------ Summary: Build Error when using DS security module and @Secured @Stereotype annotation Key: JBIDE-16027 URL: https://issues.jboss.org/browse/JBIDE-16027 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi-extensions Affects Versions: 4.1.1.Beta1, 4.1.0.Final Environment: Win 7 / 64-bit Eclipse Kepler SR1 / 32-bit Java 1.7.0_25 Reporter: Rainer Schön Priority: Critical When using {{(a)Secured(DecisionVoter.class)}} concept for authorization, each build ends with following build error if the method is annotated with a {{@Secured @Stereotype}} created annotation: {quote} eclipse.buildId=4.3.0.M20130911-1000 java.version=1.7.0_25 java.vendor=Oracle Corporation BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_CH Framework arguments: -product org.eclipse.epp.package.jee.product Command-line arguments: -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.jee.product Error Tue Nov 19 13:36:27 CET 2013 Errors running builder 'CDI (Context and Dependency Injection) Builder' on project 'ee7-web-ds-security'. java.lang.NullPointerException at org.jboss.tools.cdi.deltaspike.core.DeltaspikeSecurityExtension.findAnnotationAnnotatedWithSecurityBindingType(DeltaspikeSecurityExtension.java:161) at org.jboss.tools.cdi.deltaspike.core.DeltaspikeSecurityExtension.addSecurityMember(DeltaspikeSecurityExtension.java:117) at org.jboss.tools.cdi.deltaspike.core.DeltaspikeSecurityExtension.processAnnotatedMember(DeltaspikeSecurityExtension.java:106) at org.jboss.tools.cdi.internal.core.impl.definition.TypeDefinition.init(TypeDefinition.java:72) at org.jboss.tools.cdi.internal.core.impl.definition.AbstractMemberDefinition.setAnnotatable(AbstractMemberDefinition.java:64) at org.jboss.tools.cdi.internal.core.impl.definition.AbstractTypeDefinition.setType(AbstractTypeDefinition.java:69) at org.jboss.tools.cdi.internal.core.scanner.CDIBuilderDelegate.build(CDIBuilderDelegate.java:79) at org.jboss.tools.cdi.internal.core.scanner.CDIBuilderDelegate.build(CDIBuilderDelegate.java:48) at org.jboss.tools.cdi.core.CDICoreBuilder.invokeBuilderDelegates(CDICoreBuilder.java:326) at org.jboss.tools.cdi.core.CDICoreBuilder.fullBuild(CDICoreBuilder.java:261) at org.jboss.tools.cdi.core.CDICoreBuilder.build(CDICoreBuilder.java:221) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:733) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:299) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:302) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:358) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:381) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) {quote} When using the {{@SecurityBindingType}} concept for authorization or the {{@Secured}} annotation directly, the build passes with no error. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16026) Server adapter: Deploy project is not displayed nor changeable

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-16026: ---------------------------------------- Summary: Server adapter: Deploy project is not displayed nor changeable Key: JBIDE-16026 URL: https://issues.jboss.org/browse/JBIDE-16026 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.1.1.CR1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 4.1.1.CR1 -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16025) AS7 rse deployment has unnecessary 3 second delay during publish

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16025?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-16025: -------------------------------- Labels: respin-a (was: ) > AS7 rse deployment has unnecessary 3 second delay during publish > ---------------------------------------------------------------- > > Key: JBIDE-16025 > URL: https://issues.jboss.org/browse/JBIDE-16025 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.1.CR1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Labels: respin-a > Fix For: 4.1.1.CR1 > > > The block of code inside RSEPublishMethod attempts to stop and restart the deployment scanners on the remote server. The current implementation is only fit for AS < 7. There does not currently exist an implementation (in our code) for AS>=7. > This block of code is entered, and attempts to ssh into the remote machine, and execute a twiddle command, to turn off (and restart) the scanners. It also delays for 3 seconds hoping that the change goes through. > This code is questionable already for AS < 7, but for AS >= 7, it is only a wasted 3-second delay with no purpose at all. Deploy-only servers also suffer from this delay, and deploy-only servers have no such scanners to even be turned off. > Since larger-scale refactors are not currently possible at this time, the best solution is to simply exit the block of code early if the target server is not < AS7. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16025) AS7 rse deployment has unnecessary 3 second delay during publish

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16025?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-16025: -------------------------------- Priority: Critical (was: Major) > AS7 rse deployment has unnecessary 3 second delay during publish > ---------------------------------------------------------------- > > Key: JBIDE-16025 > URL: https://issues.jboss.org/browse/JBIDE-16025 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.1.CR1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Priority: Critical > Labels: respin-a > Fix For: 4.1.1.CR1 > > > The block of code inside RSEPublishMethod attempts to stop and restart the deployment scanners on the remote server. The current implementation is only fit for AS < 7. There does not currently exist an implementation (in our code) for AS>=7. > This block of code is entered, and attempts to ssh into the remote machine, and execute a twiddle command, to turn off (and restart) the scanners. It also delays for 3 seconds hoping that the change goes through. > This code is questionable already for AS < 7, but for AS >= 7, it is only a wasted 3-second delay with no purpose at all. Deploy-only servers also suffer from this delay, and deploy-only servers have no such scanners to even be turned off. > Since larger-scale refactors are not currently possible at this time, the best solution is to simply exit the block of code early if the target server is not < AS7. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16025) AS7 rse deployment has unnecessary 3 second delay during publish

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-16025: ----------------------------------- Summary: AS7 rse deployment has unnecessary 3 second delay during publish Key: JBIDE-16025 URL: https://issues.jboss.org/browse/JBIDE-16025 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.1.1.CR1 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 4.1.1.CR1 The block of code inside RSEPublishMethod attempts to stop and restart the deployment scanners on the remote server. The current implementation is only fit for AS < 7. There does not currently exist an implementation (in our code) for AS>=7. This block of code is entered, and attempts to ssh into the remote machine, and execute a twiddle command, to turn off (and restart) the scanners. It also delays for 3 seconds hoping that the change goes through. This code is questionable already for AS < 7, but for AS >= 7, it is only a wasted 3-second delay with no purpose at all. Deploy-only servers also suffer from this delay, and deploy-only servers have no such scanners to even be turned off. Since larger-scale refactors are not currently possible at this time, the best solution is to simply exit the block of code early if the target server is not < AS7. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16022) Seam Portlet deployment error on JPP 6

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16022?page=com.atlassian.jira.plugi... ] Rastislav Wagner updated JBIDE-16022: ------------------------------------- Labels: respin-a (was: ) > Seam Portlet deployment error on JPP 6 > -------------------------------------- > > Key: JBIDE-16022 > URL: https://issues.jboss.org/browse/JBIDE-16022 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: portal-gatein > Affects Versions: 4.1.1.CR1 > Environment: JBDS 7.1.0 CR1-v20131116-1929-B543, JPP 6.1 (also JPP 6.0) and Seam 2.2.2 > Reporter: Radoslav Rábara > Assignee: Snjezana Peco > Priority: Critical > Labels: respin-a > Fix For: 4.1.1.CR1 > > Attachments: jpp-seam-server.log > > > Deployment of Seam Portal Project with Seam Portlet ends with error on JPP 6. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15834) Server error while deleting application on Openshift Enterprise

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15834?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-15834. --------------------------------- > Server error while deleting application on Openshift Enterprise > --------------------------------------------------------------- > > Key: JBIDE-15834 > URL: https://issues.jboss.org/browse/JBIDE-15834 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.Beta1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Fix For: 4.1.1.CR1 > > > Sometimes attempt to delete application in Openshift Enterprise (in Openshift Online I didn't notice such bug) cause internal server error - HTTP error 500. > Application (after showed dialog) is not deleted in Openshift Enterprise. Second attempt delete application succesfully. > Unfortunately, I have no idea how to reproduce it (many various attempts done). It occurs sometimes. > Eclipse log: > {code} > com.openshift.client.OpenShiftEndpointException: Could not request https://console.itos.redhat.com/broker/rest/domains/domainequo2/applicati...: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> > <html><head> > <title>500 Internal Server Error</title> > </head><body> > <h1>Internal Server Error</h1> > <p>The server encountered an internal error or > misconfiguration and was unable to complete > your request.</p> > <p>Please contact the server administrator, > root@localhost and inform them of the time the error occurred, > and anything you might have done that may have > caused the error.</p> > <p>More information about this error may be available > in the server error log.</p> > <hr> > <address>Apache/2.2.15 (Red Hat) Server at console.itos.redhat.com Port 80</address> > </body></html> > at com.openshift.internal.client.RestService.request(RestService.java:136) > at com.openshift.internal.client.RestService.request(RestService.java:109) > at com.openshift.internal.client.RestService.request(RestService.java:92) > at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:142) > at com.openshift.internal.client.ApplicationResource.destroy(ApplicationResource.java:256) > at org.jboss.tools.openshift.express.internal.ui.job.DeleteApplicationsJob.doRun(DeleteApplicationsJob.java:47) > at org.jboss.tools.openshift.express.internal.ui.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) > Caused by: com.openshift.internal.client.httpclient.InternalServerErrorException: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> > <html><head> > <title>500 Internal Server Error</title> > </head><body> > <h1>Internal Server Error</h1> > <p>The server encountered an internal error or > misconfiguration and was unable to complete > your request.</p> > <p>Please contact the server administrator, > root@localhost and inform them of the time the error occurred, > and anything you might have done that may have > caused the error.</p> > <p>More information about this error may be available > in the server error log.</p> > <hr> > <address>Apache/2.2.15 (Red Hat) Server at console.itos.redhat.com Port 80</address> > </body></html> > at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:169) > at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:150) > at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:125) > at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.delete(UrlConnectionHttpClient.java:113) > at com.openshift.internal.client.RestService.request(RestService.java:183) > at com.openshift.internal.client.RestService.request(RestService.java:123) > ... 7 more > Caused by: java.io.IOException: Server returned HTTP response code: 500 for URL: https://console.itos.redhat.com/broker/rest/domains/domainequo2/applicati... > at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1625) > at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254) > at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:146) > ... 11 more > {code} -- 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, 5 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 November 2013