August 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (TOOLSDOC-383) Technical Review of 7.0 Migration Guide

by Michelle Murray (JIRA)

Michelle Murray created TOOLSDOC-383: ---------------------------------------- Summary: Technical Review of 7.0 Migration Guide Key: TOOLSDOC-383 URL: https://issues.jboss.org/browse/TOOLSDOC-383 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Migration Guide Affects Versions: 4.1.0 Reporter: Michelle Murray Assignee: Michelle Murray Fix For: 4.1.0 Conduct a post release technical review of 7.0 Migration Guide to catch any previously missed technical or copy errors. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-350) Migration Guide 7.0.0 - add screen captures

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-350?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-350: ------------------------------------------ No screen captures necessary at this time. Marking Jira as done. > Migration Guide 7.0.0 - add screen captures > ------------------------------------------- > > Key: TOOLSDOC-350 > URL: https://issues.jboss.org/browse/TOOLSDOC-350 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Migration Guide > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.1.0 > > -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-350) Migration Guide 7.0.0 - add screen captures

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-350?page=com.atlassian.jira.plug... ] Michelle Murray resolved TOOLSDOC-350. -------------------------------------- Resolution: Done > Migration Guide 7.0.0 - add screen captures > ------------------------------------------- > > Key: TOOLSDOC-350 > URL: https://issues.jboss.org/browse/TOOLSDOC-350 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Migration Guide > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.1.0 > > -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-382) Get all JBDS docs on the customer portal moved to RHJBDS page

by Michelle Murray (JIRA)

Michelle Murray created TOOLSDOC-382: ---------------------------------------- Summary: Get all JBDS docs on the customer portal moved to RHJBDS page Key: TOOLSDOC-382 URL: https://issues.jboss.org/browse/TOOLSDOC-382 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Task Security Level: Public (Everyone can see) Components: General documentation issues Affects Versions: 4.1.0 Reporter: Michelle Murray Assignee: Michelle Murray Old JBDS docs are located at: https://access.redhat.com/site/documentation/JBoss_Developer_Studio/ They need to appear under: https://access.redhat.com/site/documentation/Red_Hat_JBoss_Developer_Studio/ -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15318) Import Maven Archetype Project Example ignores JBoss Maven Integration preferences

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15318?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-15318: ---------------------------------- Description: Creating projects out of JBoss Central doesn't enable JBoss Tools features like CDI. This bag is regression of JBIDE-14807 where mandatory execution [Maven->Update Project...] was replaced to update only for projects with "out of date" markers. ArchetypeExamplesWizardPage.finishPage() method disable all configurators before importing projects into workspace and with fix of JBIDE-14807 it leads to new problem when configurators are never being called. was: Creating projects out of JBoss Central doesn't enable JBoss Tools features like CDI. > Import Maven Archetype Project Example ignores JBoss Maven Integration preferences > ---------------------------------------------------------------------------------- > > Key: JBIDE-15318 > URL: https://issues.jboss.org/browse/JBIDE-15318 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, project-examples > Affects Versions: 4.1.0.Beta2 > Reporter: Denis Golovin > Priority: Critical > Fix For: 4.1.1.Final, 4.2.0.Alpha1 > > > Creating projects out of JBoss Central doesn't enable JBoss Tools features like CDI. > This bag is regression of JBIDE-14807 where mandatory execution [Maven->Update Project...] was replaced to update only for projects with "out of date" markers. ArchetypeExamplesWizardPage.finishPage() method disable all configurators before importing projects into workspace and with fix of JBIDE-14807 it leads to new problem when configurators are never being called. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15318) Import Maven Archetype Project Example ignores JBoss Maven Integration preferences

by Denis Golovin (JIRA)

