[JBoss JIRA] (JBDS-2445) Messaging for JPP 6 in JBDS plugin
by Divya Mehra (JIRA)
Divya Mehra created JBDS-2445:
---------------------------------
Summary: Messaging for JPP 6 in JBDS plugin
Key: JBDS-2445
URL: https://issues.jboss.org/browse/JBDS-2445
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: P2 Enabled Product
Affects Versions: 6.0.0.GA
Environment: All
Reporter: Divya Mehra
Priority: Minor
Starting from GateIn 3.5/JPP 6.0, Maven quick starts would be the recommended way to bootstrap a portal project.
Older technology, for example JSF 1.2 and Rich Faces 3 portlets, would not work if deployed on GateIn 3.5/JPP 6.0 (or later versions).
It is desirable that we message prominently in the JBDS plugin for portal that the developer should use the quick starts (instead of the plugin) for deployments on GateIn 3.5/JPP 6.0 or later versions.
--
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
13 years, 5 months
[JBoss JIRA] (JBIDE-13373) Allow to specify modeshape repository from commad
by Andrej Podhradsky (JIRA)
Andrej Podhradsky created JBIDE-13373:
-----------------------------------------
Summary: Allow to specify modeshape repository from commad
Key: JBIDE-13373
URL: https://issues.jboss.org/browse/JBIDE-13373
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: QA
Reporter: Andrej Podhradsky
Assignee: Andrej Podhradsky
Fix For: 4.0.0.Final
So far, the modeshape repository is hardcoded. Since different modeshape distributions contain different repositories it would be great to have possibility to specify the repository from command line.
For example:
as-5.1 + modeshape 2.8.3 uses 'repository'
but
as-7.1 + modeshape 3.0.1 uses 'sample'
or
soa-5.3 + eds-5.3 uses 'eds
--
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
13 years, 5 months
[JBoss JIRA] (JBIDE-13373) Allow to specify modeshape repository from commad line
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13373?page=com.atlassian.jira.plugi... ]
Andrej Podhradsky updated JBIDE-13373:
--------------------------------------
Summary: Allow to specify modeshape repository from commad line (was: Allow to specify modeshape repository from commad)
> Allow to specify modeshape repository from commad line
> ------------------------------------------------------
>
> Key: JBIDE-13373
> URL: https://issues.jboss.org/browse/JBIDE-13373
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: QA
> Reporter: Andrej Podhradsky
> Assignee: Andrej Podhradsky
> Fix For: 4.0.0.Final
>
>
> So far, the modeshape repository is hardcoded. Since different modeshape distributions contain different repositories it would be great to have possibility to specify the repository from command line.
> For example:
> as-5.1 + modeshape 2.8.3 uses 'repository'
> but
> as-7.1 + modeshape 3.0.1 uses 'sample'
> or
> soa-5.3 + eds-5.3 uses 'eds
--
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
13 years, 5 months
[JBoss JIRA] (JBIDE-12347) Unable to invoke SOAP web service when using Java 7
by Jaroslav Jankovič (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12347?page=com.atlassian.jira.plugi... ]
Jaroslav Jankovič commented on JBIDE-12347:
-------------------------------------------
Well, I am not able to test all SOAP 1.1 service, but yeah, I believe that all SOAP 1.1 service invocations fail.
> Unable to invoke SOAP web service when using Java 7
> ---------------------------------------------------
>
> Key: JBIDE-12347
> URL: https://issues.jboss.org/browse/JBIDE-12347
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Webservices
> Affects Versions: 3.3.1
> Environment: Java 7
> Reporter: Jaroslav Jankovič
> Assignee: Brian Fitzpatrick
> Fix For: 4.0.1.Final
>
>
> I am unable to invoke SOAP web service in WS Tester from http://www.webservicex.net/BibleWebservice.asmx?WSDL.
> In Response Body of WS Tester I got the message:
> {code}
> javax.xml.ws.soap.SOAPFaultException: System.Web.Services.Protocols.SoapException: Server did not recognize the value of HTTP Header SOAPAction: .
> at System.Web.Services.Protocols.Soap11ServerProtocolHelper.RouteRequest()
> at System.Web.Services.Protocols.SoapServerProtocol.RouteRequest(SoapServerMessage message)
> at System.Web.Services.Protocols.SoapServerProtocol.Initialize()
> at System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type, HttpContext context, HttpRequest request, HttpResponse response, Boolean& abortProcessing)
> {code}
> In error log I got the error:
> {code}
> java.lang.Exception: javax.xml.ws.soap.SOAPFaultException: System.Web.Services.Protocols.SoapException: Server did not recognize the value of HTTP Header SOAPAction: .
> at System.Web.Services.Protocols.Soap11ServerProtocolHelper.RouteRequest()
> at System.Web.Services.Protocols.SoapServerProtocol.RouteRequest(SoapServerMessage message)
> at System.Web.Services.Protocols.SoapServerProtocol.Initialize()
> at System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type, HttpContext context, HttpRequest request, HttpResponse response, Boolean& abortProcessing)
> at org.jboss.tools.ws.ui.utils.JAXWSTester2.doTest(JAXWSTester2.java:205)
> at org.jboss.tools.ws.ui.views.JAXRSWSTestView2.handleWSTest(JAXRSWSTestView2.java:1803)
> at org.jboss.tools.ws.ui.views.JAXRSWSTestView2.access$34(JAXRSWSTestView2.java:1789)
> at org.jboss.tools.ws.ui.views.JAXRSWSTestView2$21.run(JAXRSWSTestView2.java:1706)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> Caused by: javax.xml.ws.soap.SOAPFaultException: System.Web.Services.Protocols.SoapException: Server did not recognize the value of HTTP Header SOAPAction: .
> at System.Web.Services.Protocols.Soap11ServerProtocolHelper.RouteRequest()
> at System.Web.Services.Protocols.SoapServerProtocol.RouteRequest(SoapServerMessage message)
> at System.Web.Services.Protocols.SoapServerProtocol.Initialize()
> at System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type, HttpContext context, HttpRequest request, HttpResponse response, Boolean& abortProcessing)
> at com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:178)
> at com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:111)
> at com.sun.xml.internal.ws.client.dispatch.DispatchImpl$DispatchAsyncInvoker$1.onCompletion(DispatchImpl.java:450)
> at com.sun.xml.internal.ws.client.Stub$1.onCompletion(Stub.java:381)
> at com.sun.xml.internal.ws.api.pipe.Fiber.completionCheck(Fiber.java:502)
> at com.sun.xml.internal.ws.api.pipe.Fiber.run(Fiber.java:420)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:722)
> {code}
--
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
13 years, 5 months
[JBoss JIRA] (JBIDE-13322) Add JBossAS 7.x configuration schemas to eclipse xml catalog
by Samuli Saarinen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13322?page=com.atlassian.jira.plugi... ]
Samuli Saarinen commented on JBIDE-13322:
-----------------------------------------
I was thinking of the schemas of the various subsystems (jboss-as-logging_1_1.xsd, jboss-as-datasources_1_1.xsd etc..). I don't know If there is an easier way to add these using Eclipse but what I have done currently is added these via Preferences > XML catalog > Add.. > Catalog Entry, for every xsd used in standalone.xml. It's pretty tedious as there is quite alot of these subsystem schemas.
> Add JBossAS 7.x configuration schemas to eclipse xml catalog
> ------------------------------------------------------------
>
> Key: JBIDE-13322
> URL: https://issues.jboss.org/browse/JBIDE-13322
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: JBossAS/Servers
> Reporter: Samuli Saarinen
> Assignee: Rob Stryker
> Fix For: 4.1.0.Alpha1
>
>
> JBAS7 configuration schemas could be added to Eclipse XML catalog. This way developer wanting to edit eg. standalone.xml could get auto-complete without the need to import all the schemas by hand.
--
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
13 years, 5 months
[JBoss JIRA] (JBIDE-8530) Message Driven Bean (EJB3.x) wizard generates incorrect annotattions
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-8530?page=com.atlassian.jira.plugin... ]
Rob Stryker resolved JBIDE-8530.
--------------------------------
Fix Version/s: 4.0.2.Final
(was: 4.0.x)
Resolution: Done
This will be bundled in the wtp 3.4.2 release. It was pushed to wtp maintenance on Kaloyan Raev 2012-10-04 04:49:22 EDT.
The final generated text is as follows:
@MessageDriven(
activationConfig = { @ActivationConfigProperty(
propertyName = "destinationType", propertyValue = "javax.jms.Queue"), @ActivationConfigProperty(
propertyName = "destination", propertyValue = "queue")
},
mappedName = "queue")
public class MyBean3 implements MessageListener {
public MyBean3() {
}
public void onMessage(Message message) {
}
}
The annotations compile correctly. mappedNAme="queue" was left there as legacy for other adopters who still needed it and demanded it not be removed.
This is the final text. Unless there is a severe issue making this generated text a failure, then this will most likely not be revisited.
> Message Driven Bean (EJB3.x) wizard generates incorrect annotattions
> --------------------------------------------------------------------
>
> Key: JBIDE-8530
> URL: https://issues.jboss.org/browse/JBIDE-8530
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: ejb3
> Affects Versions: 3.2.0.Final
> Reporter: Libor Zoubek
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.0.2.Final
>
>
--
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
13 years, 5 months
[JBoss JIRA] (JBIDE-10525) server editor Server behavior expansion too tall
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-10525?page=com.atlassian.jira.plugi... ]
Rob Stryker reassigned JBIDE-10525:
-----------------------------------
Assignee: Snjezana Peco (was: Rob Stryker)
Hey Snjezana,
you're always willing to take on a quick task, and this one's been bugging me for a long time. I can't seem to shrink that widget. I can change the exact size, sure, but then the rse or local widgets inside may not be proper.
Was trying to squeeze it into a smaller space but enable a scroll bar and have it look good in local and rse mode, but have been stuck on it for a very long time.
Any thoughts?
> server editor Server behavior expansion too tall
> ------------------------------------------------
>
> Key: JBIDE-10525
> URL: https://issues.jboss.org/browse/JBIDE-10525
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Affects Versions: 3.3.0.M5
> Reporter: Martin Malina
> Assignee: Snjezana Peco
> Priority: Minor
> Fix For: 4.0.x
>
> Attachments: server-behavior-white-space.jpg
>
>
> Cloned from JBIDE-10117 since this issue is similar. (Probably should have created a new issue, but too late now.)
> When Server Behavior is expanded, it is too tall - there is a lot of blank space at the bottom. See screenshot. This happens only when the server is set to Local.
--
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
13 years, 5 months
[JBoss JIRA] (JBIDE-13371) test failure in org.jboss.ide.eclipse.as.test.server.XPathModelTest.testEap60Mock (from org.jboss.ide.eclipse.as.test.ASTestSuite) : The XPath File has not been created. Xpaths will be lost on workspace restart
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13371?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-13371.
---------------------------------
Fix Version/s: 4.1.0.Alpha1
(was: 3.3.2)
Resolution: Done
You also received this error in https://issues.jboss.org/browse/JBDS-2394
It seems to be an intermitent bug. I will not fix it in 3.3.x but I will try to adjust the test in master. Specifically, I will move the test from the as.core.test into the new parametized test suite, adn will add some protections such as changing the server name (to ensure cleanup of one test running concurrently with creation of next doesn't cause a problem).
> test failure in org.jboss.ide.eclipse.as.test.server.XPathModelTest.testEap60Mock (from org.jboss.ide.eclipse.as.test.ASTestSuite) : The XPath File has not been created. Xpaths will be lost on workspace restart
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13371
> URL: https://issues.jboss.org/browse/JBIDE-13371
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Affects Versions: 3.3.2
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Fix For: 4.1.0.Alpha1
>
>
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_5.0.indigo/job/jbosstools-3.3_stable_branch.component--as/lastCompletedBuild/testReport/org.jboss.ide.eclipse.as.test.server/XPathModelTest/testEap60Mock/}
> Regression
> org.jboss.ide.eclipse.as.test.server.XPathModelTest.testEap60Mock (from org.jboss.ide.eclipse.as.test.ASTestSuite)
> Failing for the past 1 build (Since Unstable#152 )
> Took 30 ms.
> add description
> Error Message
> The XPath File has not been created. Xpaths will be lost on workspace restart
> Stacktrace
> junit.framework.AssertionFailedError: The XPath File has not been created. Xpaths will be lost on workspace restart
> at junit.framework.Assert.fail(Assert.java:47)
> at org.jboss.ide.eclipse.as.test.server.XPathModelTest.serverTestImpl(XPathModelTest.java:31)
> at org.jboss.ide.eclipse.as.test.server.SimpleServerImplTest.testEap60Mock(SimpleServerImplTest.java:61){code}
--
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
13 years, 5 months