March 2010 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBDS-806) Maven integration is added

by OLga Chikvina (JIRA)

Maven integration is added -------------------------- Key: JBDS-806 URL: https://jira.jboss.org/jira/browse/JBDS-806 Project: Developer Studio Issue Type: Sub-task Components: documentation Affects Versions: 2.0.0.GA Reporter: OLga Chikvina Assignee: OLga Chikvina Fix For: 2.1.0 Add the description on the new functionality -- 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

16 years

3
12
0 / 0

[JBoss JIRA] Created: (JBDS-467) Seminar on WS

by Svetlana mukhina (JIRA)

Seminar on WS ------------- Key: JBDS-467 URL: https://jira.jboss.org/jira/browse/JBDS-467 Project: Developer Studio Issue Type: Sub-task Components: Doc - JBossWS Affects Versions: 1.1.0.GA Reporter: Svetlana mukhina Assignee: Anastasiya Bogachuk Fix For: 2.0.0.beta1 Prepare presentation and seminar on WS Jboss Tools -- 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

16 years

2
6
0 / 0

[JBoss JIRA] Created: (JBDS-952) Riftsaw samples are added to the JBT Project Examples wizard offerings

by Svetlana mukhina (JIRA)

Riftsaw samples are added to the JBT Project Examples wizard offerings ---------------------------------------------------------------------- Key: JBDS-952 URL: https://jira.jboss.org/jira/browse/JBDS-952 Project: JBoss Developer Studio Issue Type: Task Components: Doc - VisualWebTools, Doc - RHDS GSG Affects Versions: 2.1.0 Reporter: Svetlana mukhina Assignee: Svetlana mukhina Fix For: 2.1.0-doc update the chapters on examples, see the linked tasks -- 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

16 years

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-5206) Create FreeMarker Template builder for generating XML messages (from XML Sample message)

by Tom Fennelly (JIRA)

Create FreeMarker Template builder for generating XML messages (from XML Sample message) ----------------------------------------------------------------------------------------- Key: JBIDE-5206 URL: https://jira.jboss.org/jira/browse/JBIDE-5206 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: smooks Reporter: Tom Fennelly Fix For: 3.1.0.CR1 -- 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

16 years

3
5
0 / 0

[JBoss JIRA] Created: (JBDS-1169) PicketLink Integration with SOA-P5 (JBDS ESB XML Tooling plus Action design)

by Gary Lamperillo (JIRA)

PicketLink Integration with SOA-P5 (JBDS ESB XML Tooling plus Action design) ---------------------------------------------------------------------------- Key: JBDS-1169 URL: https://jira.jboss.org/jira/browse/JBDS-1169 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Reporter: Gary Lamperillo With the PicketLink and SOA-P 5 quickstart sample (security_saml), a client requests a web service and immediately receives an acknowledgement back. A more realistic use case would be to request a token and use it for the request using a chainhandler. SOA-P 5 can still be utilized as the intermediate. There are a few additional pieces that are needed. The SOA-P 5 needs a Service which forwards issue requests to PicketLink and then sends the Token client. SOA-P 5 needs another service that validates the tokens in the requests and either forwards the request or logs the exception and send error to the client. Both of these services should be implemented as new actions, and should be available in the ESB Actions as "Security Services". In addition, the current implementation requires smooks to add the assertion to the out going message. While the internal implementation using smooks is fine, it should not be required by the user to deal with these internals. In the new "Security Services" section a "Add Assertion" should be available. -- 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

16 years

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-5925) Creating web service from Maven (m2eclipse) webapp generates unhelpful error

by Brian Fitzpatrick (JIRA)

Creating web service from Maven (m2eclipse) webapp generates unhelpful error ---------------------------------------------------------------------------- Key: JBIDE-5925 URL: https://jira.jboss.org/jira/browse/JBIDE-5925 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 2.1.1 Reporter: Brian Fitzpatrick https://enterprise.redhat.com/issue-tracker/554003 Product: JBoss Developer's Studio 5.1.1.GA When attempting to create a web service in a Maven webapp generated with the m2 Maven plugin (version 0.10.020100209-0800), unable to complete wizard due to the following error: "The JBossWS Web service runtime does not support the service project <project>." in the Web Services step. Steps: 1) Create maven project using archetype webapp 2) Create a wsdl file 3) Create new web service in maven webapp using top-down Web service type This also happens we attempting to create a Web Service Client in a maven project. Thanks for any input. -- 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

