MOSS VisualStudio Workflow change document metadata

To change a metadata of the document of the workflow do the following:

SPListItem document = workflowProperties.Item;
document.File.CheckOut();
// for example the title metadata
document["Title"] = "title";
document.Update();
document.File.CheckIn("check in description", SPCheckinType.MajorCheckIn);

MOSS VisualStudio Workflow create a task in the task list

To create a task in the assigend task list of the workflow do the following:

// get the assigned task list of the workflow
SPList taskList = workflowProperties.TaskList;

// create the task
SPListItem task = taskList.Items.Add(documentFolder.Folder.ServerRelativeUrl, SPFileSystemObjectType.File);

// set properties
task["Title"] = "title";
task["Assigned To"] = "user name";
task["Description"] = "task description";

// store the task
task.Update();

MOSS VisualStudio Workflow create folder in task list

To create a folder in the assigned task list of the workflow do following:

// get the task list for the read receipts
SPList taskList = workflowProperties.TaskList;

// create a folder with the document name
SPListItem documentFolder = taskList.Items.Add(taskList.RootFolder.ServerRelativeUrl, SPFileSystemObjectType.Folder);

documentFolder["Name"] = "new folder name";

Wicket Version 1.3.1 released

Wicket released the version 1.3.1

http://www.apache.org/dyn/closer.cgi/wicket/1.3.1

Following bugs are fixed and improvments are done:

Bugs

• WICKET-812 - Submit button, multipart content and UploadProgressBar
• WICKET-989 - DatePicker: NaN if numerical input cannot be parsed
• WICKET-1184 - PageSavingThread keeps running after undeploy
• WICKET-1194 - UploadProgressBar incompatible with submit buttons onSubmit method (in FireFox at least)
• WICKET-1243 - the DatePicker show the same week title in china.
• WICKET-1249 - modal.js conflicts with mootools and possibly other javascript frameworks. + patch fix
• WICKET-1254 - Binding to a BigDecimal don't honor browser locale
• WICKET-1257 - iframe get request done 2x after ajax change in IE
• WICKET-1258 - AjaxFormChoiceComponentUpdatingBehavior assumes Radio/Choice items are a direct child of the group in the client-side DOM
• WICKET-1260 - CheckBox.setRequired() is not picked up in 1.3-final
• WICKET-1262 - Page#readResolve is not called
• WICKET-1263 - Using nested wicket:enclosure throws exception
• WICKET-1264 - assertComponentOnAjaxResponse does not work with WicketTester.clickLink
• WICKET-1270 - NPE in ListMultipleChoice.updateModel()
• WICKET-1271 - Script in RenderHead method of AjaxFormChoiceComponentUpdatingBehavior needs fixing
• WICKET-1274 - Only properties from first panel-implementation loaded when using different implementations of an abstract panel on the same page
• WICKET-1275 - FLAG_HAS_BEEN_RENDERED is set when rendering invisible components
• WICKET-1277 - When no component is focused on AjaxRequestTarget, wicket tries to focus element with id 'null'
• WICKET-1282 - AjaxFormSubmitBehavior doesn't work well with nested forms
• WICKET-1290 - PrependingStringBuffer.equals(Object obj) is not reflexive
• WICKET-1304 - Form processing workflow is broken for FormComponentPanels

Improvements

• WICKET-1020 - expose configuration of CompoundValidator, NumberValidator
• WICKET-1193 - i18n: Translation of resource files in Korean
• WICKET-1252 - Default start week day based on locale
• WICKET-1272 - Better clustering support for DiskPageStore
• WICKET-1283 - Allow to query component markup id without creating one
• WICKET-1284 - Report last focused element id on ajax request
• WICKET-1293 - Improve SelectOptions: allow customization of created SelectOption objects
• WICKET-1299 - HybridUrlCodingStrategy should throw a PageExpiredException if a RequestListenerInterface is targeted on a non-existent page-id/version
• WICKET-1309 - Properties files translation (_es)
• WICKET-1313 - Created Norwegian translation of Application.properties
• WICKET-1318 - NavigatorLabel should be localizable

