September 2011 - jbosstools-issues

[JBoss JIRA] Created: (JBDS-1855) helloworld_mail quickstart - confusing instructions in readme file

by Len DiMaggio (JIRA)

helloworld_mail quickstart - confusing instructions in readme file ------------------------------------------------------------------ Key: JBDS-1855 URL: https://issues.jboss.org/browse/JBDS-1855 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: SOA Platform Affects Versions: 4.1.1.M1 Environment: Version: 4.1.1.GA Build id: v20110908-0132-H1012-GA Build date: 20110908-0132 Reporter: Len DiMaggio Assignee: Brian Fitzpatrick Fix For: 4.1.1.Final The readme.txt file says: --- To run this example, you should create EAP server runtime with the name is "jboss-soa-p.5.0 Runtime" in your workspace. You will need to place a copy of camel-mail-2.4.0.jar into esbcontent/lib. You will need to copy mail-ra.jar from ${jboss.server.home.dir}/deploy/mail-ra.rar. --- Two problems: 1) camel-mail-2.4.0.jar is already installed in esbcontent/lib 2) Where should the user copy mail-ra.jar? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (JBDS-1856) helloworld_mail quickstart - fails to deploy - class not found: java.lang.NoClassDefFoundError: org/springframework/mail/javamail/JavaMailSender

by Len DiMaggio (JIRA)

helloworld_mail quickstart - fails to deploy - class not found: java.lang.NoClassDefFoundError: org/springframework/mail/javamail/JavaMailSender ------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBDS-1856 URL: https://issues.jboss.org/browse/JBDS-1856 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: SOA Platform Affects Versions: 4.1.1.M1 Environment: Version: 4.1.1.GA Build id: v20110908-0132-H1012-GA Build date: 20110908-0132 SOA-P 5.2.0, ER4 Reporter: Len DiMaggio Assignee: Brian Fitzpatrick Fix For: 4.1.1.M1 I can't see anything in the quickstart that needs Spring - where is the reference? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

4
11
0 / 0

[JBoss JIRA] Created: (JBIDE-9766) Refactor org.jboss.tools.jst.web.WebUtils.getWebRootFolders() to take into account derived resources and default web root folder

by Alexey Kazakov (JIRA)

Refactor org.jboss.tools.jst.web.WebUtils.getWebRootFolders() to take into account derived resources and default web root folder -------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-9766 URL: https://issues.jboss.org/browse/JBIDE-9766 Project: Tools (JBoss Tools) Issue Type: Task Components: common/jst/core Affects Versions: 3.3.0.M3 Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.3.0.M4 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-9765) Fix optional dependecies in MANIFEST.MF with "; x-installation:=greedy" to support using Tycho 0.13

by Nick Boldt (JIRA)

Fix optional dependecies in MANIFEST.MF with ";x-installation:=greedy" to support using Tycho 0.13 -------------------------------------------------------------------------------------------------- Key: JBIDE-9765 URL: https://issues.jboss.org/browse/JBIDE-9765 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Build/Releng Affects Versions: 3.3.0.M4 Reporter: Nick Boldt Assignee: Denis Golovin Fix For: 3.3.0.M4 Denis said: {code} resolved by adding ;x-installation:=greedy into xulrunner bundles dependencies in org.jboss.tools.xulrunner bundle. Now it works. with -DtychoVersion=0.13.0. It also means we can now build product with tycho :) usage plug-in references should be also updated. {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (JBDS-1862) Add RichFaces tag library declaration to RichFaces portlet project

by Miroslav Cupak (JIRA)

Add RichFaces tag library declaration to RichFaces portlet project ------------------------------------------------------------------ Key: JBDS-1862 URL: https://issues.jboss.org/browse/JBDS-1862 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.1.0.GA Reporter: Miroslav Cupak Priority: Minor When you generate a JSF portlet project with RichFaces libraries, the RichFaces part is not really as ready for use as it could be - e.g. LoadStyleStrategy and LoadScriptStrategy are set to NONE so you have to include the relevant scripts manually and when you add a JSF portlet to the project, the pages which are created do not contain RichFaces tag library declaration. I don't see any JSF template containing the declaration for RichFaces either, which means you have to find and add it by yourself. My suggestion would be to have templates for JSF pages with RichFaces among other JSF/JSP templates and/or have something like this {code:xml} <ui:composition xmlns="http://www.w3.org/1999/xhtml" xmlns:f="http://java.sun.com/jsf/core" xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:h="http://java.sun.com/jsf/html" xmlns:a4j="http://richfaces.org/a4j" xmlns:rich="http://richfaces.org/rich"> ... {code} instead of something like this {code:xml} <ui:composition xmlns="http://www.w3.org/1999/xhtml" xmlns:f="http://java.sun.com/jsf/core" xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:h="http://java.sun.com/jsf/html"> ... {code} in generated JSF pages when the RichFaces libraries are included in the project. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JBDS-1857) Review Teiid Designer User Guide for JBDS 4.1.1

by Isaac Rooskov (JIRA)

Review Teiid Designer User Guide for JBDS 4.1.1 ----------------------------------------------- Key: JBDS-1857 URL: https://issues.jboss.org/browse/JBDS-1857 Project: Developer Studio (JBoss Developer Studio) Issue Type: Task Security Level: Public (Everyone can see) Reporter: Isaac Rooskov Hey Len and QE team, Apart from one bug (that may or may not apply to the book rather than the code: TOOLSDOC-247), this book is ready for review and I would say you're good to go. If you find any issues please open an issue in TOOLSDOC against 3.2.2.Final and assign it to Barry LaFond (not myself, as Barry writes and maintains this book). Thanks, Isaac -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
1
0 / 0

