[500]SSO error:null
Hi..
I finished the vSphere Web Client SDK Setup ,after starting my virgo server i get the following error when i open the link https://localhost:9443/vsphere-client/.
A server error occured.
[500]SSO error:null
Check the vsphere webclient server logs for details.
Can you please help me,i am stuck here.
Regards
srini
These are the Errors that i see in the log generated in the path vsphere-client-sdk-6\server\serviceability\logs of the development machine.
[ERROR] system-artifacts org.apache.catalina.mbeans.GlobalResourcesLifecycleListener No global naming context defined for server
[ERROR] cm-catalog-manager-pool-5 com.vmware.vim.sso.client.impl.SoapBindingImpl The SSL certificate of STS service cannot be verified
[ERROR] cm-catalog-manager-pool-5 com.vmware.vise.vim.security.sso.impl.NgcSolutionUser Login as solution user failed.
[ERROR] http-bio-9443-exec-1 70000001 100001 ###### com.vmware.vim.sso.client.impl.SoapBindingImpl The SSL certificate of STS service cannot be
[ERROR] http-bio-9443-exec-1 70000001 100001 ###### com.vmware.vise.vim.security.sso.impl.NgcSolutionUser Login as solution user failed.
[ERROR] http-bio-9443-exec-1 70000001 100001 ###### com.vmware.vsphere.client.security.websso.MetadataGeneratorImpl Error when registering ngc metadata.
[ERROR] ing.timer.TimerFactoryBean#0 com.vmware.vim.sso.client.impl.SoapBindingImpl The SSL certificate of STS service cannot be verified
[ERROR] ing.timer.TimerFactoryBean#0 com.vmware.vise.vim.security.sso.impl.NgcSolutionUser Login as solution user failed.
[ERROR] ing.timer.TimerFactoryBean#0 com.vmware.vise.vim.cm.healthstatus.InventoryServiceHealth Search failed for Health Status
[ERROR] ing.timer.TimerFactoryBean#0 com.vmware.vise.vim.cm.healthstatus.InventoryServiceHealth Could not find Health Status EndPoint for Inventory Service
Regards
Srini
Similar Messages
-
Error 500 Java.Lang.Null.Pointer Exception
Please help me:
I have problem with starting my portlet under portal.
Provider is registred correctly ,portlet is added corectly on
Portal Page ,but when I test my page I have :
The Listener Returned the folowing message-
Error 500 Java.Lang.Null.Pointer Exception
Note:Portlet is compiled in JDeveloper 2.0 and there look Ok.
Thankswe encountered the same error on aix4.3.3. in fact the error comes from a variable, that has not been initialized, jserv error log says the following:
[07/11/2001 10:00:54:098 GMT+00:00] esvportal/init
[07/11/2001 10:01:08:668 GMT+00:00] esvportal/Response status: 500 : java.lang.NullPointerException
at oracle.portal.provider.v1.http.ServletProviderRequest.getAcceptLanguage(ServletProviderRequest.java:162)
at oracle.portal.provider.v1.http.ServletProviderResponse.showPortlet(ServletProviderResponse.java:521)
at oracle.portal.provider.v1.http.HttpProvider.dispatchProviderAction(HttpProvider.java:662)
at oracle.portal.provider.v1.http.HttpProvider.service(HttpProvider.java:391)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:588)
at org.apache.jserv.JServConnection.processRequest(JServConnection.java:402)
at org.apache.jserv.JServConnection.run(JServConnection.java:260)
at java.lang.Thread.run(Thread.java:481)
i habe a public page with 4 jsp portlets and one pl/sql portlet. the plsql ist working, every one of the jsp portlets gets the "getAcceptLanguage" error -
Need help!!!! 500 internal Error ( not replicable)
Hi,
Our application went to production today, few of the users are experiencing "500 internal error"( Not replicable)
again they have to quit browser and login again to start their work again.it was becoming a big issue as its tampering their work.
we tried to replicate the issue in our test system, only way we could replicate is by clicking too fast , before waiting for the response.
(as they used to that speed with their old application)
I tried to disable the buttons,but that couldn't helped much.
today i was monitoring the production logs whole day below are the repeated Exceptions i found.
Error # 1
May 18, 2009 16:28:27,733 ERROR [RMICallHandler-12] ApplyRequestValuesPhase.execute(104) | Error testing property 'selectedChkBox' in bean of type null
javax.faces.el.PropertyNotFoundException: Error testing property 'selectedChkBox' in bean of type nullat com.sun.faces.el.PropertyResolverImpl.isReadOnly(PropertyResolverImpl.java:274)"
Error # 2
javax.faces.el.PropertyNotFoundException: Error testing property 'partNo' in bean of type null
at com.sun.faces.el.PropertyResolverImpl.getType(PropertyResolverImpl.java:362)
we are not able to find the solution to fix these exceptions.. is there any better way to avoid these...
any help is greatly greatly appreciated...!!!
i eagerly waiting for suggestions....
Thanks a lot!
Arthi..Hi BaluC,
Thank you for the response. and how can i make sure that bean is not null
i tried <a4j:keepAlive and <t:saveState value="#{SearchSI_bean}" /> seems not working.
can you please suggest if we have any other option.
if user clicks her and there without waiting for the response we are getting the error
javax.faces.el.PropertyNotFoundException: Error testing property 'selectedChkBox' in bean of type null in logs.. and user is seeing 500 internal error..
this issue is seems growing..
thanks for the help..
Arthi. -
SSO error message when publishing a BI 7.0 report to the NW04s Portal
Please indicate how to resolve the following SSO error message received when publishing a BI 7.0 report from Query Designer to a PCD folder on a NW04s Portal:
Java system error: call FM RSRD_X_MAP_TO_PRTL_USERS_PROXY to ProgId (server alias)_PORTAL_ABV on host (server alias) with SSO not authorized: Authentication fHi,
Please check if the integration and sso configuration did correctly
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b0a5216a-349c-2a10-9baf-9d4797349f6a
Hope it helps.
Regards,
Mona -
Hi everybody,
I have two Distinct Databases on two distinct servers. (Oracle Ent. Release 10.2.0.3.0 on AIX 5.3). After I install the latest patch last week, One of the APEX installation has some problems on Home>Application Builder Page. The error message is very random and
report error:
ORA-06502: PL/SQL: numeric or value error: NULL index table key value.
When i change the view (details to icons), everything goes to normal. This error message is reflected some of the pages (report region) of some of my applications randomly. When it appears in a report region, i deselect the order method of the region, the result is normal.
But the other APEX application on the other instance has no problem. It is a bug? or Should i re-install the APEX instance?
Thank you for your interest?
Gökhan ÇATALKAYANo, but we have a reproducible test case now so we're working on it. See ORA-06502: PL/SQL: numeric or value error: NULL index table key value
Scott -
Oracle SSO error while trying to access a report
Hi All,
I am using Oracle 11g reports and forms.My adf application(using JDeveloper 11.1.1.4) will use oracle reports through url.
From adf application we form a url for the reports like https://<server>:<port>/reports/rwservlet?server=devstage11g&destype=cache&desformat=pdf&report=spore001…
we send the userid parameter as a hidden parameter in the request as we do not want the userid information to be visible in the URL. It works fine in one environment. But in another environment when we hit the url it always give a page with a single line saying "Oracle SSO". When we hit the same url with userid parameter appended to it directly, it works fine.
Checked the configuration difference, but not able to find any difference in the configuration. Please help me to find why it always gives "Oracle SSO" error.
Thanks,
Priya.Hi ;
pelase check below which could be similar error like yours
Troubleshooting of Runtime Errors of Customer Intelligence Reports [ID 284829.1]
Regard
Helios -
HFM Application Library error Null while deploying the validated app
Hello,
I am trying to deploy a HFM application on EPM 11.1.3 and when I right click on the application in Application library of EPMA, I am getting a pop-up with the following error:
Application Library Error
null
Please note:
1. This is a EPMA managed HFM application.
2. The validation of the application is successful.
3. Deployement errors with the above error.
4. It is on Windows 2003 server with MSServer as the RDBMS.
Please help me resolve this issue.
thanks,
AnkitHi Ankit,
This would be normally resolved by Restarting the EPM Services and also remember to restart the Calculation manager services as well.
Once the services are restarted try deploying the application again to see if it deploys successfully.
Hope this helps,
Thank you,
Charles Babu J -
I am getting "Fatal Error: null" when connection to P6v8.3.2 DB using P6 Integration API.
I can connect via P6 client using admin account but cannot connect using P6 API. If I provide invalid credentials it says that the credentials are incorrect. When correct credentials are provided, it comes up with the above error.
Stacktrace is atteched.
Please assist.
Thanks
SunilHi Sunil,
In the absence of sample code it is difficult to identify the cause. If that is not possible, you can try logging SR with Oracle support.
Regards,
Sachin Gupta -
500 internal error in managhe substitution rule in UWL
Hi All,
One user is getting 500 internal error when cklicks on manage substitution rule in UWL.Only one user is facing this problem.
I checked in backend system, so substitute exists.
Can some body help me what could be the problem? Thanks in advance.
Regards,
Thirun.Hi Thirun,
This is a common issue and usually has to do if the 'substitutee' for lack of a better word, is no longer a valid user.
4. When there is a substitution rule connecting the current user to a
deleted user, the following problems were discovered:
- substitution rule management returns 500 browser error;
- it is not possible to delete a Java Workflow substitution which
refers to a deleted user as assignee;
- Java workflow connector is not able to retrieve items for user that
has a substitution rule with a deleted user;
- The "status", "What to do", "assignee" and "Task Owner" fields are
not properly filled in the Manage Substitution Rules view.
Do a search in SAP notes in component EP-BC-UWL and also for your version. Alternatively you can let me know the version here and I can tell you in what release this is fixed in that matches closest to your version. (maybe only a patch required).
Beth Maben
EP - Senior Support Consultant
AGS Primary Support, Business Suite & Technology
Please see the UWL Wiki @
https://www.sdn.sap.com/irj/scn/wiki?path=/display/bpx/uwl+faq *** -
Hi,
I am trying toceate an interface which collects data from database make some transformation and populated seeded tables in the same database.
My Approach is :
a) Create a record type variable ( concists of multiple segments)
b) Create a pl/sql table type of the records type in a)
c) Created a cursor of same structure as pl/sql table type ( collects data)
d) BULK CoLLECT data from cursor into pl/sql table
e) Print the data
But during Bulk Collect i get the below error :
Unexpected error in xxc_hr2hr_populate_elements.main at FLOW TRACE-1.120. Error: ORA-06502: PL/SQL: numeric or value error: NULL index table key value
ORA-20003: Unexpected error in xxc_hr2hr_populate_elements.get_data at FLOW TRACE-1.1.100. Error: ORA-06502: PL/SQL: numeric or value error: Bulk Bind: Truncated BindAshish_Apps wrote:
Hi,
I am trying toceate an interface which collects data from database make some transformation and populated seeded tables in the same database.
My Approach is :
a) Create a record type variable ( concists of multiple segments)
b) Create a pl/sql table type of the records type in a)
c) Created a cursor of same structure as pl/sql table type ( collects data)
d) BULK CoLLECT data from cursor into pl/sql table
e) Print the data
But during Bulk Collect i get the below error :
Unexpected error in xxc_hr2hr_populate_elements.main at FLOW TRACE-1.120. Error: ORA-06502: PL/SQL: numeric or value error: NULL index table key value
ORA-20003: Unexpected error in xxc_hr2hr_populate_elements.get_data at FLOW TRACE-1.1.100. Error: ORA-06502: PL/SQL: numeric or value error: Bulk Bind: Truncated BindVerify the rows you are fetching are having the same data types as your Record like Dates should go to date , decimal should not be fetched in type defined as number etc. -
OBIEE 11G - BI Publisher returning 500 internal error
Hi,
One of the user is getting the 500 internal error wheever she tries to view the BI Publisher report.
1) It is a single sign-on set up. She is the only one who gets this error.
2) She used her id and logged in some one elses computer and she WAS ABLE to view the BIP reports.
3) It is her computer that gives this error.
How to identify the root cause of the issue? I am thinking it could be one of the software installed in her machine, but which one should I check for?
Please help with suggestions. Thanks for your time and help.You need to setup SA System in order for BI EE security to work with BI Publisher. Setting this up will fix the error that you are listing below. Couple of options for you.
1. Log an SR on supportweb to get sample RPD and table structure for the SA System
2. check the 7.8.x documentation. It had a better description of the SA System than the 10.1.3.2 documentation does.
3. I can email you an RPD and table structure that I have used.
The only thing BIP needs in SA system is user name, group name and user to group assignment. This is needed for two screens in BIP (Roles and Permissions and JDBC connections). It's a bit annoying to have to set this up, but two good things to note. If you setup SA System, then you have additional options for delivery of iBots (that's what SA System is really designed for). The other is that BIP's dependence on SA System is going away in a future release. So this will get easier soon.
Bryan -
500 Server Error when Trying to Download Files
Hi,
I keep getting a 500 server error when trying to download any of the Oracle ORION files: http://www.oracle.com/technology/software/tech/orion/index.html Any ideas? Thank you for your help.
PS. Here's the exact error:
"Server Error
The following error occurred:
[code=SERVER_RESPONSE_RESET] The server response could not be read because of an error. Contact your system administrator.
Please contact the administrator."Thanks. It seems to be fixed now.
-
When trying to access Bell Mobility account I get 500: Server Error [20-0004]. Is this a problem with my mac or their server?
Have you tried on another device?
The folow sugests it is a server issue (not your computer)( but give several actions to confirm that.
http://pcsupport.about.com/od/findbyerrormessage/a/500servererror.htm -
Unable to access OWA or ECP. - "Something went wrong" or "500 unexpected error"
Our environment consist of 3 client access servers with 8 mailbox servers. I recently installed windows updates on all of the servers. Now when a user tries to access OWA it fails and says "Something went wrong" when I try to access
ECP I receive "500 unexpected error"
I have tried building a new CAS and mailbox servers with the default settings but it still fails. I did not install the latest Windows updates on the new servers. I tried creating new databases with new users and it also fails.
There are also these ASP.NET 4.0.30319.0 warnings showing in the application log:
Log Name: Application
Source: ASP.NET 4.0.30319.0
Date: 8/30/2013 11:02:13 AM
Event ID: 1309
Task Category: Web Event
Level: Warning
Keywords: Classic
User: N/A
Computer: FacultyEmail01.corjesu.org
Description:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 8/30/2013 11:02:13 AM
Event time (UTC): 8/30/2013 4:02:13 PM
Event ID: 1088bfe111264e01b536f66f2591c15a
Event sequence: 48245
Event occurrence: 1597
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/2/ROOT/owa-1-130223042171473642
Trust level: Full
Application Virtual Path: /owa
Application Path: C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\owa\
Machine name: FACULTYEMAIL01
Process information:
Process ID: 13764
Process name: w3wp.exe
Account name: NT AUTHORITY\SYSTEM
Exception information:
Exception type: NullReferenceException
Exception message: Object reference not set to an instance of an object.
at Microsoft.Exchange.Clients.Common.Canary15.Init(Byte[] userContextIdBinary, Byte[] timeStampBinary, String logonUniqueKey, Byte[] hashBinary, String logData)
at Microsoft.Exchange.Clients.Common.Canary15..ctor(String logonUniqueKey)
at Microsoft.Exchange.Clients.Common.Canary15Cookie.TryCreateFromHttpCookie(HttpCookie cookie, String logonUniqueKey, Canary15Profile profile)
at Microsoft.Exchange.Clients.Common.Canary15Cookie.TryCreateFromHttpContext(HttpContext httpContext, String logOnUniqueKey, Canary15Profile profile)
at Microsoft.Exchange.Clients.Owa2.Server.Core.OwaRequestHandler.InternalOnPostAuthorizeRequest(Object sender)
at Microsoft.Exchange.Clients.Owa2.Server.Core.OwaRequestHandler.OnPostAuthorizeRequest(Object sender, EventArgs e)
at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
Request information:
Request URL: https://localhost:444/owa/logoff.owa
Request path: /owa/logoff.owa
User host address: 127.0.0.1
User: CORJESU\SM_cab26786a5604c759
Is authenticated: True
Authentication Type: Kerberos
Thread account name: NT AUTHORITY\SYSTEM
Thread information:
Thread ID: 12
Thread account name: NT AUTHORITY\SYSTEM
Is impersonating: False
Stack trace: at Microsoft.Exchange.Clients.Common.Canary15.Init(Byte[] userContextIdBinary, Byte[] timeStampBinary, String logonUniqueKey, Byte[] hashBinary, String logData)
at Microsoft.Exchange.Clients.Common.Canary15..ctor(String logonUniqueKey)
at Microsoft.Exchange.Clients.Common.Canary15Cookie.TryCreateFromHttpCookie(HttpCookie cookie, String logonUniqueKey, Canary15Profile profile)
at Microsoft.Exchange.Clients.Common.Canary15Cookie.TryCreateFromHttpContext(HttpContext httpContext, String logOnUniqueKey, Canary15Profile profile)
at Microsoft.Exchange.Clients.Owa2.Server.Core.OwaRequestHandler.InternalOnPostAuthorizeRequest(Object sender)
at Microsoft.Exchange.Clients.Owa2.Server.Core.OwaRequestHandler.OnPostAuthorizeRequest(Object sender, EventArgs e)
at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
Custom event details:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="ASP.NET 4.0.30319.0" />
<EventID Qualifiers="32768">1309</EventID>
<Level>3</Level>
<Task>3</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-08-30T16:02:13.000000000Z" />
<EventRecordID>721791</EventRecordID>
<Channel>Application</Channel>
<Computer>FacultyEmail01.corjesu.org</Computer>
<Security />
</System>
<EventData>
<Data>3005</Data>
<Data>An unhandled exception has occurred.</Data>
<Data>8/30/2013 11:02:13 AM</Data>
<Data>8/30/2013 4:02:13 PM</Data>
<Data>1088bfe111264e01b536f66f2591c15a</Data>
<Data>48245</Data>
<Data>1597</Data>
<Data>0</Data>
<Data>/LM/W3SVC/2/ROOT/owa-1-130223042171473642</Data>
<Data>Full</Data>
<Data>/owa</Data>
<Data>C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\owa\</Data>
<Data>FACULTYEMAIL01</Data>
<Data>
</Data>
<Data>13764</Data>
<Data>w3wp.exe</Data>
<Data>NT AUTHORITY\SYSTEM</Data>
<Data>NullReferenceException</Data>
<Data>Object reference not set to an instance of an object.
at Microsoft.Exchange.Clients.Common.Canary15.Init(Byte[] userContextIdBinary, Byte[] timeStampBinary, String logonUniqueKey, Byte[] hashBinary, String logData)
at Microsoft.Exchange.Clients.Common.Canary15..ctor(String logonUniqueKey)
at Microsoft.Exchange.Clients.Common.Canary15Cookie.TryCreateFromHttpCookie(HttpCookie cookie, String logonUniqueKey, Canary15Profile profile)
at Microsoft.Exchange.Clients.Common.Canary15Cookie.TryCreateFromHttpContext(HttpContext httpContext, String logOnUniqueKey, Canary15Profile profile)
at Microsoft.Exchange.Clients.Owa2.Server.Core.OwaRequestHandler.InternalOnPostAuthorizeRequest(Object sender)
at Microsoft.Exchange.Clients.Owa2.Server.Core.OwaRequestHandler.OnPostAuthorizeRequest(Object sender, EventArgs e)
at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
</Data>
<Data>https://localhost:444/owa/logoff.owa</Data>
<Data>/owa/logoff.owa</Data>
<Data>127.0.0.1</Data>
<Data>CORJESU\SM_cab26786a5604c759</Data>
<Data>True</Data>
<Data>Kerberos</Data>
<Data>NT AUTHORITY\SYSTEM</Data>
<Data>12</Data>
<Data>NT AUTHORITY\SYSTEM</Data>
<Data>False</Data>
<Data> at Microsoft.Exchange.Clients.Common.Canary15.Init(Byte[] userContextIdBinary, Byte[] timeStampBinary, String logonUniqueKey, Byte[] hashBinary, String logData)
at Microsoft.Exchange.Clients.Common.Canary15..ctor(String logonUniqueKey)
at Microsoft.Exchange.Clients.Common.Canary15Cookie.TryCreateFromHttpCookie(HttpCookie cookie, String logonUniqueKey, Canary15Profile profile)
at Microsoft.Exchange.Clients.Common.Canary15Cookie.TryCreateFromHttpContext(HttpContext httpContext, String logOnUniqueKey, Canary15Profile profile)
at Microsoft.Exchange.Clients.Owa2.Server.Core.OwaRequestHandler.InternalOnPostAuthorizeRequest(Object sender)
at Microsoft.Exchange.Clients.Owa2.Server.Core.OwaRequestHandler.OnPostAuthorizeRequest(Object sender, EventArgs e)
at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
</Data>
</EventData>
</Event>I opened a case with Microsoft. After 3 days and over 15 hours on the phone they were able to resolve the problem. They had to use ADSI edit to remove the canary data for the domain.
I tried rebuilding the virtual directories, building a new CAS server, a new mailbox server and a new server with both roles installed. I created a new database and new users in that database and used the new CAS server but the problem continued which
led us to believe it was something being obtained from Active Directory. We finally figured out the problem was in the properties of an object in ADSI.
You have to open the ADSI editor on the primary domain controller (start-->administrative tools-->ADSI edit), go to CN=Services --> CN=Microsoft Exchange --> CN=<Your Site Name> Right click CN=Client Access and click properties.
Scroll down to msExchCanaryData0. You have to click edit and copy the data from Data0, Data1 and Data2 (you may have more or less) to a notepad file. Then erase the data from those settings. Now log onto the CAS server and open IIS management.
Go to application pools and right click MSExchangeOWAAppPool and click Recycling. Then restart all of the mailbox servers.
It's a great idea to take a system state backup before performing these steps as editing ADSI data is risky. -
Error Null Databinding context encountered -WSDL to Java webservice convert
HI,
I have been trying to generate service and client from WSDL using Jdeveloper11 and im unable to progress on this particular WSDL, i was succesfull in creating the client and service for a sample Apache WSDL using the Jdeveloper. If anyone can point out the issue in this WSDL or is there a bug in Jdeveloper when handling complex type? i attach the WSDL that i used, now note that the WSDL calls for another WSDL import witin it, if i comment out the import and its bindings im able to proceed,
WSDL-1
<!-- Tigerstripe : Operations relating to Alarm -->
<wsdl:operation name="getAlarmsByKeys">
<wsdl:input name="getAlarmsByKeysRequest" message="fmWS-v1-0:getAlarmsByKeysRequest" />
<wsdl:output name="getAlarmsByKeysResponse" message="fmWS-v1-0:getAlarmsByKeysResponse" />
<wsdl:fault name="getAlarmsByKeysException" message="fmWS-v1-0:getAlarmsByKeysException" />
</wsdl:operation>
<wsdl:operation name="getAlarmsByTemplate">
<wsdl:input name="getAlarmsByTemplateRequest" message="fmWS-v1-0:getAlarmsByTemplateRequest" />
<wsdl:output name="getAlarmsByTemplateResponse" message="fmWS-v1-0:getAlarmsByTemplateResponse" />
<wsdl:fault name="getAlarmsByTemplateException" message="fmWS-v1-0:getAlarmsByTemplateException" />
</wsdl:operation>
<wsdl:operation name="queryAlarms">
<wsdl:input name="queryAlarmsRequest" message="fmWS-v1-0:queryAlarmsRequest" />
<wsdl:output name="queryAlarmsResponse" message="fmWS-v1-0:queryAlarmsResponse" />
<wsdl:fault name="queryAlarmsException" message="fmWS-v1-0:queryAlarmsException" />
</wsdl:operation>
<!-- Tigerstripe : Operations for Interface artifact methods ( JVTAlarmCreationSession ) -->
<wsdl:operation name="getAlarmSpecificInfoTypes">
<wsdl:input
name="getAlarmSpecificInfoTypesRequest"
message="fmWS-v1-0:getAlarmSpecificInfoTypesRequest" />
<wsdl:output
name="getAlarmSpecificInfoTypesResponse"
message="fmWS-v1-0:getAlarmSpecificInfoTypesResponse" />
<wsdl:fault
name="getAlarmSpecificInfoTypesException"
message="fmWS-v1-0:getAlarmSpecificInfoTypesException" />
</wsdl:operation>
<wsdl:operation name="getVersion">
<wsdl:input
name="getVersionRequest"
message="fmWS-v1-0:getVersionRequest" />
<wsdl:output
name="getVersionResponse"
message="fmWS-v1-0:getVersionResponse" />
<wsdl:fault
name="getVersionException"
message="fmWS-v1-0:getVersionException" />
</wsdl:operation>
<wsdl:operation name="createAlarms">
<wsdl:input
name="createAlarmsRequest"
message="fmWS-v1-0:createAlarmsRequest" />
<wsdl:output
name="createAlarmsResponse"
message="fmWS-v1-0:createAlarmsResponse" />
<wsdl:fault
name="createAlarmsException"
message="fmWS-v1-0:createAlarmsException" />
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="JVTAlarmCreationSessionSoapBinding"
type="fmWS-v1-0:JVTAlarmCreationSessionWSPort">
<soap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http" />
<!-- Tigerstripe : Bindings relating to Alarm -->
<wsdl:operation name="getAlarmsByKeys">
<soap:operation soapAction="getAlarmsByKeys" style="document" />
<wsdl:input>
<soap:body parts="parameters" use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body parts="parameters" use="literal" />
</wsdl:output>
<wsdl:fault name="getAlarmsByKeysException">
<soap:fault name="getAlarmsByKeysException" use="literal" />
</wsdl:fault>
</wsdl:operation>
<wsdl:operation name="getAlarmsByTemplate">
<soap:operation soapAction="getAlarmsByTemplate" style="document" />
<wsdl:input>
<soap:body parts="parameters" use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body parts="parameters" use="literal" />
</wsdl:output>
<wsdl:fault name="getAlarmsByTemplateException">
<soap:fault name="getAlarmsByTemplateException" use="literal" />
</wsdl:fault>
</wsdl:operation>
<wsdl:operation name="queryAlarms">
<soap:operation soapAction="queryAlarms" style="document" />
<wsdl:input>
<soap:body parts="parameters" use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body parts="parameters" use="literal" />
</wsdl:output>
<wsdl:fault name="queryAlarmsException">
<soap:fault name="queryAlarmsException" use="literal" />
</wsdl:fault>
</wsdl:operation>
<wsdl:operation name="getAlarmSpecificInfoTypes">
<soap:operation soapAction="getAlarmSpecificInfoTypes" style="document" />
<wsdl:input>
<soap:body parts="parameters" use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body parts="parameters" use="literal" />
</wsdl:output>
<wsdl:fault name ="getAlarmSpecificInfoTypesException">
<soap:fault name ="getAlarmSpecificInfoTypesException" use="literal"/>
</wsdl:fault>
</wsdl:operation>
<wsdl:operation name="getVersion">
<soap:operation soapAction="getVersion" style="document" />
<wsdl:input>
<soap:body parts="parameters" use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body parts="parameters" use="literal" />
</wsdl:output>
<wsdl:fault name ="getVersionException">
<soap:fault name ="getVersionException" use="literal"/>
</wsdl:fault>
</wsdl:operation>
<wsdl:operation name="createAlarms">
<soap:operation soapAction="createAlarms" style="document" />
<wsdl:input>
<soap:body parts="parameters" use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body parts="parameters" use="literal" />
</wsdl:output>
<wsdl:fault name ="createAlarmsException">
<soap:fault name ="createAlarmsException" use="literal"/>
</wsdl:fault>
</wsdl:operation>
</wsdl:binding>
<!-- Binding for the Notification Producer -->
<!-- <wsdl:binding name="NotificationProducerSoapBinding" type="wsnt:NotificationProducer">
<soap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http" />-->
<!-- =========== NotificationProducer Specific ============== -->
<!-- <wsdl:operation name="Subscribe">
<soap:operation soapAction="Subscribe" style="document"/>
<wsdl:input>
<soap:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal"/>
</wsdl:output>
<wsdl:fault name="ResourceUnknownFault">
<soap:fault name="ResourceUnknownFault" use="literal"/>
</wsdl:fault>
<wsdl:fault name="SubscribeCreationFailedFault">
<soap:fault name="SubscribeCreationFailedFault" use="literal"/>
</wsdl:fault>
<wsdl:fault name="TopicExpressionDialectUnknownFault">
<soap:fault name="TopicExpressionDialectUnknownFault" use="literal"/>
</wsdl:fault>
<wsdl:fault name="InvalidFilterFault">
<soap:fault name="InvalidFilterFault" use="literal"/>
</wsdl:fault>
<wsdl:fault name="InvalidTopicExpressionFault">
<soap:fault name="InvalidTopicExpressionFault" use="literal"/>
</wsdl:fault>
<wsdl:fault name="TopicNotSupportedFault">
<soap:fault name="TopicNotSupportedFault" use="literal"/>
</wsdl:fault>
<wsdl:fault name="InvalidProducerPropertiesExpressionFault">
<soap:fault name="InvalidProducerPropertiesExpressionFault" use="literal"/>
</wsdl:fault>
<wsdl:fault name="InvalidMessageContentExpressionFault">
<soap:fault name="InvalidMessageContentExpressionFault" use="literal"/>
</wsdl:fault>
<wsdl:fault name="UnacceptableInitialTerminationTimeFault">
<soap:fault name="UnacceptableInitialTerminationTimeFault" use="literal"/>
</wsdl:fault>
<wsdl:fault name="UnrecognizedPolicyRequestFault">
<soap:fault name="UnrecognizedPolicyRequestFault" use="literal"/>
</wsdl:fault>
<wsdl:fault name="UnsupportedPolicyRequestFault">
<soap:fault name="UnsupportedPolicyRequestFault" use="literal"/>
</wsdl:fault>
<wsdl:fault name="NotifyMessageNotSupportedFault">
<soap:fault name="NotifyMessageNotSupportedFault" use="literal"/>
</wsdl:fault>
</wsdl:operation>
<wsdl:operation name="GetCurrentMessage">
<soap:operation soapAction="GetCurrentMessage" style="document" />
<wsdl:input>
<soap:body use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body use="literal" />
</wsdl:output>
<wsdl:fault name="ResourceUnknownFault">
<soap:fault name="ResourceUnknownFault" use="literal" />
</wsdl:fault>
<wsdl:fault name="TopicExpressionDialectUnknownFault">
<soap:fault name="TopicExpressionDialectUnknownFault" use="literal" />
</wsdl:fault>
<wsdl:fault name="InvalidTopicExpressionFault">
<soap:fault name="InvalidTopicExpressionFault" use="literal" />
</wsdl:fault>
<wsdl:fault name="TopicNotSupportedFault">
<soap:fault name="TopicNotSupportedFault" use="literal" />
</wsdl:fault>
<wsdl:fault name="NoCurrentMessageOnTopicFault">
<soap:fault name="NoCurrentMessageOnTopicFault" use="literal" />
</wsdl:fault>
<wsdl:fault name="MultipleTopicsSpecifiedFault">
<soap:fault name="MultipleTopicsSpecifiedFault" use="literal" />
</wsdl:fault>
</wsdl:operation>
</wsdl:binding>-->
<!-- Binding for the SubscriptionManager -->
<!-- <wsdl:binding name="SubscriptionManagerSoapBinding" type="wsnt:PausableSubscriptionManager">
<soap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http" />-->
<!-- ========= SubscriptionManager specific operations ====== -->
<!-- <wsdl:operation name="PauseSubscription">
<soap:operation soapAction="PauseSubscription" style="document" />
<wsdl:input>
<soap:body use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body use="literal" />
</wsdl:output>
<wsdl:fault name="ResourceUnknownFault">
<soap:fault name="ResourceUnknownFault" use="literal" />
</wsdl:fault>
<wsdl:fault name="PauseFailedFault">
<soap:fault name="PauseFailedFault" use="literal" />
</wsdl:fault>
</wsdl:operation>
<wsdl:operation name="Renew">
<soap:operation soapAction="Renew" style="document" />
<wsdl:input>
<soap:body use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body use="literal" />
</wsdl:output>
<wsdl:fault name="ResourceUnknownFault">
<soap:fault name="ResourceUnknownFault" use="literal" />
</wsdl:fault>
<wsdl:fault name="UnacceptableTerminationTimeFault">
<soap:fault name="UnacceptableTerminationTimeFault" use="literal" />
</wsdl:fault>
</wsdl:operation>
<wsdl:operation name="Unsubscribe">
<soap:operation soapAction="Unsubscribe" style="document" />
<wsdl:input>
<soap:body use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body use="literal" />
</wsdl:output>
<wsdl:fault name="ResourceUnknownFault">
<soap:fault name="ResourceUnknownFault" use="literal" />
</wsdl:fault>
<wsdl:fault name="UnableToDestroySubscriptionFault">
<soap:fault name="UnableToDestrySubscriptionFault" use="literal" />
</wsdl:fault>
</wsdl:operation>
<wsdl:operation name="ResumeSubscription">
<soap:operation soapAction="ResumeSubscription" style="document" />
<wsdl:input>
<soap:body use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body use="literal" />
</wsdl:output>
<wsdl:fault name="ResourceUnknownFault">
<soap:fault name="ResourceUnknownFault" use="literal" />
</wsdl:fault>
<wsdl:fault name="ResumeFailedFault">
<soap:fault name="ResumeFailedFault" use="literal" />
</wsdl:fault>
</wsdl:operation>
</wsdl:binding>-->
<wsdl:service name="JVTAlarmCreationSessionWebService">
<wsdl:port name="JVTAlarmCreationSessionWSPort"
binding="fmWS-v1-0:JVTAlarmCreationSessionSoapBinding">
<soap:address location="http://localhost/JVTAlarmCreationSessionWebService/JVTAlarmCreationSession" />
</wsdl:port>
<!--wsdl:port name="NotificationProducerPort" binding="wsnt:NotificationProducerSoapBinding">
<soap:address location="http://localhost/JVTAlarmCreationSessionWebService/NotificationProducer"/>
</wsdl:port>
<wsdl:port name="SubscriptionManagerPort" binding="wsnt:SubscriptionManagerSoapBinding">
<soap:address location="http://localhost/JVTAlarmCreationSessionWebService/SubscriptionManager"/>
</wsdl:port-->
</wsdl:service>
</wsdl:definitions>
WSDL-2 imported in the above WSDL
<?xml version="1.0" encoding="utf-8"?>
<!--
OASIS takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on OASIS's procedures with respect to rights in OASIS specifications can be found at the OASIS website. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementors or users of this specification, can be obtained from the OASIS Executive Director.
OASIS invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to implement this specification. Please address the information to the OASIS Executive Director.
Copyright (C) OASIS Open (2004-2006). All Rights Reserved.
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to OASIS, except as needed for the purpose of developing OASIS specifications, in which case the procedures for copyrights defined in the OASIS Intellectual Property Rights document must be followed, or as required to translate it into languages other than English.
The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns.
This document and the information contained herein is provided on an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
-->
<wsdl:definitions name="WS-BaseNotification"
targetNamespace="http://docs.oasis-open.org/wsn/bw-2"
xmlns:wsntw="http://docs.oasis-open.org/wsn/bw-2"
xmlns:wsnt="http://docs.oasis-open.org/wsn/b-2"
xmlns:wsa="http://www.w3.org/2005/08/addressing"
xmlns:wsrf-rw="http://docs.oasis-open.org/wsrf/rw-2"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
<!-- ========================== Imports =========================== -->
<wsdl:import
namespace="http://docs.oasis-open.org/wsrf/rw-2"
location="rw-2.wsdl"/>
<!-- ===================== Types Definitions ====================== -->
<wsdl:types>
<xsd:schema elementFormDefault="qualified">
<xsd:import
namespace="http://docs.oasis-open.org/wsn/b-2"
schemaLocation="b-2.xsd"/>
</xsd:schema>
</wsdl:types>
<!-- ================ NotificationConsumer::Notify ================
Notify(
NotificationMessage
(SubscriptionReference, TopicExpression, ProducerReference,
Message)*
returns: n/a (one way)
-->
<wsdl:message name="Notify">
<wsdl:part name="Notify" element="wsnt:Notify"/>
</wsdl:message>
<!-- ============== NotificationProducer::Subscribe ===============
Subscribe(
(ConsumerEndpointReference, [Filter], [SubscriptionPolicy],
[InitialTerminationTime])
returns: WS-Resource qualified EPR to a Subscription
-->
<wsdl:message name="SubscribeRequest" >
<wsdl:part name="SubscribeRequest"
element="wsnt:Subscribe"/>
</wsdl:message>
<wsdl:message name="SubscribeResponse">
<wsdl:part name="SubscribeResponse"
element="wsnt:SubscribeResponse"/>
</wsdl:message>
<wsdl:message name="SubscribeCreationFailedFault">
<wsdl:part name="SubscribeCreationFailedFault"
element="wsnt:SubscribeCreationFailedFault" />
</wsdl:message>
<wsdl:message name="TopicExpressionDialectUnknownFault">
<wsdl:part name="TopicExpressionDialectUnknownFault"
element="wsnt:TopicExpressionDialectUnknownFault" />
</wsdl:message>
<wsdl:message name="InvalidFilterFault">
<wsdl:part name="InvalidFilterFault"
element="wsnt:InvalidFilterFault" />
</wsdl:message>
<wsdl:message name="InvalidProducerPropertiesExpressionFault">
<wsdl:part name="InvalidProducerPropertiesExpressionFault"
element="wsnt:InvalidProducerPropertiesExpressionFault" />
</wsdl:message>
<wsdl:message name="InvalidMessageContentExpressionFault">
<wsdl:part name="InvalidMessageContentExpressionFault"
element="wsnt:InvalidMessageContentExpressionFault" />
</wsdl:message>
<wsdl:message name="UnrecognizedPolicyRequestFault">
<wsdl:part name="UnrecognizedPolicyRequestFault"
element="wsnt:UnrecognizedPolicyRequestFault" />
</wsdl:message>
<wsdl:message name="UnsupportedPolicyRequestFault">
<wsdl:part name="UnsupportedPolicyRequestFault"
element="wsnt:UnsupportedPolicyRequestFault" />
</wsdl:message>
<wsdl:message name="NotifyMessageNotSupportedFault">
<wsdl:part name="NotifyMessageNotSupportedFault"
element="wsnt:NotifyMessageNotSupportedFault" />
</wsdl:message>
<wsdl:message name="UnacceptableInitialTerminationTimeFault">
<wsdl:part name="UnacceptableInitialTerminationTimeFault"
element="wsnt:UnacceptableInitialTerminationTimeFault"/>
</wsdl:message>
<!-- ========== NotificationProducer::GetCurrentMessage ===========
GetCurrentMessage(topicExpression)
returns: a NotificationMessage (xsd:any)
-->
<wsdl:message name="GetCurrentMessageRequest">
<wsdl:part name="GetCurrentMessageRequest"
element="wsnt:GetCurrentMessage"/>
</wsdl:message>
<wsdl:message name="GetCurrentMessageResponse">
<wsdl:part name="GetCurrentMessageResponse"
element="wsnt:GetCurrentMessageResponse"/>
</wsdl:message>
<wsdl:message name="InvalidTopicExpressionFault">
<wsdl:part name="InvalidTopicExpressionFault"
element="wsnt:InvalidTopicExpressionFault" />
</wsdl:message>
<wsdl:message name="TopicNotSupportedFault">
<wsdl:part name="TopicNotSupportedFault"
element="wsnt:TopicNotSupportedFault" />
</wsdl:message>
<wsdl:message name="MultipleTopicsSpecifiedFault">
<wsdl:part name="MultipleTopicsSpecifiedFault"
element="wsnt:MultipleTopicsSpecifiedFault" />
</wsdl:message>
<wsdl:message name="NoCurrentMessageOnTopicFault">
<wsdl:part name="NoCurrentMessageOnTopicFault"
element="wsnt:NoCurrentMessageOnTopicFault" />
</wsdl:message>
<!-- ========== PullPoint::GetMessages ===========
GetMessages(MaximumNumber)
returns: NotificationMessage list
-->
<wsdl:message name="GetMessagesRequest">
<wsdl:part name="GetMessagesRequest"
element="wsnt:GetMessages"/>
</wsdl:message>
<wsdl:message name="GetMessagesResponse">
<wsdl:part name="GetMessagesResponse"
element="wsnt:GetMessagesResponse"/>
</wsdl:message>
<wsdl:message name="UnableToGetMessagesFault">
<wsdl:part name="UnableToGetMessagesFault"
element="wsnt:UnableToGetMessagesFault"/>
</wsdl:message>
<!-- ========== PullPoint::DestroyPullPoint ===========
DestroyPullPoint()
returns: void
-->
<wsdl:message name="DestroyPullPointRequest">
<wsdl:part name="DestroyPullPointRequest"
element="wsnt:DestroyPullPoint"/>
</wsdl:message>
<wsdl:message name="DestroyPullPointResponse">
<wsdl:part name="DestroyPullPointResponse"
element="wsnt:DestroyPullPointResponse"/>
</wsdl:message>
<wsdl:message name="UnableToDestroyPullPointFault">
<wsdl:part name="UnableToDestroyPullPointFault"
element="wsnt:UnableToDestroyPullPointFault"/>
</wsdl:message>
<!-- ========== PullPoint::CreatePullPoint ===========
CreatePullPoint()
returns: PullPoint (wsa:EndpointReference)
-->
<wsdl:message name="CreatePullPointRequest">
<wsdl:part name="CreatePullPointRequest"
element="wsnt:CreatePullPoint"/>
</wsdl:message>
<wsdl:message name="CreatePullPointResponse">
<wsdl:part name="CreatePullPointResponse"
element="wsnt:CreatePullPointResponse"/>
</wsdl:message>
<wsdl:message name="UnableToCreatePullPointFault">
<wsdl:part name="UnableToCreatePullPointFault"
element="wsnt:UnableToCreatePullPointFault"/>
</wsdl:message>
<!-- ================ SubscriptionManager::Renew ==================
Renew( Duration | AbsoluteTime)
returns: (New Termination Time [CurrentTime])
-->
<wsdl:message name="RenewRequest">
<wsdl:part name="RenewRequest"
element="wsnt:Renew"/>
</wsdl:message>
<wsdl:message name="RenewResponse">
<wsdl:part name="RenewResponse"
element="wsnt:RenewResponse"/>
</wsdl:message>
<wsdl:message name="UnacceptableTerminationTimeFault">
<wsdl:part name="UnacceptableTerminationTimeFault"
element="wsnt:UnacceptableTerminationTimeFault" />
</wsdl:message>
<!-- ============== SubscriptionManager::Unsubscribe ===============
Unsubscribe()
returns: empty
-->
<wsdl:message name="UnsubscribeRequest">
<wsdl:part name="UnsubscribeRequest"
element="wsnt:Unsubscribe"/>
</wsdl:message>
<wsdl:message name="UnsubscribeResponse">
<wsdl:part name="UnsubscribeResponse"
element="wsnt:UnsubscribeResponse"/>
</wsdl:message>
<wsdl:message name="UnableToDestroySubscriptionFault">
<wsdl:part name="UnableToDestroySubscriptionFault"
element="wsnt:UnableToDestroySubscriptionFault" />
</wsdl:message>
<!-- ========== SubscriptionManager::PauseSubscription ============
PauseSubscription()
returns: empty
-->
<wsdl:message name="PauseSubscriptionRequest">
<wsdl:part name="PauseSubscriptionRequest"
element="wsnt:PauseSubscription"/>
</wsdl:message>
<wsdl:message name="PauseSubscriptionResponse">
<wsdl:part name="PauseSubscriptionResponse"
element="wsnt:PauseSubscriptionResponse"/>
</wsdl:message>
<wsdl:message name="PauseFailedFault">
<wsdl:part name="PauseFailedFault"
element="wsnt:PauseFailedFault" />
</wsdl:message>
<!-- ========= SubscriptionManager::ResumeSubscription ============
ResumeSubscription()
returns: empty
-->
<wsdl:message name="ResumeSubscriptionRequest">
<wsdl:part name="ResumeSubscriptionRequest"
element="wsnt:ResumeSubscription"/>
</wsdl:message>
<wsdl:message name="ResumeSubscriptionResponse">
<wsdl:part name="ResumeSubscriptionResponse"
element="wsnt:ResumeSubscriptionResponse"/>
</wsdl:message>
<wsdl:message name="ResumeFailedFault">
<wsdl:part name="ResumeFailedFault"
element="wsnt:ResumeFailedFault" />
</wsdl:message>
<!-- =================== PortType Definitions ===================== -->
<!-- ========= NotificationConsumer PortType Definition =========== -->
<wsdl:portType name="NotificationConsumer">
<wsdl:operation name="Notify">
<wsdl:input message="wsntw:Notify" />
</wsdl:operation>
</wsdl:portType>
<!-- ========= NotificationProducer PortType Definition =========== -->
<wsdl:portType name="NotificationProducer">
<wsdl:operation name="Subscribe">
<wsdl:input message="wsntw:SubscribeRequest" />
<wsdl:output message="wsntw:SubscribeResponse" />
<wsdl:fault name="ResourceUnknownFault"
message="wsrf-rw:ResourceUnknownFault" />
<wsdl:fault name="InvalidFilterFault"
message="wsntw:InvalidFilterFault"/>
<wsdl:fault name="TopicExpressionDialectUnknownFault"
message="wsntw:TopicExpressionDialectUnknownFault"/>
<wsdl:fault name="InvalidTopicExpressionFault"
message="wsntw:InvalidTopicExpressionFault" />
<wsdl:fault name="TopicNotSupportedFault"
message="wsntw:TopicNotSupportedFault" />
<wsdl:fault name="InvalidProducerPropertiesExpressionFault"
message="wsntw:InvalidProducerPropertiesExpressionFault"/>
<wsdl:fault name="InvalidMessageContentExpressionFault"
message="wsntw:InvalidMessageContentExpressionFault"/>
<wsdl:fault name="UnacceptableInitialTerminationTimeFault"
message="wsntw:UnacceptableInitialTerminationTimeFault"/>
<wsdl:fault name="UnrecognizedPolicyRequestFault"
message="wsntw:UnrecognizedPolicyRequestFault"/>
<wsdl:fault name="UnsupportedPolicyRequestFault"
message="wsntw:UnsupportedPolicyRequestFault"/>
<wsdl:fault name="NotifyMessageNotSupportedFault"
message="wsntw:NotifyMessageNotSupportedFault"/>
<wsdl:fault name="SubscribeCreationFailedFault"
message="wsntw:SubscribeCreationFailedFault"/>
</wsdl:operation>
<wsdl:operation name="GetCurrentMessage">
<wsdl:input message="wsntw:GetCurrentMessageRequest"/>
<wsdl:output message="wsntw:GetCurrentMessageResponse"/>
<wsdl:fault name="ResourceUnknownFault"
message="wsrf-rw:ResourceUnknownFault" />
<wsdl:fault name="TopicExpressionDialectUnknownFault"
message="wsntw:TopicExpressionDialectUnknownFault"/>
<wsdl:fault name="InvalidTopicExpressionFault"
message="wsntw:InvalidTopicExpressionFault" />
<wsdl:fault name="TopicNotSupportedFault"
message="wsntw:TopicNotSupportedFault" />
<wsdl:fault name="NoCurrentMessageOnTopicFault"
message="wsntw:NoCurrentMessageOnTopicFault" />
<wsdl:fault name="MultipleTopicsSpecifiedFault"
message="wsntw:MultipleTopicsSpecifiedFault" />
</wsdl:operation>
</wsdl:portType>
<!-- ========== PullPoint PortType Definition ===================== -->
<wsdl:portType name="PullPoint">
<wsdl:operation name="GetMessages">
<wsdl:input name="GetMessagesRequest"
message="wsntw:GetMessagesRequest" />
<wsdl:output name="GetMessagesResponse"
message="wsntw:GetMessagesResponse" />
<wsdl:fault name="ResourceUnknownFault"
message="wsrf-rw:ResourceUnknownFault" />
<wsdl:fault name="UnableToGetMessagesFault"
message="wsntw:UnableToGetMessagesFault" />
</wsdl:operation>
<wsdl:operation name="DestroyPullPoint">
<wsdl:input name="DestroyPullPointRequest"
message="wsntw:DestroyPullPointRequest" />
<wsdl:output name="DestroyPullPointResponse"
message="wsntw:DestroyPullPointResponse" />
<wsdl:fault name="ResourceUnknownFault"
message="wsrf-rw:ResourceUnknownFault"/>
<wsdl:fault name="UnableToDestroyPullPointFault"
message="wsntw:UnableToDestroyPullPointFault" />
</wsdl:operation>
<wsdl:operation name="Notify">
<wsdl:input message="wsntw:Notify"/>
</wsdl:operation>
</wsdl:portType>
<!-- ========== CreatePullPoint PortType Definition =============== -->
<wsdl:portType name="CreatePullPoint">
<wsdl:operation name="CreatePullPoint">
<wsdl:input name="CreatePullPointRequest"
message="wsntw:CreatePullPointRequest" />
<wsdl:output name="CreatePullPointResponse"
message="wsntw:CreatePullPointResponse" />
<wsdl:fault name="UnableToCreatePullPointFault"
message="wsntw:UnableToCreatePullPointFault" />
</wsdl:operation>
</wsdl:portType>
<!-- ========== SubscriptionManager PortType Definition =========== -->
<wsdl:portType name="SubscriptionManager">
<wsdl:operation name="Renew">
<wsdl:input name="RenewRequest"
message="wsntw:RenewRequest" />
<wsdl:output name="RenewResponse"
message="wsntw:RenewResponse" />
<wsdl:fault name="ResourceUnknownFault"
message="wsrf-rw:ResourceUnknownFault" />
<wsdl:fault name="UnacceptableTerminationTimeFault"
message=
"wsntw:UnacceptableTerminationTimeFault" />
</wsdl:operation>
<wsdl:operation name="Unsubscribe">
<wsdl:input name="UnsubscribeRequest"
message="wsntw:UnsubscribeRequest" />
<wsdl:output name="UnsubscribeResponse"
message="wsntw:UnsubscribeResponse" />
<wsdl:fault name="ResourceUnknownFault"
message="wsrf-rw:ResourceUnknownFault" />
<wsdl:fault name="UnableToDestroySubscriptionFault"
message=
"wsntw:UnableToDestroySubscriptionFault" />
</wsdl:operation>
</wsdl:portType>
<!-- ====== PausableSubscriptionManager PortType Definition ======= -->
<wsdl:portType name="PausableSubscriptionManager">
<!-- ============== Extends: SubscriptionManager ============ -->
<wsdl:operation name="Renew">
<wsdl:input name="RenewRequest"
message="wsntw:RenewRequest" />
<wsdl:output name="RenewResponse"
message="wsntw:RenewResponse" />
<wsdl:fault name="ResourceUnknownFault"
message="wsrf-rw:ResourceUnknownFault" />
<wsdl:fault name="UnacceptableTerminationTimeFault"
message=
"wsntw:UnacceptableTerminationTimeFault" />
</wsdl:operation>
<wsdl:operation name="Unsubscribe">
<wsdl:input name="UnsubscribeRequest"
message="wsntw:UnsubscribeRequest" />
<wsdl:output name="UnsubscribeResponse"
message="wsntw:UnsubscribeResponse" />
<wsdl:fault name="ResourceUnknownFault"
message="wsrf-rw:ResourceUnknownFault" />
<wsdl:fault name="UnableToDestroySubscriptionFault"
message=
"wsntw:UnableToDestroySubscriptionFault" />
</wsdl:operation>
<!-- === PausableSubscriptionManager specific operations === -->
<wsdl:operation name="PauseSubscription">
<wsdl:input message="wsntw:PauseSubscriptionRequest"/>
<wsdl:output message="wsntw:PauseSubscriptionResponse"/>
<wsdl:fault name="ResourceUnknownFault"
message="wsrf-rw:ResourceUnknownFault" />
<wsdl:fault name="PauseFailedFault"
message="wsntw:PauseFailedFault" />
</wsdl:operation>
<wsdl:operation name="ResumeSubscription">
<wsdl:input message="wsntw:ResumeSubscriptionRequest"/>
<wsdl:output message="wsntw:ResumeSubscriptionResponse"/>
<wsdl:fault name="ResourceUnknownFault"
message="wsrf-rw:ResourceUnknownFault" />
<wsdl:fault name="ResumeFailedFault"
message="wsntw:ResumeFailedFault" />
</wsdl:operation>
</wsdl:portType>
</wsdl:definitions>
And the error i get is [fatal error] null databinding context encountered when creating service.
Steps i followed:
1. Created a new project in Jdev
2. Right clicked on project to expand Business Tier - Web Services nodes. Selected the Java web Service from WSDL.
3. Selected WSDL to convert
---Says it is Fetching WSDL
---then says building model
--and pops error : [fatal error] null databinding context encountered.
Any suggestions? I'm unable to get this issue fixed for a long time.Hey guys,
I couldnt get this fixed in jdeveloper, i finally gave up on using Jdeveloper for Web service creation.
I went back to my eclipse3.2.2 and used the Eclipse WTP 1.5.4 and guess what, it had no issues generating the service and client for my WSDL.
I am not sure Jdeveloper can compete with Eclipse functionality and ease.
Maybe you are looking for
-
Interactive report search hidden column
I have a comment column in an interactive report (form with report) and I want the user to be able to search records on that column but I don't want to display that column in the report - it's just too big and the user can click on the edit icon to s
-
I used Ion Profile Pro turntable to digitize some old records. It worked fine for most of the records, but on five or six albums I get an error message saying "the original file can't be found" and it won't transfer them to my iPod Touch. However, th
-
I have updated my iPhone 4s to iOS7 but when i connect it to itunes on my PC it give me a msg to restore your iPhone in summary tab, Please help m using win 7 and updated itunes.
-
My friend lost my original power adapter and she bought me a new adapter, however, this adapter causes me lots of problems-it works sometimes, but often I found it failed to work(the light is off, doesn't charge at all), you never know when it is gon
-
3.2; DAC; ListControl - Problem with rollback
I have a ListControl used for navigation. The problem arises when I click rollback button on NavigationBar. After this event ListControl stops updating its state according to InfoBus events. Is it a bug or what? Did anyone encounter such behaviour? A