July 2010 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-6661) Deploying BPEL process with dependent jars

by Gary Brown (JIRA)

Deploying BPEL process with dependent jars ------------------------------------------ Key: JBIDE-6661 URL: https://jira.jboss.org/browse/JBIDE-6661 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: bpel Reporter: Gary Brown Attachments: Quickstart_bpel_service_handler-1.jar The current BPEL deployer packages up BPEL, WSDL and XSD artifacts found in the bpelContent folder, and deploys the packaged jar to the JBossAS server. Although the BPEL process cannot invoke Java code, occasionally the Web Service configuration references Java classes - e.g. JAX-WS handlers. In this situation, it would be necessary for those Java classes to be deployed to the server along with the BPEL process. One approach would be for the user to independently deploy the dependent Java code to the server (e.g. in the server/default/lib folder) although this assumes that the code will not need to change during the lifetime of the server. An alternative approach would be to bundle the dependent jar inside the BPEL deployment jar. This can be achieved by placing the dependent jar at the top level of the BPEL jar. The RiftSaw quickstart service_handler example has been attached, as an example of how this can be done. One solution maybe to offer the user the option to reference external jars, or other Java Eclipse projects that could be packaged on deployment, that can then be included in the packaged BPEL jar. Although this may be simply a case of the user packaging the jar manually, and placing it in the bpelContent folder themselves? -- 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, 4 months

7
8
0 / 0

[JBoss JIRA] Created: (JBIDE-5703) Hibernate Reverse Engineering Editor should show multiple catalogs/schemas from a MySQL database

by Pieter Hartog (JIRA)

Hibernate Reverse Engineering Editor should show multiple catalogs/schemas from a MySQL database ------------------------------------------------------------------------------------------------ Key: JBIDE-5703 URL: https://jira.jboss.org/jira/browse/JBIDE-5703 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Hibernate Affects Versions: 3.1.0.CR1 Reporter: Pieter Hartog Priority: Minor MySQL is funny with catalogs and schemas. It doesn't support schemas like most other databases do. It's just called 'databases'. When you try to create a reveng.xml file using the Hibernate Reverse Engineering Editor, you can't get multiple databases / schemas to show up. It looks like the wizard looks at the hibernate.connection.url property in the hibernate-console.properties file. However, when I leave out the name of the database (e.g. jdbc:mysql://localhost:3306) without the database, the wizard does not return any tables. When you leave out the default database (i.e. schema) name in the connection.url, you should see all databases/ schemas for that one connection. When a user selects multiple schemas, the resulting reveng.xml file should have one <schema-selection ...> element for each schema the user wants to map tables from. -- 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, 4 months

5
5
0 / 0

[JBoss JIRA] Created: (JBIDE-6622) [Designer] Search menus and toolbar buttons should only appear in Designer perspective

by Brian Fitzpatrick (JIRA)

[Designer] Search menus and toolbar buttons should only appear in Designer perspective -------------------------------------------------------------------------------------- Key: JBIDE-6622 URL: https://jira.jboss.org/browse/JBIDE-6622 Project: Tools (JBoss Tools) Issue Type: Bug Components: teiid Affects Versions: 3.2.0.M1 Reporter: Brian Fitzpatrick Assignee: Barry LaFond Fix For: 3.2.x After installing Designer, I saw a couple of buttons on the toolbar: Find Model Object By Name and Open Metadata Search Page. Why do these seem to show up in every perspective? Same with the new items in the Search menu... Find Model Object, Metadata, Transformations. Does it make sense to have these everywhere or should they only appear in the Designer perspective? -- 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, 4 months

4
5
0 / 0

[JBoss JIRA] Created: (JBIDE-5826) Incorrect work of EL and CDI validator for action Validate

by Viacheslav Kabanovich (JIRA)