[JBoss JIRA] Commented: (JBDS-1819) Configure SOA-P quickstarts to be run OOTB in JBDS 4.1.1 with SOA-P 5.2

by Isaac Rooskov (JIRA)

[ https://issues.jboss.org/browse/JBDS-1819?page=com.atlassian.jira.plugin.... ] Isaac Rooskov commented on JBDS-1819: ------------------------------------- Len, I think that would be something to be documented wherever these examples are referred to within SOA documentation, so perhaps you should open up a JIRA for the SOA docs team concerning that. > Configure SOA-P quickstarts to be run OOTB in JBDS 4.1.1 with SOA-P 5.2 > ----------------------------------------------------------------------- > > Key: JBDS-1819 > URL: https://issues.jboss.org/browse/JBDS-1819 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Security Level: Public(Everyone can see) > Components: SOA Platform > Affects Versions: 4.1.0.CR3 > Reporter: Len DiMaggio > Assignee: Brian Fitzpatrick > Fix For: 4.1.1.M1 > > Attachments: bfitzpat_examples.png, product_examples.png, runtimes.png > > > Need to ensure there are sample ESB quickstarts available to run cleanly with SOA-P 5.2 on JBDS 4.1.1 > Was: > Need to verify that all JBDS supplied sample ESB quickstarts run cleanly with SOA-P 5.2 on JBDS 4.1.1 > Was: > This subject comes up now and then - it would be very useful to new users to have the full set of SOA-P quickstarts configured to run OOTB from JBDS. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Issue Comment Edited: (JBDS-1819) Configure SOA-P quickstarts to be run OOTB in JBDS 4.1.1 with SOA-P 5.2

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-1819?page=com.atlassian.jira.plugin.... ] Len DiMaggio edited comment on JBDS-1819 at 9/21/11 5:21 PM: ------------------------------------------------------------- One more thing we need to document - this client: helloworld_mail_testclient The install of the helloworld_mail quickstart reports compile/import errors for: import javax.mail.Message; import javax.mail.Message.RecipientType; import javax.mail.MessagingException; import javax.mail.PasswordAuthentication; import javax.mail.Session; import javax.mail.Transport; import javax.mail.URLName; import javax.mail.internet.AddressException; import javax.mail.internet.InternetAddress; import javax.mail.internet.MimeMessage; Unless the user adds JavaMail (mail.jar) to the build path. It's an optional package so some users may not have it installed. was (Author: ldimaggio): One more thing we need to document - this client: helloworld_mail_testclient Won't compile unless the user adds JavaMail (mail.jar) to the build path. It's an optional package so some users may not have it installed. > Configure SOA-P quickstarts to be run OOTB in JBDS 4.1.1 with SOA-P 5.2 > ----------------------------------------------------------------------- > > Key: JBDS-1819 > URL: https://issues.jboss.org/browse/JBDS-1819 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Security Level: Public(Everyone can see) > Components: SOA Platform > Affects Versions: 4.1.0.CR3 > Reporter: Len DiMaggio > Assignee: Brian Fitzpatrick > Fix For: 4.1.1.M1 > > Attachments: bfitzpat_examples.png, product_examples.png, runtimes.png > > > Need to ensure there are sample ESB quickstarts available to run cleanly with SOA-P 5.2 on JBDS 4.1.1 > Was: > Need to verify that all JBDS supplied sample ESB quickstarts run cleanly with SOA-P 5.2 on JBDS 4.1.1 > Was: > This subject comes up now and then - it would be very useful to new users to have the full set of SOA-P quickstarts configured to run OOTB from JBDS. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBDS-1819) Configure SOA-P quickstarts to be run OOTB in JBDS 4.1.1 with SOA-P 5.2

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-1819?page=com.atlassian.jira.plugin.... ] Len DiMaggio commented on JBDS-1819: ------------------------------------ One more thing we need to document - this client: helloworld_mail_testclient Won't compile unless the user adds JavaMail (mail.jar) to the build path. It's an optional package so some users may not have it installed. > Configure SOA-P quickstarts to be run OOTB in JBDS 4.1.1 with SOA-P 5.2 > ----------------------------------------------------------------------- > > Key: JBDS-1819 > URL: https://issues.jboss.org/browse/JBDS-1819 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Security Level: Public(Everyone can see) > Components: SOA Platform > Affects Versions: 4.1.0.CR3 > Reporter: Len DiMaggio > Assignee: Brian Fitzpatrick > Fix For: 4.1.1.M1 > > Attachments: bfitzpat_examples.png, product_examples.png, runtimes.png > > > Need to ensure there are sample ESB quickstarts available to run cleanly with SOA-P 5.2 on JBDS 4.1.1 > Was: > Need to verify that all JBDS supplied sample ESB quickstarts run cleanly with SOA-P 5.2 on JBDS 4.1.1 > Was: > This subject comes up now and then - it would be very useful to new users to have the full set of SOA-P quickstarts configured to run OOTB from JBDS. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-9671) Set up a mirror for WTP 3.2.5 integration build

by Fred Bricon (JIRA)

Set up a mirror for WTP 3.2.5 integration build ----------------------------------------------- Key: JBIDE-9671 URL: https://issues.jboss.org/browse/JBIDE-9671 Project: Tools (JBoss Tools) Issue Type: Task Components: Build/Releng Affects Versions: 3.3.0.M2 Reporter: Fred Bricon Assignee: Nick Boldt Fix For: 3.3.0.M4 I need the latest 3.3.1 build for WTP in order to fix some [Dali issue|https://issues.sonatype.org/browse/MECLIPSEWTP-11] in upcoming m2e-wtp 0.14.0. Problem is there's no public update site for the current dev build. So ideally, I'd need to use a mirror of say, the latest 3.3.1 dev build from http://download.eclipse.org/webtools/downloads/ -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

3
11
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 September 2011