January 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Updated: (JBIDE-8054) Text selection in VPE source pane is not synchronized with selection in Visual Pane

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8054?page=com.atlassian.jira.plugin... ] Vlado Pakan updated JBIDE-8054: ------------------------------- Attachment: selectionError.swf > Text selection in VPE source pane is not synchronized with selection in Visual Pane > ----------------------------------------------------------------------------------- > > Key: JBIDE-8054 > URL: https://issues.jboss.org/browse/JBIDE-8054 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Visual Page Editor core > Affects Versions: 3.2.0.CR1 > Environment: Linux 32bit JBDS 4.0.0.v201012161657N-H584-CR1 > Reporter: Vlado Pakan > Assignee: Maxim Areshkau > Attachments: selectionError.swf > > > Steps to reproduce: > 1. Open any jsp page in VPE editor and select some text in VPE source pane. The same text is selected in visual pane. > 2. Make mouse left click somewhere in visual pane. There should be no selected text. > 3. Select the same text in step 1. via source pane > 4. No text is selected in visual pane but the same text selected in source pane has to be selected in visual pane. > After reopening jsp page it's working again as mentioned above. Selection is synchronized only first time. > See attached screencast. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBDS-1435) Two differerent target plaforms for JBDS

by Nick Boldt (JIRA)

Two differerent target plaforms for JBDS ---------------------------------------- Key: JBDS-1435 URL: https://jira.jboss.org/browse/JBDS-1435 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: Build Affects Versions: 4.0.0.Beta2 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 4.0.0.CR1 Build 1: http://hudson.qa.jboss.com/hudson/view/DevStudio_Stable_Branch/job/devstu... uses this target platform: /home/hudson/static_build_env/jbds/jbds-target-platform/jbds400-e361-wtp322.target/ Build 2: http://hudson.qa.jboss.com/hudson/job/devstudio-4.0.0.Beta2.nightly/ uses this target platform: /qa/services/http/binaries/RHDS/requirements/helios/JBDS-4.0.0-target-p2repo Must determine how these are different and get them in synch so that devstudio-4.0_stable_branch.updatesite build is once again green. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
15
0 / 0

[JBoss JIRA] Updated: (JBIDE-8045) Unable to select fault variable data type in faultHandler.

by Marek Baluch (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8045?page=com.atlassian.jira.plugin... ] Marek Baluch updated JBIDE-8045: -------------------------------- Attachment: fault_handler.zip > Unable to select fault variable data type in faultHandler. > ---------------------------------------------------------- > > Key: JBIDE-8045 > URL: https://issues.jboss.org/browse/JBIDE-8045 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: bpel > Affects Versions: 3.2.0.Beta2, 3.2.0.CR1 > Reporter: Marek Baluch > Attachments: fault_handler.zip > > > User is not able to select the data type for a user defined fault when defining a faultHandler catch branch. It's possible to attempt to select the data type using the browse button but the chosen type is not noticed by the UI. The message structure is missing too. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBIDE-8042) BPEL validator does not recognize counter variable inside forEach.

by Marek Baluch (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8042?page=com.atlassian.jira.plugin... ] Marek Baluch updated JBIDE-8042: -------------------------------- Attachment: Screen.png > BPEL validator does not recognize counter variable inside forEach. > ------------------------------------------------------------------ > > Key: JBIDE-8042 > URL: https://issues.jboss.org/browse/JBIDE-8042 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: bpel > Affects Versions: 3.2.0.Beta2, 3.2.0.CR1 > Reporter: Marek Baluch > Attachments: Screen.png > > > The declared counter variable in the following code snippet is marked by the validator red (see attached image). > CODE > ... > <bpel:variable name="number" type="xsd:int"/> > ... > <bpel:forEach parallel="no" counterName="counter" name="ForEach"> > <bpel:startCounterValue><![CDATA[1]]></bpel:startCounterValue> > <bpel:finalCounterValue><![CDATA[10]]></bpel:finalCounterValue> > <bpel:scope name="Scope"> > <bpel:assign validate="no" name="Assign"> > <bpel:copy> > <bpel:from variable="counter"/> > <bpel:to variable="number"/> > </bpel:copy> > </bpel:assign> > </bpel:scope> > </bpel:forEach> -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-7905) Unable to expand Hibernate Console after JPA entity is added in JPA project

by Jiri Peterka (JIRA)

