Products Products
Support & Forums Support & Forums
Compliance Testing Compliance Testing
Labs & Sandboxes Labs & Sandboxes
Program Program
Co-Marketing Co-Marketing
Avaya Experience Platform Avaya Enterprise Cloud Avaya Client SDK Avaya Aura Platform See All Products Find Developer Resources

Avaya Experience Platform

Overview Interfaces Learning Support Options Compliance Testing

Avaya Enterprise Cloud

Overview Interfaces Learning Support Options Compliance Testing

Avaya Client SDK

Overview Programming Docs Developer Downloads Licensing Support & Testing

Avaya Aura Platform

Application Enablement Services Communication Manager Presence Services Snap-in Session Manager System Manager Session Border Controller
About DevConnect Support Submit Support Tickets Support Forums Other Support Options

About DevConnect Support

Support Options Support FAQs Supported Platforms and Interfaces

Submit Support Tickets

Procured System Support
For procurement issues or questions Remote Lab Support
For issues and questions related to DevConnect remote labs Membership & Program Support
For membership and program benefits questions General Support
For general issues not covered by the other support tickets

Support Forums

Avaya Client SDK AEServices DMCC APIs AEServices JTAPI AEServices Web Services Avaya Workspaces Avaya Experience Platform Orchestration Designer All Forums

Other Support Options

Product Notices Non-DevConnect Support Resources

Compliance Testing

About Compliance Testing Compliance Tested Solutions

About Compliance Testing

Compliance Testing Overview Avaya Interfaces Eligible For Testing Compliance Testing FAQs Compliance Testing Guide(s) (PDF)

Compliance Tested Solutions

DevConnect Marketplace Search Applications Notes

Labs & Sandboxes

Remote Labs Procurement Benefits

Remote Labs

Remote Labs Overview Avaya Aura Session Manager Avaya Aura AE Services & Communication Manager Self Services (Experience Portal) Avaya Proactive Outreach Manager Avaya Contact Center Elite

Procurement Benefits

About DevConnect Procurement Access/View Procurement Catalog Procurement FAQs DevConnect Procured System Support

Program

Program Overview Program Benefits Membership Options

Program Overview

DevConnect Membership Levels DevConnect Program Guide (PDF) DevConnect Program FAQs

Program Benefits

Membership Benefits DevConnect Procurement Co-marketing

Membership Options

Manage My Portfolio/Solutions Manage My Profile

Co-Marketing

Co-Marketing Benefits Relationship Benefits

Co-Marketing Benefits

Co-Marketing Overview Logos Marketplace Co-branded Collateral Select Product Program

Relationship Benefits

Social Media 8-and-Out Podcasts Sponsorships Advertising

Author Message
16/02/2015 16:23:07
Subject: Orchestration Designer and Java 1.8
#1
DustinFlegel
Joined: Aug 22, 2014
Messages: 10
Offline
Hi, this is my first time posting in the forums. Our company has required that we use Java 1.8 moving foward, so I have gone through the efforts of upgrading to a newer version of Eclipse that supports Java 1.8. Everything seems to work, except for web services. When I right-click on a web service and select Properties > Generate Client, and press the Generate button, nothing happens. I went to my workspace > .metadata > .log, I see the following error, but I'm unable to find a plugin or componenent to resolve this issue. Has anyone else tried to upgrade to Kepler or Luna with success?

I also have an issue while attempting to create a new web service, that indicates there's an issue with the WSDL, but if I go back to Eclipse Indigo and perform the same action, there are no issues with creating the web service reference.

Here's the error I get with the Generate option
!ENTRY org.eclipse.ui 4 0 2015-02-16 15:07:49.473
!MESSAGE Unhandled event loop exception
!STACK 0
java.lang.NoSuchMethodError: org.eclipse.ui.internal.WorkbenchPage.getEditorManager()Lorg/eclipse/ui/internal/EditorManager;
at com.avaya.sce.ws.ui.properties.WebServicePropertyPage$1.widgetSelected(WebServicePropertyPage.java:87)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4353)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4172)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:832)
at org.eclipse.jface.window.Window.open(Window.java:808)
at org.eclipse.ui.dialogs.PropertyDialogAction.run(PropertyDialogAction.java:160)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:519)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4353)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4172)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
at org.eclipse.equinox.launcher.Main.run(Main.java:1465)


Here's the error I get when I try to create a new reference to a web service. Not sure why this works in a previous version, and not a newer version.

