nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

WCM 2.1 adding .war files

umair_qureshi

Not sure if everyone using WCM2.1 is having the same issue. I am unable to upload the .war file in the Web Projects, tried it for 2 different .war files already and it isn't working. MOre specifically for the Alfresco-sample-website.war is giving trouble uploading. Is anyone having the same issue?

Find more posts tagged with

Comments

slickshow

I have the same trouble too. After a while, I cancelled the operation and when I peeked into the web project, it had uploaded some files into my sandbox. Not sure if it was complete, so I deleted the web project and tried to upload it again but it errored out when I used the same name for the web project. Maybe a bug with this release, maybe we need to await a patch.

kevinr

Yes there is a bug raised on import into a User Sandbox. Importing directly into the Staging Area (admin user only) is working fine.
http://issues.alfresco.com/browse/WCM-573

Thanks,

Kevin

kvc

Everyone:

For 2.1, we implemented our new locking service. This means that all assets uploaded into a user's sandbox are auto-locked, just as is any edited items in the web client or CIFS.

The result, however, was a significant performance degradation as locks are taken on assets. That is the issue noted by Kev. We are doing some serious performance profiling and tuning presently for our next Community drop.

As Kev notes, if you've mounted CIFS as admin you can drag-and-drop directly into Staging, where created assets do not have locks explicitly taken. This is a temporary workaround until we can correct this performance issue.

If you upload an expanded war via CIFS into Staging instead of a user's sandbox either via CIFS or the web client, you'll have anywhere between a 25 and 30x diff in performance. For example, a WAR file that will take 15s using the workaround will take ~18m because of locking.

We will keep you posted on this.

Kevin

slickshow

Thanks for the clarification.

umair_qureshi

that works… thanks.

kvc

As an update …

A fix went in this weekend to improve locking performance when bulk importing a WAR file via the Bulk Import action in the GUI.

With this improvement, Bulk Import is now takes a little bit more than twice as long as in 2.0.1, or 50 seconds versus 20 seconds in our sample dataset. This is a *significant* improvement however from our RC1 release.

Please note that Bulk Import into a user's sandbox via the GUI will always be more expensive starting with 2.1.0, given that we are now enforcing the taking of locks.

Please also note that we still intend to reset the default CIFS configuration so that developers using the CIFS interface will not have lock-taking auto-enforced (as it is in the GUI). When this is added, performance should be commensurate with 2.0.1.

For parties interested in testing with the latest fix, you can grab the current nightly build or download and build direct from source.

Kevin