Incorrect work of EL and CDI validator for action Validate ---------------------------------------------------------- Key: JBIDE-5826 URL: https://jira.jboss.org/jira/browse/JBIDE-5826 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.CR1 Reporter: Viacheslav Kabanovich Assignee: Alexey Kazakov Fix For: 3.1.0.CR2 1. Switch off automatic build. 2. Create 2 seam projects. 3. Build them manually. 4. Open an xhtml of the first project. 5. Add some correct EL in it, and run Validate on that file. 6. Repeat that several times corrupting and fixing EL and running Validate to make sure that it is ok. 7. Open an xhtml of the second project. 8. Try to do the same as with the first xhtml. Make sure that action Validate does not work. 9. Return to the first xhtml. Make sure that action Validate works. It looks like action Validate works only for the project on which it was run first. -- 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, 4 months

4
3
0 / 0

[JBoss JIRA] Created: (JBIDE-6718) The import org.jboss.tools.cdi.text.ext.hyperlink.EventHyperlinkDetector cannot be resolved in org.jboss.tools.cdi.text.ext.test.EventHyperlinkDetectorTest.java

by Nick Boldt (JIRA)

The import org.jboss.tools.cdi.text.ext.hyperlink.EventHyperlinkDetector cannot be resolved in org.jboss.tools.cdi.text.ext.test.EventHyperlinkDetectorTest.java ---------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-6718 URL: https://jira.jboss.org/browse/JBIDE-6718 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Affects Versions: 3.2.0.M2 Reporter: Nick Boldt Assignee: Alexey Kazakov (default-compile) on project org.jboss.tools.cdi.text.ext.test: Compilation failure: Compilation failure: /mnt/hudson_workspace/workspace/jbosstools-3.2.0.M2.continuous/sources/cdi/tests/org.jboss.tools.cdi.text.ext.test/src/org/jboss/tools/cdi/text/ext/test/EventHyperlinkDetectorTest.java (at line 6):[-1,-1] import org.jboss.tools.cdi.text.ext.hyperlink.EventHyperlinkDetector; ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The import org.jboss.tools.cdi.text.ext.hyperlink.EventHyperlinkDetector cannot be resolved /mnt/hudson_workspace/workspace/jbosstools-3.2.0.M2.continuous/sources/cdi/tests/org.jboss.tools.cdi.text.ext.test/src/org/jboss/tools/cdi/text/ext/test/EventHyperlinkDetectorTest.java (at line 26):[-1,-1] checkRegions("JavaSource/org/jboss/jsr299/tck/tests/event/bindingTypes/EventEmitter.java", regionList, new EventHyperlinkDetector()); ^^^^^^^^^^^^^^^^^^^^^^ EventHyperlinkDetector cannot be resolved to a type -- 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, 4 months

4
3
0 / 0

[JBoss JIRA] Created: (JBIDE-5799) CDI Validator fails with BadLocationException

by Alexey Kazakov (JIRA)

CDI Validator fails with BadLocationException --------------------------------------------- Key: JBIDE-5799 URL: https://jira.jboss.org/jira/browse/JBIDE-5799 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.CR2 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.1.0.CR2 Add such producer field to any CDI bean: @Produces @Typed(String.class) private Integer i = new Integer(0); Force CDI validation (build the project). See eclipse log: org.eclipse.jface.text.BadLocationException at org.eclipse.jface.text.TreeLineTracker.fail(TreeLineTracker.java:1061) at org.eclipse.jface.text.TreeLineTracker.lineByOffset(TreeLineTracker.java:271) at org.eclipse.jface.text.TreeLineTracker.getLineNumberOfOffset(TreeLineTracker.java:1143) at org.eclipse.jface.text.AbstractLineTracker.getLineNumberOfOffset(AbstractLineTracker.java:161) at org.eclipse.jface.text.AbstractDocument.getLineOfOffset(AbstractDocument.java:881) at org.eclipse.core.internal.filebuffers.SynchronizableDocument.getLineOfOffset(SynchronizableDocument.java:398) at org.jboss.tools.jst.web.kb.internal.validation.ValidationErrorManager.addError(ValidationErrorManager.java:182) at org.jboss.tools.jst.web.kb.internal.validation.ValidationErrorManager.addError(ValidationErrorManager.java:119) at org.jboss.tools.jst.web.kb.internal.validation.ValidationErrorManager.addError(ValidationErrorManager.java:133) at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateBean(CDICoreValidator.java:263) at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateResource(CDICoreValidator.java:223) at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validate(CDICoreValidator.java:179) at org.jboss.tools.jst.web.kb.internal.validation.ValidatorManager.validate(ValidatorManager.java:92) at org.jboss.tools.jst.web.kb.internal.validation.ValidatorManager.validateInJob(ValidatorManager.java:75) at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:78) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) The resoun of this execption is that ITypedDeclaration returns start position == -1 for String.class -- 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, 4 months

