Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added commands for adding acceptors and connectors in messaging subsystem #53

Merged

Conversation

honza-kasik
Copy link
Contributor

No description provided.

@Ladicek
Copy link
Contributor

Ladicek commented Jan 22, 2016

The AddAcceptor and AddConnector names are a bit too generic. There's a multitude of connectors in the applicatoin server. Can we figure out a better name?

Also, how often does one need to use these commands? They seem quite specific to me.

@honza-kasik
Copy link
Contributor Author

What about AddMessagingAcceptor and AddMessagingConnector?
I really have no idea how often these commands are needed. I just though that it would be nice to have them since I used in in several test cases...

@Ladicek
Copy link
Contributor

Ladicek commented Jan 22, 2016

+1 to those names. They're unique and, at the same time, not that longer.

import java.util.Map;

/**
* An abstract class which implements common properties of connector and acceptor in messaging connections.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You don't have to say that it's an abstract class, everyone can see that from abstract class ... below.

@Ladicek
Copy link
Contributor

Ladicek commented Jan 22, 2016

Good work on test coverage, by the way!

@honza-kasik
Copy link
Contributor Author

Thank you! I added suggested improvements and fixed it.

@honza-kasik honza-kasik force-pushed the messaging-connections-commands branch 3 times, most recently from c0e741b to c05e160 Compare January 22, 2016 14:16
protected final String factoryClass;


public AbstractTransportConfigAddCommand(TransportConfigType configType, TransportConfigItem configItem,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

private

@Ladicek
Copy link
Contributor

Ladicek commented Jan 25, 2016

I think this looks good now, with that single comment about privacy of a constructor.

@Ladicek
Copy link
Contributor

Ladicek commented Jan 25, 2016

Oh, and one more thing: the validate method in the builders should have a return type of void. The return value is never used anyway.

@Ladicek
Copy link
Contributor

Ladicek commented Jan 26, 2016

OK, please squash and I'll merge.

@honza-kasik
Copy link
Contributor Author

Commits were squashed

@Ladicek
Copy link
Contributor

Ladicek commented Jan 27, 2016

Why two commits? Are the tests in the 2nd commit somehow different from the tests in the 1st commit? Also, why the note "Fixed bugs and added suggested improvements" in the first commit?

@honza-kasik honza-kasik force-pushed the messaging-connections-commands branch 2 times, most recently from e55cb84 to 84240c4 Compare January 27, 2016 07:56
@honza-kasik
Copy link
Contributor Author

Sorry, fixed

this.factoryClass = factoryClass;
}

protected AbstractTransportConfigAddCommand(InVmBuilder builder, TransportConfigItem configItem) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you parametrize reference to generic type with wildcard (i.e. InVmBuilder<?> builder) to prevent in this case IMO uneccessary compiler complaints?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure I can, I just did not understand why to generify this before. 👍

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We already have quite a bunch of unchecked conversions in commands. They are practically unavoidable when using generics to simulate self types. I don't mind much, really. @honza-kasik it's your choice; in fact, I was just getting to merge this when @zebrik added these comments :-)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hah, took me too long to comment :-) Nevermind.

@honza-kasik honza-kasik force-pushed the messaging-connections-commands branch from 84240c4 to 618faa8 Compare January 27, 2016 09:13
@honza-kasik
Copy link
Contributor Author

Parametrized contructor arguments with wildcard.

@Ladicek
Copy link
Contributor

Ladicek commented Jan 27, 2016

I still don't understand why we have AddAcceptorOnlineTest, AddConnectorOnlineTest, AddMessagingAcceptorOnlineTest and AddMessagingConnectorOnlineTest.

@honza-kasik honza-kasik force-pushed the messaging-connections-commands branch from 618faa8 to f78a17a Compare January 27, 2016 09:30
@honza-kasik
Copy link
Contributor Author

I am really sorry, as I was squashing commits I totally overlooked this...

@Ladicek Ladicek merged commit f78a17a into wildfly-extras:master Jan 27, 2016
@Ladicek Ladicek self-assigned this Jan 27, 2016
@Ladicek Ladicek added this to the 0.9.4 milestone Jan 27, 2016
olukas pushed a commit to olukas/creaper that referenced this pull request Jan 9, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants