common-web | Turn web user activity into a analyzable stream | Runtime Evironment library

It turns out bookmarklets do indeed fail to work on the latest Android Firefox. This was pointed out on the Mozilla support forum after I asked, with a link to the relevant github issue.

I don't think that this diagram belongs to any UML type, isn't it?

That does not follow UML notation, for instance as I know the only cases of a rectangle with dotted border are regions(interruptible, expansion) in an activity and your diagram is not at all for an activity.

Does this diagram follow any kind of standard notation?

The more important is not to know if the notation looks like something from UML but to know what is represented.

As the title indicate that diagram shows the architecture, but with mixed types of elements, the closer possible in UML seems to be a deployment diagram, a little bit more far component diagram.

As far I understand, the actual path of the process is layer based and precisely equivalent to n-tier version (only differing in how it's drawn, which should be irrelevant).

Yes, that's right.

Is the main difference between those two architecture types simply how we're using them or is there an actual difference code-wise or in the project structure (except for the naming, of course)?

The difference is which code knows about, has references to, depends on other code.

In N-Tier, the business logic needs to know the API of the infrastructure layer. All of the dependencies point down.

In clean architecture/onion architecture, etc, the infrastructure layer knows about the API of the domain layer. All of the dependencies point inward.

Clean architecture puts the business logic and application model at the center of the application. Instead of having business logic depend on data access or other infrastructure concerns, this dependency is inverted: infrastructure and implementation details depend on the Application Core.

This style is often accompanied by the use of a Composition Root, which is responsible for wiring together the components that will eventually do the work.

Are you saying that there's no business logic layer in onion version? I.e. that it's baked in into the application core?

Typically, business logic is understood to be in the middle of the onion. For instance, Robert Martin offers

You may find that you need more than just these four. There’s no rule that says you must always have just these four. However, The Dependency Rule always applies. Source code dependencies always point inwards.

if I understand you correctly, you want to put all pipeline related operations, sdev scripts related to the solution level.

in the picture above, they are not focusing on that, it is focused on the code itself.

so I suggest having this structure instead

Visual Studio doesn't like to behave quite right when the TargetFramework does not totally match up.

Common.Bll.csproj

Problems came from simultaneous access of different users with the same credentials, plus the Undertow's issue. Upgrading to a newer version of Wildfly solved our problem.