4
3
0 / 0

[JBoss JIRA] Created: (JBIDE-5747) IllegalArgumentException is thrown during CDI validation.

by Alexey Kazakov (JIRA)

IllegalArgumentException is thrown during CDI validation. --------------------------------------------------------- Key: JBIDE-5747 URL: https://jira.jboss.org/jira/browse/JBIDE-5747 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Affects Versions: 3.1.0.CR2 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.1.0.CR2 java.lang.IllegalArgumentException at org.eclipse.jdt.core.Signature.appendTypeSignature(Signature.java:2371) at org.eclipse.jdt.core.Signature.appendTypeSignature(Signature.java:2278) at org.eclipse.jdt.core.Signature.toCharArray(Signature.java:2257) at org.jboss.tools.common.model.util.EclipseJavaUtil.resolveTypeAsString(EclipseJavaUtil.java:50) at org.jboss.tools.cdi.internal.core.impl.definition.ParametedTypeFactory.getParametedType(ParametedTypeFactory.java:18) at org.jboss.tools.cdi.internal.core.impl.AbstractBeanElement.getRestrictedTypeDeclaratios(AbstractBeanElement.java:133) at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateBean(CDICoreValidator.java:246) at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateAll(CDICoreValidator.java:197) at org.jboss.tools.jst.web.kb.internal.validation.ValidatorManager.validateAll(ValidatorManager.java:99) at org.jboss.tools.jst.web.kb.internal.validation.ValidatorManager.validateInJob(ValidatorManager.java:78) at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:78) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) org.eclipse.jdt.core.Signature.toCharArray() is supposed to get a singnature but CDI model gives a type name instead of signature. -- 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, 4 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-5770) CDI EL code completion: Use weld icons for EL proposals.

by Alexey Kazakov (JIRA)

CDI EL code completion: Use weld icons for EL proposals. -------------------------------------------------------- Key: JBIDE-5770 URL: https://jira.jboss.org/jira/browse/JBIDE-5770 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: cdi (jsr-299) Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.1.0.CR2 -- 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, 4 months

2
5
0 / 0

[JBoss JIRA] Created: (JBIDE-5412) Add CDI plug-ins to build for GA.

by Alexey Kazakov (JIRA)

Add CDI plug-ins to build for GA. --------------------------------- Key: JBIDE-5412 URL: https://jira.jboss.org/jira/browse/JBIDE-5412 Project: Tools (JBoss Tools) Issue Type: Task Components: Build/Releng, cdi (jsr-299) Reporter: Alexey Kazakov Assignee: Denis Golovin Fix For: 3.1.0.GA So it's time to add CDI module to the build again. For GA. :) -- 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, 4 months

4
3
0 / 0

[JBoss JIRA] Created: (JBIDE-5459) Please add new cdi plugins to build

by Viacheslav Kabanovich (JIRA)

Please add new cdi plugins to build ----------------------------------- Key: JBIDE-5459 URL: https://jira.jboss.org/jira/browse/JBIDE-5459 Project: Tools (JBoss Tools) Issue Type: Task Components: Build/Releng, cdi (jsr-299) Affects Versions: 3.1.0.GA Reporter: Viacheslav Kabanovich Assignee: Denis Golovin Fix For: 3.1.0.GA org.jboss.tools.cdi.xml org.jboss.tools.cdi.xml.ui -- 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, 4 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 July 2010