Unable to expand Hibernate Console after JPA entity is added in JPA project --------------------------------------------------------------------------- Key: JBIDE-7905 URL: https://issues.jboss.org/browse/JBIDE-7905 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.2.0.Beta2 Environment: JBDS 4.0.0.beta2 H33, Linux 64 Reporter: Jiri Peterka Steps: 1. Create jpa 2.0 project (target runtime jboss-eap 5.1, hibernate platform, hsql connection, discover classes automatically) 2. Add JPA entity 3. Open hibernate console org.hibernate.console.HibernateConsoleRuntimeException: Could not create JPA based Configuration at org.hibernate.console.ConfigurationFactory.buildJPAConfiguration(ConfigurationFactory.java:242) at org.hibernate.console.ConfigurationFactory.buildConfiguration(ConfigurationFactory.java:172) at org.hibernate.console.ConfigurationFactory.createConfiguration(ConfigurationFactory.java:94) at org.hibernate.console.ConsoleConfiguration$3.execute(ConsoleConfiguration.java:209) at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63) at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:71) at org.hibernate.console.ConsoleConfiguration.buildWith(ConsoleConfiguration.java:206) at org.hibernate.console.ConsoleConfiguration.build(ConsoleConfiguration.java:162) at org.hibernate.eclipse.console.workbench.ConsoleConfigurationWorkbenchAdapter.getChildren(ConsoleConfigurationWorkbenchAdapter.java:40) at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.getChildren(BasicWorkbenchAdapter.java:100) at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:106) at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:235) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.hibernate.console.ConfigurationFactory.buildJPAConfiguration(ConfigurationFactory.java:229) ... 12 more Caused by: javax.persistence.PersistenceException: [PersistenceUnit: jpatest1] Unable to configure EntityManagerFactory at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:376) ... 17 more Caused by: org.hibernate.AnnotationException: No identifier specified for entity: org.example2.Customer2 at org.hibernate.cfg.InheritanceState.determineDefaultAccessType(InheritanceState.java:272) at org.hibernate.cfg.InheritanceState.getElementsToProcess(InheritanceState.java:227) at org.hibernate.cfg.AnnotationBinder.bindClass(AnnotationBinder.java:712) at org.hibernate.cfg.AnnotationConfiguration.processArtifactsOfType(AnnotationConfiguration.java:636) at org.hibernate.cfg.AnnotationConfiguration.secondPassCompile(AnnotationConfiguration.java:359) at org.hibernate.cfg.Configuration.buildMappings(Configuration.java:1206) at org.hibernate.ejb.Ejb3Configuration.buildMappings(Ejb3Configuration.java:1459) at org.hibernate.ejb.EventListenerConfigurator.configure(EventListenerConfigurator.java:193) at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:1086) at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:280) at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:364) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

3
13
0 / 0

[JBoss JIRA] Updated: (JBDS-1483) By default name for JBDS Nightly Update site and Update Site zip is "file:///home/hudson/static_build_env/jbds/tools/sources/JBDS-REPO"

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-1483?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-1483: -------------------------------- Attachment: screenshot36.png > By default name for JBDS Nightly Update site and Update Site zip is "file:///home/hudson/static_build_env/jbds/tools/sources/JBDS-REPO" > --------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-1483 > URL: https://issues.jboss.org/browse/JBDS-1483 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: Build, P2 Enabled Product > Affects Versions: 4.0.0.CR1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.0.0.CR1 > > Attachments: screenshot36.png > > > See attached screenshot for details -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBDS-1478) Move rse-terminals requirement archive to jboss-tools requirements site and update URI for it

by Denis Golovin (JIRA)

Move rse-terminals requirement archive to jboss-tools requirements site and update URI for it --------------------------------------------------------------------------------------------- Key: JBDS-1478 URL: https://issues.jboss.org/browse/JBDS-1478 Project: Developer Studio (JBoss Developer Studio) Issue Type: Task Components: Build Affects Versions: 4.0.0.CR1 Reporter: Denis Golovin Assignee: Nick Boldt Priority: Minor Fix For: 4.0.0.CR1 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
9
0 / 0

[JBoss JIRA] Created: (JBDS-1473) Publish p2 product update site created during nightly product build

by Denis Golovin (JIRA)

Publish p2 product update site created during nightly product build ------------------------------------------------------------------- Key: JBDS-1473 URL: https://issues.jboss.org/browse/JBDS-1473 Project: Developer Studio (JBoss Developer Studio) Issue Type: Task Components: Build Affects Versions: 4.0.0.CR1 Reporter: Denis Golovin Assignee: Nick Boldt Fix For: 4.0.0.CR1 Every nightly product build creates p2 repo which is literary the update site that can be used to update previously installed p2 enabled JBDS. Example of location this p2 repo in build results is http://reports.qa.atl.jboss.com/binaries/RHDS/builds/staging/devstudio-4.... It should be published and available from static location so QA can use this URL to verify update. This URL could be http://reports.qa.atl.jboss.com/binaries/RHDS/updates/nightly/trunk -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
7
0 / 0

[JBoss JIRA] Created: (JBIDE-6343) Create a "sanity check plugin/feature" tool for running on integration builds

by Max Rydahl Andersen (JIRA)

Create a "sanity check plugin/feature" tool for running on integration builds ----------------------------------------------------------------------------- Key: JBIDE-6343 URL: https://jira.jboss.org/browse/JBIDE-6343 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Max Rydahl Andersen Fix For: LATER I keep seeing the following antipatterns or oversights happening in our codebase, most of them I believe we could mechanically check for. No duplicate names in .project since it makes it impossible to import into Eclipse bin folders should be svn:ignored and not be committed (causes problems when doing svn synchronization and all the .class files are showing up and some even commits it) things in svn:ignore should be committed (either someone overrode svn:ignore or the svn:ignore were added later) if pom.xml file exists target should be svn:ignored too. Execution environment should be specified in manifest.mf's -- 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

13 years, 11 months

2
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2011