I would like to share my sad experience which I had with Esta, when trying to arrange my vacation 28.05-02.06.2009

My wife and me decided to have a short sporting holidays and play tennis. In a big sporting store (Sport Experts, Wien) I saw an Esta booklet, which advertised different kinds of sporting vacations. We’ve slected Slowakei, Stupava hotel «Parkhotel».

On Esta site http://www.esta.net hotel was announced as a ***-stars one. It has a lot of sand courts as well as indoor courts. The latter was very important for us, hence the spring was very rainy this year. Together with the hotel voucher we received additional information, which stated that all guests MUST have tennis shoes for sand and indoor courts. So, we had to buy another two pairs of shoes for each of us.

Right on our arrival we’ve been unpleasantly surprised: hotel entrance was decorated only with ** (two!) stars, but not with the declared ***. I was even more surprised when starting to write this post, I’ve visited Esta site once again. The hotel had already **** (FOUR) starts! Really nice and quick upgrade

Despite small number of guests in the hotel, we had to wait for our meal for 40 minutes. The food itself was disgusting: half-fried chicken, over-spiced soup, etc… At the same time the hotel was declared as “kids-friendly”. I’m not sure this is a healthy food for adults, not saying about the kids.

From bad to worse. It was raining all day long and sand courts turned into  sand beaches. No playing, no trainings. To my question about the indoor courts I’ve received an answer, that they are busy with handball or some other, not tennis related competitions. We felt really bad…

Esta office was placed on the same floor we lived. I went for the explanations. Of course, to all my questions I’ve received very prompt and useless answers. The hotel was “awarded” with three starts according to “there” classification, but not to the world-wide excepted. And because it’s only a ***-hotel, they don’t have a first-class cook. (Of course, it’s a rocket-science to fry chicken legs)

The only positive effect of that slam was the waiter speed-up.

It was raining for a second day in a row and we decided to go back home and not wasting our time and money.

Don’t go for Esta, it really SU…KS!!!

Хочу поделиться некоторым прескорбным опытом, который я поимел от отдыха (28.05 – 02.06.2009), организованного компанией Esta.

Мы с семьей решили устроить себе небольшой спортивный отдых и поиграть в теннис. В одном большой спортивном магазине (Sport Experts, Wien) мне попался на глаза рекламный буклет компании Esta, которая предлагала разнообразный спортивный отдых. Наш выбор пал на Slowakei, Stupava, отель Parkhotel.

Итак, отель на сайте http://www.esta.net был заявлен как ***. Отель располагает крытыми кортами, что для нас было решающим моментом, поскольку весна была очень дождливая. Вместе с ваучером на отдых мы по почте получили дополнительную информацию, в которой говорилось, что все, приезжающие на теннисный отдых, ОБЯЗАНЫ иметь две пары обуви: для крытых и песочных кортов. Нам пришлось купить еще 2 пары кроссовок.

Сразу по приезде в отель мы были неприятно удивлены: на входе красовались только ** (две!) звезды, а не ***, заявленные в рекламе. Еще больше я был “очарован” когда начал писать этот пост и снова зашел на сайт Esta. Отель уже значится как **** (четырех!!!) звездочный! Это просто чудо, как братья словаки быстро успели обновить отель.

Не смотря на очень небольшое количество людей в отеле, обсуживали в ресторане очень медленно. Еду приходилось ждать по 40 минут. Само же качество еды было просто отвратительное: недожаренная курица, очень острый суп и т.д. И все это при том, что отель заявлен как kids-friendly? Простите, ЭТО тоже детям давать есть???

Дальше-больше. День подряд непрекращаясь лил дождь. Корты превратились в бассейны и тренировки откладывались. На мой вопрос по поводу использования закрытых кортов мне ответили, что там сейчас проходят не то гандбольные, не то еще какие-то, абсолютно не относящиеся к теннису, соревнования. Настроение было абсолютно испорчено.

Как на “счастье”, офис недобросовестной компании Esta находился как раз на этаже, где мы жили. Я пошел разбираться. На вопрос про количество звезд, мне ответили, что это ИХ, видите ли, классификация, которая может и не совпадать со всемирно принятой. Вот, только не понятно, зачем это надо? По поводу нареканий на качество еды, мне сказали, что конечно, есть “проблемки” и повор не супер-класс. Гы-гы, конечно, нужен повар-француз, чтобы нормально пожарить обычные куриные ножки Вобщем, на все вопросы мне был дан абсолютно квалифицированный и бесполезный ответ.

Единственным плюсом данной разборки было то, что официант реально начал шевелиться быстрей.

Дождь лил не переставая, платить за отвратительную еду и ждать в надежде солнца мы не хотели. Уехали раньше, пробыв в горе-отеле всго 2 дня

Никому не посоветую иметь дело с компанией Esta! Esta – really su…ks!!!

# /usr/sbin/alternatives --display java

In case there is some – remove that:

# /usr/sbin/alternatives --remove java [put-the-path-here]

Set up JAVA_HOME variable and update PATH variable in /etc/profile. PATH should contain the path to default jdk’s bin directory.

// Security	token
String token;
// MyService and MySoapService are stubs generated from WSDL
MyService service = new MyService();
MyServiceSoap ep = service.getMyServiceSoap();