!ENTRY com.avaya.sce.ws.ui 4 0 2015-02-16 15:16:53.372
!MESSAGE Unable to access WSDL in URL https://localhost/IVR.svc?wsdl. You may need to configure a proxy in the Orchestration Designer preferences, or the WSDL file is invalid.
!STACK 0
java.lang.RuntimeException: javax.wsdl.WSDLException: WSDLException (at /wsdl:definitions/wsdl:types/xsd:schema): faultCode=OTHER_ERROR: An error occurred trying to resolve schema referenced at 'https://localhost/IVR.svc?xsd=xsd0', relative to 'https://localhost/IVR.svc?wsdl'.: java.io.IOException: Server returned HTTP response code: 401 for URL: https://localhost/IVR.svc?xsd=xsd0
at com.avaya.sce.ws.internal.WSDLDescriptor$1.run(WSDLDescriptor.java:135)
at com.avaya.ade.common.core.utils.TimedCancelableOperation.run(TimedCancelableOperation.java:116)
Caused by: javax.wsdl.WSDLException: WSDLException (at /wsdl:definitions/wsdl:types/xsd:schema): faultCode=OTHER_ERROR: An error occurred trying to resolve schema referenced at 'https://localhost/IVR.svc?xsd=xsd0', relative to 'https://localhost/IVR.svc?wsdl'.: java.io.IOException: Server returned HTTP response code: 401 for URL: https://localhost/IVR.svc?xsd=xsd0
at com.ibm.wsdl.xml.WSDLReaderImpl.parseSchema(Unknown Source)
at com.ibm.wsdl.xml.WSDLReaderImpl.parseSchema(Unknown Source)
at com.ibm.wsdl.xml.WSDLReaderImpl.parseTypes(Unknown Source)
at com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(Unknown Source)
at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:516)
at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:495)
at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:361)
at java.lang.Thread.run(Unknown Source)
Caused by: java.io.IOException: Server returned HTTP response code: 401 for URL: https://localhost/IVR.svc?xsd=xsd0
at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(Unknown Source)
at java.net.URL.openStream(Unknown Source)
at com.ibm.wsdl.util.StringUtils.getContentAsInputStream(Unknown Source)
... 11 more


Any assistance would be greatly appreciated. Thanks!

Dustin
PM
16/02/2015 19:02:52
Subject: Re:Orchestration Designer and Java 1.8
#2
WilsonYu
Joined: Nov 6, 2013
Messages: 3950
Offline
We do not support Luna or Kelper. You do not have to upgrade even you use Java 1.8. This is the error we have to fix when we start supporting Kelper in the next release.
PM
16/02/2015 19:15:09
Subject: Re:Orchestration Designer and Java 1.8
#3
DustinFlegel
Joined: Aug 22, 2014
Messages: 10
Offline
I appreciate your prompt reply. I am unable to get Eclipse Indigo to use Java 1.8, I would greatly appreciate some direction on how to use Java 1.8 with Eclipse Indigo, or is there another version of Eclipse I should be using? Our company is requiring the removal of Java 7 from all of our workstations. I'm quite new to the Eclipse environment, so a little guidance is needed here.

Thanks!
  • [Thumb - Whereisjava8.png]
[Disk] Download
PM
16/02/2015 19:24:22
Subject: Re:Orchestration Designer and Java 1.8
#4
WilsonYu
Joined: Nov 6, 2013
Messages: 3950
Offline
I don't expect you to be able to build your projects in Java 1.8 since Indigo does not give you the option to do that. You can still run Eclipse using Java 1.8, and compile the project with Java 1.7 compliance. The the project will run on Java 1.8 runtime with whatever app server we support. That's all you can do for now.
PM
16/02/2015 20:04:24
Subject: Re:Orchestration Designer and Java 1.8
#5
DustinFlegel
Joined: Aug 22, 2014
Messages: 10
Offline
Excellent. Thank you for your assistance with this, WilsonYu.
PM
16/02/2015 20:48:08
Subject: Re:Orchestration Designer and Java 1.8
#6
DustinFlegel
Joined: Aug 22, 2014
Messages: 10
Offline
Hi -- I just removed Java 7 from the system, specified Java 8 in Eclipse as the JRE and now I'm receiving errors on simple things like String.replace. There's a question similar to mine on Stack Overflow found here:
http://stackoverflow.com/questions/24301986/the-type-java-lang-charsequence-cannot-be-resolved-in-package-declaration

Since Eclipse Indigo cannot specify Java 1.8 in the section previously mentioned, does this mean that I won't be able to develop with AAOD 7 using Java 8 at all? If there are no workarounds, how soon can we expect an update? We just purchased our Avaya platform, there must be something we can do.
PM
16/02/2015 22:12:11
Subject: Re:Orchestration Designer and Java 1.8
#7
WilsonYu
Joined: Nov 6, 2013
Messages: 3950
Offline
AAOD 7 does not support Java 1.8 to begin with. That means we've not done any testing with Java 1.8. You are at your own risk trying what you can do with Java 1.8. If that does not workout, you have to go back to Java 1.7.
To me, you develop the app using Java 1.7 but you should be able to run the app on Java 1.8 runtime with whatever app server that supports it because Java is always backward compatible. Not sure why you have to build your app on Java 1.8. There is nothing I can do if that does not work out.
Our OD 8 is not due to release until next year.
If what I said doesn't jive with your purchase agreement, please contact Avaya support.
PM
16/02/2015 22:26:04
Subject: Re:Orchestration Designer and Java 1.8
#8
DustinFlegel
Joined: Aug 22, 2014
Messages: 10
Offline
I appreciate your direct response. Removal of Java 1.7 is a security requirement for us. Thanks for your time.
PM
Go to:   
Mobile view