16 years

4
13
0 / 0

[JBoss JIRA] Created: (JBDS-1081) <rich:menuItem ... icon="|" /> suggestions are fixed

by Svetlana mukhina (JIRA)

<rich:menuItem ... icon="|" /> suggestions are fixed ----------------------------------------------------- Key: JBDS-1081 URL: https://jira.jboss.org/jira/browse/JBDS-1081 Project: Developer Studio (JBoss Developer Studio) Issue Type: Task Components: Doc - VisualWebTools Affects Versions: 3.0.0.M4-doc Reporter: Svetlana mukhina Assignee: Svetlana mukhina Priority: Minor Fix For: 3.0.0.CR2-doc See weather it was just an suggestion fixing - if yes, check whether we have screens with this particular element - update them. -- 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

16 years

1
2
0 / 0

[JBoss JIRA] Created: (JBIDE-3393) Fix weird output to console during polling

by Rob Stryker (JIRA)

Fix weird output to console during polling ------------------------------------------ Key: JBIDE-3393 URL: https://jira.jboss.org/jira/browse/JBIDE-3393 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: JBossAS Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.0.0.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

16 years

2
8
0 / 0

[JBoss JIRA] Created: (JBDS-901) VPE dialogs were redesign

by Svetlana mukhina (JIRA)

VPE dialogs were redesign -------------------------- Key: JBDS-901 URL: https://jira.jboss.org/jira/browse/JBDS-901 Project: JBoss Developer Studio Issue Type: Task Components: documentation Affects Versions: 2.1.0 Reporter: Svetlana mukhina Assignee: Anastasiya Bogachuk Fix For: 2.1.0-doc Check all the screens with VPE, make sure they are up-to-date, update if necessary according with the linked task. -- 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

16 years

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-4448) error during undeployment: no META-INF/application.xml found

by Rustam Abdullaev (JIRA)

error during undeployment: no META-INF/application.xml found ------------------------------------------------------------ Key: JBIDE-4448 URL: https://jira.jboss.org/jira/browse/JBIDE-4448 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.0.1.GA Reporter: Rustam Abdullaev using deployment option "Use workspace metadata", getting an error each time I try to undeploy my application: 17:19:03,378 INFO [EARDeployer] Undeploying J2EE application, destroy step: file:/D:/workspaces/eclipse/.metadata/.plugins/org.jboss.ide.eclipse.as.core/JBoss_4.2_Server/deploy/echo-ear.ear/ 17:19:03,378 INFO [EARDeployer] Undeployed J2EE application: file:/D:/workspaces/eclipse/.metadata/.plugins/org.jboss.ide.eclipse.as.core/JBoss_4.2_Server/deploy/echo-ear.ear/ 17:19:03,378 INFO [EARDeployer] Init J2EE application: file:/D:/workspaces/eclipse/.metadata/.plugins/org.jboss.ide.eclipse.as.core/JBoss_4.2_Server/deploy/echo-ear.ear/ 17:19:03,378 ERROR [MainDeployer] Could not initialise deployment: file:/D:/workspaces/eclipse/.metadata/.plugins/org.jboss.ide.eclipse.as.core/JBoss_4.2_Server/deploy/echo-ear.ear/ org.jboss.deployment.DeploymentException: No META-INF/application.xml found at org.jboss.deployment.EARDeployer.init(EARDeployer.java:146) at org.jboss.deployment.MainDeployer.init(MainDeployer.java:872) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:809) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy9.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:610) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:194) 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:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) 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:585) at org.jboss.jmx.connector.invoker.InvokerAdaptorService.invoke(InvokerAdaptorService.java:266) at sun.reflect.GeneratedMethodAccessor119.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.jmx.connector.invoker.SerializableInterceptor.invoke(SerializableInterceptor.java:74) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:179) at sun.reflect.GeneratedMethodAccessor118.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:818) at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:419) at sun.reflect.GeneratedMethodAccessor117.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294) at sun.rmi.transport.Transport$1.run(Transport.java:153) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:149) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707) at java.lang.Thread.run(Thread.java:595) -- 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

16 years

3
13
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 March 2010