[JBoss JIRA] (JBTIS-83) JBoss ESB (aka SOA-P 5) Examples Need Updating/Migration
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBTIS-83?page=com.atlassian.jira.plugin.s... ]
Brian Fitzpatrick commented on JBTIS-83:
----------------------------------------
Hey Nick - thanks for the feedback.
1) Yes, that would be wonderful if we could get them in to test.
2) 7.1 was just the example filename I'd seen bouncing around in IRC chats so that's what I went with - am happy to change to 8.0 if that's the going thought.
3) Can you give me an example of "latest in a branch" vs. "specific SHA hash"? I went with what I could get to work locally but I'd much rather not have the SHA in there to muss things up.
> JBoss ESB (aka SOA-P 5) Examples Need Updating/Migration
> --------------------------------------------------------
>
> Key: JBTIS-83
> URL: https://issues.jboss.org/browse/JBTIS-83
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: ESB
> Affects Versions: 4.0.0
> Reporter: Len DiMaggio
> Assignee: Brian Fitzpatrick
> Fix For: 4.0.0
>
> Attachments: jbtis-project-examples-community-7.1.xml
>
>
> JBoss ESB (aka SOA-P 5) Examples Need Updating/Migration
> Steps as defined by Nick (thanks Nick!):
> a) the contents of the examples are in a former employee's SVN workspace
> and haven't been updated since a couple of years. They don't really work
> as well as they could.
> b) the examples are all mostly duplicated in the quickstarts folder that
> ships with SOA-P 5.3.1. See
> https://bugzilla.redhat.com/show_bug.cgi?id=951677 and
> https://issues.jboss.org/browse/JBTIS-62
> Basically, we need to:
> * fix the quickstarts in SOA-P 6 so they ACTUALLY WORK as importable
> eclipse projects (merge in contents from duplicate examples in Denny's
> workspace). Could decide to backport to 5.3 if there's a 5.3.2 planned;
> if not, no great need.
> * copy the older examples that are not already in SOA-P 5.3 - the ones
> that are *exclusively* in Denny's workspace - into SOA-P 6 so they'll be
> available there.
> * update the BPEL Examples guide as needed
> * document the fact that these examples are no longer available as
> importable zipped example projects contributed by a plugin, but rather
> as already-unpacked projects nested within the SOA-P runtime zip
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-17877) Classe with unbounded type parameter triggers "TypeParameter cannot be cast to IType" exceptions
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17877?page=com.atlassian.jira.plugi... ]
Xavier Coulon reassigned JBIDE-17877:
-------------------------------------
Assignee: Denis Golovin (was: Xavier Coulon)
Assigning to you while waiting for your answer.
> Classe with unbounded type parameter triggers "TypeParameter cannot be cast to IType" exceptions
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-17877
> URL: https://issues.jboss.org/browse/JBIDE-17877
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.2.0.Beta3
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 4.2.0.CR1
>
>
> Exception below was fixed by checking instance of target obect before casting to IType see JBIDE-17716 and skipping the rest of the code.
> Do we need to do something extra in this case?
> {code}
> org.jboss.tools.common
> Error
> Mon Jun 30 12:28:44 CEST 2014
> org.eclipse.jdt.internal.core.TypeParameter cannot be cast to org.eclipse.jdt.core.IType
> org.jboss.tools.common.validation.JBTValidationException: org.eclipse.jdt.internal.core.TypeParameter cannot be cast to org.eclipse.jdt.core.IType
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:187)
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateString(AsYouTypeValidatorManager.java:205)
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateString(AsYouTypeValidatorManager.java:200)
> at org.jboss.tools.common.validation.java.JavaDirtyRegionProcessor.endProcessing(JavaDirtyRegionProcessor.java:498)
> at org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor$BackgroundThread.run(DirtyRegionProcessor.java:697)
> Caused by: java.lang.ClassCastException: org.eclipse.jdt.internal.core.TypeParameter cannot be cast to org.eclipse.jdt.core.IType
> at org.jboss.tools.ws.jaxrs.core.jdt.SourceType.from(SourceType.java:79)
> at org.jboss.tools.ws.jaxrs.core.jdt.JdtUtils.getReturnType(JdtUtils.java:1143)
> at org.jboss.tools.ws.jaxrs.core.jdt.JdtUtils.resolveMethodSignature(JdtUtils.java:1067)
> at org.jboss.tools.ws.jaxrs.core.jdt.JdtUtils.resolveMethodSignatures(JdtUtils.java:1037)
> at org.jboss.tools.ws.jaxrs.core.jdt.CompilationUnitsRepository.recordAST(CompilationUnitsRepository.java:112)
> at org.jboss.tools.ws.jaxrs.core.jdt.CompilationUnitsRepository.getAST(CompilationUnitsRepository.java:76)
> at org.jboss.tools.ws.jaxrs.ui.internal.validation.JaxrsMetamodelValidator.validate(JaxrsMetamodelValidator.java:413)
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:183)
> ... 4 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBTIS-83) JBoss ESB (aka SOA-P 5) Examples Need Updating/Migration
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-83?page=com.atlassian.jira.plugin.s... ]
Nick Boldt commented on JBTIS-83:
---------------------------------
As these are NEW properties to be added to the ide-config.properties file, then we can safely add the above lines to the file so you can test it.
https://github.com/jbosstools/jbosstools-download.jboss.org/pull/387
However, I notice your filepath uses a specific commitID and that the filename has "7.1" in the name, rather than 8.0. Is that intentional? If you used "latest in a branch" rather than "specific SHA hash" you would be able to more easily update this on the fly w/o having to update the IDE config file.
> JBoss ESB (aka SOA-P 5) Examples Need Updating/Migration
> --------------------------------------------------------
>
> Key: JBTIS-83
> URL: https://issues.jboss.org/browse/JBTIS-83
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: ESB
> Affects Versions: 4.0.0
> Reporter: Len DiMaggio
> Assignee: Brian Fitzpatrick
> Fix For: 4.0.0
>
> Attachments: jbtis-project-examples-community-7.1.xml
>
>
> JBoss ESB (aka SOA-P 5) Examples Need Updating/Migration
> Steps as defined by Nick (thanks Nick!):
> a) the contents of the examples are in a former employee's SVN workspace
> and haven't been updated since a couple of years. They don't really work
> as well as they could.
> b) the examples are all mostly duplicated in the quickstarts folder that
> ships with SOA-P 5.3.1. See
> https://bugzilla.redhat.com/show_bug.cgi?id=951677 and
> https://issues.jboss.org/browse/JBTIS-62
> Basically, we need to:
> * fix the quickstarts in SOA-P 6 so they ACTUALLY WORK as importable
> eclipse projects (merge in contents from duplicate examples in Denny's
> workspace). Could decide to backport to 5.3 if there's a 5.3.2 planned;
> if not, no great need.
> * copy the older examples that are not already in SOA-P 5.3 - the ones
> that are *exclusively* in Denny's workspace - into SOA-P 6 so they'll be
> available there.
> * update the BPEL Examples guide as needed
> * document the fact that these examples are no longer available as
> importable zipped example projects contributed by a plugin, but rather
> as already-unpacked projects nested within the SOA-P runtime zip
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-17524) BrowserSim: not all source is shown for external URL
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17524?page=com.atlassian.jira.plugi... ]
Rastislav Wagner commented on JBIDE-17524:
------------------------------------------
No editor is opened in my case. Im trying this on JBDS Beta3b. The only thing i can see after clicking on View Page source is exception mentioned above (which as you say is ok for now) and one line in console
{code}
org.jboss.tools.vpe.browsersim.command.viewSource:https://www.google.cz/?gfe_rd=cr&ei=IA3RU9yyOaHY8gey64DoAg&gws_rd=ssl
{code}
> BrowserSim: not all source is shown for external URL
> ----------------------------------------------------
>
> Key: JBIDE-17524
> URL: https://issues.jboss.org/browse/JBIDE-17524
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 4.2.0.Beta1
> Reporter: Konstantin Marmalyukov
> Assignee: Konstantin Marmalyukov
> Fix For: 4.2.0.CR1
>
> Attachments: Screenshot 2014-07-24 16.32.11.png
>
>
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-17285) Lucene error messages during tests
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17285?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-17285:
----------------------------------
Summary: Lucene error messages during tests (was: Errors in jaxrs.core tests)
> Lucene error messages during tests
> ----------------------------------
>
> Key: JBIDE-17285
> URL: https://issues.jboss.org/browse/JBIDE-17285
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.2.0.Alpha2
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.2.0.CR1
>
>
> The following errors appear in the build logs:
> {code}
> Exception in thread "Lucene Merge Thread #2" org.apache.lucene.index.MergePolicy$MergeException: org.apache.lucene.store.AlreadyClosedException: this Directory is closed
> at org.apache.lucene.index.ConcurrentMergeScheduler.handleMergeException(ConcurrentMergeScheduler.java:517)
> at org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run(ConcurrentMergeScheduler.java:482)
> Caused by: org.apache.lucene.store.AlreadyClosedException: this Directory is closed
> at org.apache.lucene.store.Directory.ensureOpen(Directory.java:288)
> at org.apache.lucene.store.RAMDirectory.listAll(RAMDirectory.java:94)
> at org.apache.lucene.index.IndexFileDeleter.refresh(IndexFileDeleter.java:335)
> at org.apache.lucene.index.IndexWriter.merge(IndexWriter.java:3954)
> at org.apache.lucene.index.ConcurrentMergeScheduler.doMerge(ConcurrentMergeScheduler.java:388)
> at org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run(ConcurrentMergeScheduler.java:456)
> {code}
> but the tests pass.
> Maybe using Lucene's SearcherManager (as shown on http://blog.mikemccandless.com/2011/09/lucenes-searchermanager-simplifies...) could fix the problem ?
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months