Simple login for a web application running under JBoss

Description
How can I realize a simple login for a web application running under JBoss?

Solution
We assume that the username for the login is admin, the password also and the role is Administrator.

1. Insert the following tags in the file web.xml in the directory WEB-INF of the web application:
   
   <security-constraint>
   <web-resource-collection>
   <web-resource-name>WebApplication</web-resource-name>
   <url-pattern>/*</url-pattern>
   <http-method>GET</http-method>
   <http-method>POST</http-method>
   </web-resource-collection>
   <auth-constraint>
   <role-name>Administrator</role-name>
   </auth-constraint>
   </security-constraint>
   
   <login-config>
   <auth-method>BASIC</auth-method>
   <realm-name>Web Application</realm-name>
   </login-config>
   
   <security-role>
   <description>The role required to access the WebApplication.</description>
   <role-name>Administrator</role-name>
   </security-role>
   
2. Create a file jboss-web.xml in WEB-INF directory of the web application with the following content:
   
   <security-domain>java:/jaas/WebApplication</security-domain>
   
3. Create a file user.properties in the JBoss server directory conf\props with the following content:
   
   admin=admin
   
4. Create a file roel.properties in the JBoss server directory conf\props with the following content:
   
   admin=Administrator
   
5. Add the entry below to the file login-configuration.xml in the JBoss server directory conf.
   
   <application-policy name="WebApplication"> <authentication> <login-module code="org.jboss.security.auth.spi.UsersRolesLoginModule" flag="required"> <module-option name="usersProperties">props/users.properties</module-option> <module-option name="rolesProperties">props/roles.properties</module-option> </login-module> </authentication> </application-policy>

Edit functionality for the rows of a DataView

Description
How can I implement the edit functionality over the whole row(s) of a DataView component?

Solution
JAVA
Add following code snippet in the implementet Method void populateItem(Item item) of the DataView component:

item.add(new AjaxEventBehavior("onclick") {
protected void onEvent(AjaxRequestTarget target) {
// action
}
});

Through this piece of code the action is called by each onclick event on the whole row.


HTML
Additionaly you can define the hand cursor of the row TR-tags:

<tr wicket:id="data" style="cursor: hand;">

Visual Studio 2005 vs SharePoint Designer

SharePoint Designer
Mit dem SharePoint Designer ist es sehr einfach, sequentielle Workflows zu erstellen und diese zu konfigurieren. Allerdings ist die Funktionalität beschränkt und man hat nur eine gewisse Anzahl von Aktivitäten zur Auswahl. Es ist möglich selber Aktivitäten zu erstellen, doch das ist sehr umständlich.

Visual Studio 2005
Das Visual Studio 2005 und die "Extenstions for Windows Workflow Foundation" bieten ein mächtiges Werkzeug zur Erzeugung von speziellen oder komplizierten Workflows. Mit diesem Tool sind praktisch keine Grenzen gesetzt.

Visual Studio 2005 vs SharePoint Designer

Visual Studio 2005	SharePoint Designer
Es existieren Code Dateien, welche den Workflow beschreiben und diese sind beliebig anpassbar.	Es werden keine Code-Dateien unterstützt.
Ein Workflow kann als Template erstellt und in verschiedenen Listen oder Seiten gebraucht werden.	Wenn ein Workflow erstellt wird, ist er an eine spezifische Liste oder Seite gebunden.
Über das Webfronted von MOSS kann der Workflow einer Liste zugewiesen werden.	Die Zuweisung wird schon bei der Erstellung festgelegt.
Workflows können mit Inhaltstypen verknüpft werden.	Können nur mit Listen oder Seiten verknüpft werden.
Manuelles deployen.	Automatisches deployen bei der Erstellung.
Debugging Möglichkeiten.	Kein Debugging.
"Sequential" und "state machine" Workflows werden unterstützt.	Es werden nur "sequential" Workflows unterstütz.