Denis Golovin created JBIDE-15318: ------------------------------------- Summary: Import Maven Archetype Project Example ignores JBoss Maven Integration preferences Key: JBIDE-15318 URL: https://issues.jboss.org/browse/JBIDE-15318 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven, project-examples Affects Versions: 4.1.0.Beta2 Reporter: Denis Golovin Fix For: 4.1.1.Final, 4.2.0.Alpha1 Creating projects out of JBoss Central doesn't enable JBoss Tools features like CDI. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15318) Import Maven Archetype Project Example ignores JBoss Maven Integration preferences

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15318?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-15318: ---------------------------------- Priority: Critical (was: Major) > Import Maven Archetype Project Example ignores JBoss Maven Integration preferences > ---------------------------------------------------------------------------------- > > Key: JBIDE-15318 > URL: https://issues.jboss.org/browse/JBIDE-15318 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, project-examples > Affects Versions: 4.1.0.Beta2 > Reporter: Denis Golovin > Priority: Critical > Fix For: 4.1.1.Final, 4.2.0.Alpha1 > > > Creating projects out of JBoss Central doesn't enable JBoss Tools features like CDI. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12645) Weld extensions: built in contexts

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12645?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich updated JBIDE-12645: ------------------------------------------ Description: See http://docs.jboss.org/weld/reference/1.1.5.Final/en-US/html/contexts.html... Steps: 1. Import into Eclipse test project /jbosstools-javaee/cdi/tests/org.jboss.tools.cdi.core.test/projects/weld1.1 2. Open Java source src/test/Test.java {code} package test; import javax.enterprise.inject.Default; import javax.inject.Inject; import org.jboss.weld.context.ApplicationContext; import org.jboss.weld.context.ConversationContext; import org.jboss.weld.context.DependentContext; import org.jboss.weld.context.RequestContext; import org.jboss.weld.context.SessionContext; import org.jboss.weld.context.SingletonContext; import org.jboss.weld.context.bound.Bound; import org.jboss.weld.context.bound.BoundConversationContext; import org.jboss.weld.context.bound.BoundRequestContext; import org.jboss.weld.context.bound.BoundSessionContext; import org.jboss.weld.context.ejb.Ejb; import org.jboss.weld.context.ejb.EjbRequestContext; import org.jboss.weld.context.http.Http; import org.jboss.weld.context.http.HttpConversationContext; import org.jboss.weld.context.http.HttpRequestContext; import org.jboss.weld.context.http.HttpSessionContext; import org.jboss.weld.context.unbound.Unbound; public class Test { //Bean @Default DependentContext is injected @Inject DependentContext dependentContext; //Bean @Default ApplicationContext is injected @Inject ApplicationContext applicationContext; //Bean @Default SingletonContext is injected @Inject SingletonContext singletonContext; //Bean @Unbound RequestContext is injected @Inject @Unbound RequestContext unboundRequestContext; //Bean @Bound @Default BoundRequestContext is injected @Inject @Bound RequestContext boundRequestContext; @Inject @Default BoundRequestContext boundRequestContext2; //Bean @Http @Default HttpRequestContext is injected @Inject @Http RequestContext httpRequestContext; @Inject @Default HttpRequestContext httpRequestContext2; //Bean @Ejb @Default EjbRequestContext is injected @Inject @Ejb RequestContext ejbRequestContext; @Inject @Default EjbRequestContext ejbRequestContext2; //Bean BoundConversationContext is injected @Inject @Bound ConversationContext boundConversationContext; @Inject @Default BoundConversationContext boundConversationContext2; //Bean HttpConversationContext is injected @Inject @Http ConversationContext httpConversationContext; @Inject @Default HttpConversationContext httpConversationContext2; //Bean @Bound @Default BoundSessionContext is injected @Inject @Bound SessionContext boundSessionContext; @Inject @Default BoundSessionContext boundSessionContext2; //Bean @Http @Default HttpSessionContext is injected @Inject @Http SessionContext httpSessionContext; @Inject @Default HttpSessionContext httpSessionContext2; //Invalid: 3 beans are available for injection. @Inject RequestContext invalidRequestContext; //Invalid: 2 beans are available for injection. @Inject ConversationContext invalidConversationContext; //Invalid: 2 beans are available for injection. @Inject SessionContext invalidSessionContext; } {code} ASSERT: All injection points are satisfied, for three last injection points multiple beans are available. Open-on opens interfaces for correspondent beans. was:See http://docs.jboss.org/weld/reference/1.1.5.Final/en-US/html/contexts.html... > Weld extensions: built in contexts > ---------------------------------- > > Key: JBIDE-12645 > URL: https://issues.jboss.org/browse/JBIDE-12645 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: CDI extensions > Reporter: Alexey Kazakov > Assignee: Viacheslav Kabanovich > Fix For: 4.2.x > > > See http://docs.jboss.org/weld/reference/1.1.5.Final/en-US/html/contexts.html... > Steps: > 1. Import into Eclipse test project /jbosstools-javaee/cdi/tests/org.jboss.tools.cdi.core.test/projects/weld1.1 > 2. Open Java source src/test/Test.java > {code} > package test; > import javax.enterprise.inject.Default; > import javax.inject.Inject; > import org.jboss.weld.context.ApplicationContext; > import org.jboss.weld.context.ConversationContext; > import org.jboss.weld.context.DependentContext; > import org.jboss.weld.context.RequestContext; > import org.jboss.weld.context.SessionContext; > import org.jboss.weld.context.SingletonContext; > import org.jboss.weld.context.bound.Bound; > import org.jboss.weld.context.bound.BoundConversationContext; > import org.jboss.weld.context.bound.BoundRequestContext; > import org.jboss.weld.context.bound.BoundSessionContext; > import org.jboss.weld.context.ejb.Ejb; > import org.jboss.weld.context.ejb.EjbRequestContext; > import org.jboss.weld.context.http.Http; > import org.jboss.weld.context.http.HttpConversationContext; > import org.jboss.weld.context.http.HttpRequestContext; > import org.jboss.weld.context.http.HttpSessionContext; > import org.jboss.weld.context.unbound.Unbound; > public class Test { > //Bean @Default DependentContext is injected > @Inject DependentContext dependentContext; > //Bean @Default ApplicationContext is injected > @Inject ApplicationContext applicationContext; > //Bean @Default SingletonContext is injected > @Inject SingletonContext singletonContext; > //Bean @Unbound RequestContext is injected > @Inject @Unbound RequestContext unboundRequestContext; > //Bean @Bound @Default BoundRequestContext is injected > @Inject @Bound RequestContext boundRequestContext; > @Inject @Default BoundRequestContext boundRequestContext2; > //Bean @Http @Default HttpRequestContext is injected > @Inject @Http RequestContext httpRequestContext; > @Inject @Default HttpRequestContext httpRequestContext2; > > //Bean @Ejb @Default EjbRequestContext is injected > @Inject @Ejb RequestContext ejbRequestContext; > @Inject @Default EjbRequestContext ejbRequestContext2; > //Bean BoundConversationContext is injected > @Inject @Bound ConversationContext boundConversationContext; > @Inject @Default BoundConversationContext boundConversationContext2; > > //Bean HttpConversationContext is injected > @Inject @Http ConversationContext httpConversationContext; > @Inject @Default HttpConversationContext httpConversationContext2; > //Bean @Bound @Default BoundSessionContext is injected > @Inject @Bound SessionContext boundSessionContext; > @Inject @Default BoundSessionContext boundSessionContext2; > //Bean @Http @Default HttpSessionContext is injected > @Inject @Http SessionContext httpSessionContext; > @Inject @Default HttpSessionContext httpSessionContext2; > //Invalid: 3 beans are available for injection. > @Inject RequestContext invalidRequestContext; > //Invalid: 2 beans are available for injection. > @Inject ConversationContext invalidConversationContext; > //Invalid: 2 beans are available for injection. > @Inject SessionContext invalidSessionContext; > } > {code} > ASSERT: All injection points are satisfied, for three last injection points multiple beans are available. > Open-on opens interfaces for correspondent beans. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15314) WS Tester fails to execute test if SOAPAction value is null

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15314?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-15314: ------------------------------------------- Have a fix for this, just need to test further to make sure it doesn't break anything. > WS Tester fails to execute test if SOAPAction value is null > ----------------------------------------------------------- > > Key: JBIDE-15314 > URL: https://issues.jboss.org/browse/JBIDE-15314 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Webservices > Affects Versions: 4.1.0.Final > Reporter: Brian Fitzpatrick > Assignee: Brian Fitzpatrick > Fix For: 4.1.1.Final > > > Discovered while testing the bpm-service quickstart for SwitchYard via the WS Tester. If the SOAP operation in the WSDL includes a SOAP action, the test works just fine. But if it's missing and the WSDL is not SOAP 1.2, it fails. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15314) WS Tester fails to execute test if SOAPAction value is null

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15314?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-15314: ------------------------------------------- After quite a bit of head bashing, it seems there were two issues underlying this problem. First - soapAction is not required, it just can't be null. So setting the WS Tester code internally to use an empty string for it worked great. Second, the operation name was namespace prefixed - like "ns2:myoperation" - and when I'm looking through the WSDL for the various bits I need to invoke the service on the server, I just need to strip off the namespace prefix and try comparing it that way. > WS Tester fails to execute test if SOAPAction value is null > ----------------------------------------------------------- > > Key: JBIDE-15314 > URL: https://issues.jboss.org/browse/JBIDE-15314 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Webservices > Affects Versions: 4.1.0.Final > Reporter: Brian Fitzpatrick > Assignee: Brian Fitzpatrick > Fix For: 4.1.1.Final > > > Discovered while testing the bpm-service quickstart for SwitchYard via the WS Tester. If the SOAP operation in the WSDL includes a SOAP action, the test works just fine. But if it's missing and the WSDL is not SOAP 1.2, it fails. -- 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, 8 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 August 2013