Binding binding = ((BindingProvider) ep).getBinding();
List handlers = binding.getHandlerChain();
handlers.add(new MySOAPHandler(token));
binding.setHandlerChain(handlers);

Here is the code of the MySOAPHandler class used to intercept messages and actually add SOAP header

public class MySOAPHandler implements SOAPHandler {

	private String token;

	public DHSOAPHandler(String token) {
		this.token = token;
	}
	public boolean handleMessage(SOAPMessageContext messageContext) {
		SOAPMessage
		msg = messageContext.getMessage();
		if ((Boolean) messageContext.get(MessageContext.MESSAGE_OUTBOUND_PROPERTY)){
			try {
				SOAPEnvelope envelope = msg.getSOAPPart().getEnvelope();
				SOAPHeader header = envelope.addHeader();
				SOAPElement el = header.addHeaderElement(envelope.createName("TicketHeader",
									"", "http://ws.service.com/"));
				el = el.addChildElement(envelope.createName("Ticket", "", "http://ws.service.com/"));
				el.setValue(token);
				msg.saveChanges();
			}
			catch (SOAPException	e) {
				return false;
			}
		}
		return true;
	}

	public boolean handleFault(SOAPMessageContext messageContext) {
		return true;
	} 

	public void close(MessageContext messageContext){
	}

	// I'm not quite sure about what should this function do, but I guess something like this...
	public Set getHeaders(){
		Set headers = new HashSet();
		headers.add(new QName("https://ws.service.com/", "TicketHeader"));
		return headers;
	}
}

The structure of the header to be added is

<TicketHeader>
	<Ticket>OD01096347CCA</Ticket>
</TicketHeader>

1. The main window’s first responder and the successive responder objects up the view hierarchy
2. The main window itself
3. The main window’s delegate (which need not inherit from NSResponder)
4. The application object, NSApp
5. The application object’s delegate (which need not inherit from NSResponder)

Connecting custom controller instance of a class, derived from NSObject (or other class not rooted to NSResponder) class to NSWindow‘s or NSApplication‘s (NSApp) delegate outlet also puts controller object into FirstResponder chain.
Keep in mind sequence of responders in the chain when deciding which class should contain responding method.

• Select Targets group and select Add|New Target…|Unit Test Bundle
• Setup dependent test bundle
  • Double-click test unit target to display it’s info. Select General tab and add project to be tested to dependencies
  • Select Build tab and set Bundle Loader value to $(BUILT_PRODUCTS_DIR)/MyApp.app/Contents/MacOS/MyApp
    if you are testing application and to $(BUILT_PRODUCTS_DIR)/MyApp if you are testing framework. Set Test Host value to $(BUNDLE_LOADER)

Debugging unit tests

Mostly this is taken from Chris Hanson’s blog but contains one adjustment

When you add the custom executable, Xcode will bring up its info window. Switch to the Arguments tab. Here you’ll need to enter some command-line arguments to pass to the test rig and some environment variables to affect how it’s run. In the arguments tab of your application executable, first add an environment variable named DYLD_INSERT_LIBRARIES. Set its value to $(SYSTEM_LIBRARY_DIR)/PrivateFrameworks/DevToolsBundleInjection.framework/DevToolsBundleInjection . Then add a second environment variable, XCInjectBundle. Set its value to MyTestBundle.octest . (Originally, it was $(BUILT_PRODUCTS_DIR)/MyTestBundle.octest but that didn’t work for me. See this answer for details). Make sure the check marks next to both of these environment variables — and your -SenTest All argument, of course — are set.

To actually debug a failing test, build your tests and set a breakpoint on the line where the failure occurs. Now choose Debug Executable from the Debug menu. Do not choose Build and Debug from the Build menu. You need to use Debug Executable because your build will fail due to the failing test; Debug Executable doesn’t try to build first, it only cares whether an executable is present.

You should successfully stop at your breakpoint!

If your tests take a long time to run — they shouldn’t, they’re unit tests after all, but it can still happen — you may want to just run the tests for one test case, or just one individual test. This is easy too. Rather than specifying -SenTest All in your arguments to otest, you can specify -SenTest MyTestCaseClassName to run the all the tests in the specified test case. To run just a single test, use -SenTest MyTestCaseClassName/testMethodName instead.

References:
http://www.stiefels.net/2007/05/01/unit-testing-with-xcode
http://chanson.livejournal.com/119578.html

The important things to remember about memory management in Cocoa distill down to these rules of thumb:

• Objects created by alloc or copy have a retain count of 1.
• Assume that objects obtained by any other method have a retain count of 1 and reside in the autorelease pool. If you want to keep it beyond the current scope of execution, then you must retain it.
• When you add an object to a collection, it is retained. When you remove an object from a collection, it is released. Releasing a collection object (such as an NSArray) releases all objects stored in it as well.
• Make sure that there are as many release or autorelease messages sent to objects as there are alloc, copy, mutableCopy, or retain messages sent. In other words, make sure that the code you write is balanced.
• Retain, then release objects in setter methods.
• NSString objects created using the @" . . . " construct are effectively constants in the program. Sending retain or release messages to them has no effect. This explains why we haven’t been releasing the strings created with the @" . . . " construct.

References
http://www.stepwise.com/Articles/Technical/2001-03-11.01.html
http://www.oreillynet.com/pub/a/mac/excerpt/Cocoa_ch04/index.html