Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Comments

Close side panel

WIP towards Tomcat and Standalone support#14

Open
bmustiata wants to merge 4 commits intofakereplace:masterfakereplace/fakereplace:masterfrom
bmustiata:masterbmustiata/fakereplace:masterCopy head branch name to clipboard
Open

WIP towards Tomcat and Standalone support#14
bmustiata wants to merge 4 commits intofakereplace:masterfakereplace/fakereplace:masterfrom
bmustiata:masterbmustiata/fakereplace:masterCopy head branch name to clipboard

Conversation

@bmustiata
Copy link

DO NOT MERGE

This is just so you can have a look at.

Important changes are:

  1. Tomcat integration, works on real Tomcat, but I have no clue on how to test it in arquillian.
  2. Standalone client, that is also embedded in the dist, and will search for a fakereplace.ini and just read paths from there, pushing classes and resources as they change. This works also with multiple deployments, they are separated with ini sections.

Especially the 2nd point needs quite a bit of cleaning, since the monitoring was implemented by looping in a thread, and the ini reading has some issues. I've seen you have something in your Maven plugin that looks much cleaner for monitoring, I would probably borrow that.

return false; //lambdas
// if no packages are given, replace all classes.
if (replaceablePackages.length == 0) {
return true;
Copy link
Member

Choose a reason for hiding this comment

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

I think this will cause problems. e.g. at the moment replacement for lambdas does not work properly so lambdas will break.

Copy link
Author

Choose a reason for hiding this comment

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

I've readded it in.

@stuartwdouglas
Copy link
Member

stuartwdouglas commented Aug 31, 2016

Why did you go for .ini files rather than standard java property files (which would save a lot of code)? IMHO Java developers are a lot more familiar with property files, while .ini files are mostly a windows thing.

e.g. something like

deployments=a.war,b.war
a.war.resource=/path/to/resources
a.war.classes=/path/to/classes

b.war.resources=....

@bmustiata bmustiata force-pushed the master branch 2 times, most recently from df47b31 to 8ab7407 Compare September 20, 2016 11:44
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.

2 participants

Morty Proxy This is a proxified and sanitized view of the page, visit original site.