I am ordered to apply CORBA Notification Service. I googled a lot. But all of the information is just introduction. It isn't helpful to apply this technique to a actual project.
Is there anyone can help me? Where can I start?
Thanks a lot.
Start with the examples and tests that are shipped with your notication service implementation. The one as part of TAO has a lot of examples and tests that provide a good starting point. Also check the OMG Notification service specification that is available from the OMG website at www.omg.org
Related
I am a newbie to cf and want to contribute cloud-foundry. Can somebody point me to a newbie guide? or anything else?
Thanks,
There are a lot of ways that you can contribute.
The easiest is to help answer questions. You can do that here on SO, on the CF mailing lists or on Slack.
Another easy way to help is with documentation. Docs are managed on Github and it's easy to submit fixes and improvements via PRs.
If you want to contribute code then you're going to need to dig in a bit more first. Cloud Foundry is a large project made up of many different pieces, so the first step is picking a component that interests you / where you'd like to contribute. This page in the docs has a good overview of the different components, so it's a good reference.
Once you've narrowed it down to a specific component of CF, then check the Github page for that component and look for instructions on contributing. Most of the teams have details about how to get started hacking on their projects. Here's one example, which is the Loggregator project.
You can also check the Issues page in Github or the team's Tracker project for outstanding issues that might need resolved. That can give you inspiration for ways to pitch in and help with the code.
Hope that helps!
I'm trying to improve the semantic web services' discovery to satisfy better the user. For that, I choose to use OWL-S. So I created an ontology using Protégé then I generated semantic web services using OWL-S editor within Eclipse (these services have been in part generated automatically since they are already developed in Java). What I can't do now is the execution of these services: I don't know how to proceed. I need your help please, I didn't find good documentation or tutorials about the life cycle of OWL-S services. Could you please help me and suggest me some useful tools, tutorials..?
PS: do you think that OWL-S is still used or do you suggest something else? What is the most common way to develop semantic web services nowadays?
Thank you!
OWl-S is a W3C consortium standard, therefore documentation is available regarding that. Check the below links
http://www.w3.org/Submission/OWL-S/
http://www.daml.org/services/owl-s/
http://www.ai.sri.com/daml/services/owl-s/examples.html
Was just listening to Josh Suereth's talk "Introduction to Actors Systems" on Devnexus 2013 and got excited. I am familiar with Enterprise Integration Patterns and have Spring Integration experience.
What benefits can Akka provide that Spring Integration can't handle?
Are they competitors or is there any use case where I would like to integrate them?
Thank you for your feeadback on the matter, first of all!
I'm not familiar with Akka and really not sure it does. Seems for me it is something similar what we have with Reactor.
From other side, if you familiar with Akka and with Spring Integration as well, the contribution is always welcome. We have an Extension Repo, where you can start a new project on the matter and we will follow with you PoC and go ahead with robust integration.
From other side I know that Apache Cammel has Akka extension (http://doc.akka.io/docs/akka/current/java/camel.html), so I don't see reason don't not support it from Spring Integration as well.
Yes, I haven't answered for your original question, but as I know no one from our team is familar with Akka.
Hope someone else share his wisdom here.
I am doing some research on web services. I have not written any web service but I am doing a small write up on them.
During my research I've come across terms contract-first and contract-last.
Can someone explain these two in an understandable form ?
To expound on the answer by Kaleb, contract-first is where you create the WSDL, and then you can create the implementation from this, and since the WSDL is your contract, this would be contract-first.
Contract-last is where the WSDL is created from the source code, or implementation, so it will most likely be generated by a tool rather than created by the developer.
Update:
For a nice explanation with code, in Java, you can look at this explanation from the Spring Web Services 1.5 documentation.
They will discuss the pros and cons, though they will be biased toward their approach (which is contract-first). Anyway, I think it is a nice explanation.
Contract-first means you design the way your services are going to communicate with each other before you design the services themselves.
Contract-last is the other way around – you design how your service is going to work, then make one or more methods available as the interface for other services.
The web service endpoint usually is defined in an early stage of a project. Since it follows the "contract first" principle, it shouldn't be changed after communicated to client systems.
Therefore, it is vital to label the web service in a good way.
How would you label web services?
e.g.
http://my.domain.com/businessProcess/services/concreteServiceName
Other ideas?
See this question as a poll... Feel free to vote for the best idea.
We decide on names by talking to the developers, business guys, and support guys. We formed a committee called the "interface control committee", and we approach it kind of like you described in the question. We want service names to be descriptive, reflect the processes they support, and fit the needs of the technical and business stakeholders.
When we have ICC meetings, we also talk about schemas and how they should be developed. The business guys are key in this as well since they know what data they want to expose and why.
KA
I would include a version number in the URLs.