[J2EE Deployment SPI:260080]Unable to define application install directory

Using ant deploy task to deploy the app to Weblogic server(Windows) through Hudson server(Linux), failed due to the following issue:

deploy:
 [wldeploy] weblogic.Deployer -debug -verbose -upload -noexit -name TestApp -source /app/hudson/job1/workspace/dist/TestApp.war -targets AdminServer -adminurl t3://192.168.1.111:7001 -user weblogic -password ******** -deploy 


 [wldeploy] [BasicOperation.dumpTmids():689] :   {Target=AdminServer, WebLogicTargetType=server, Name=TestApp}, targeted=true
 [wldeploy] [BasicOperation.deriveAppName():139] : appname established as: TestApp
 [wldeploy]  
 [wldeploy] java.io.IOException: [J2EE Deployment SPI:260080]Unable to define application install directory at '/tmp/TestApp.war'. Directory could not be created or is a file.


Solution: check the folder /tmp on Hudson server and remove the TestApp.war from there.

Silverlight sample site

Tools:

Silverlight Toolkit

Image Tools for Silverlight

samples:
http://samples.msdn.microsoft.com/Silverlight/SampleBrowser/index.htm#/?sref=GlobalOffsetAnimation_2

 

Silverlight Controls with Effects and Transitions

Silverlight.FX Effects in Depth

Effects and Transitions for Silverlight

Silverlight 3 Drag Behavior

Transforms

http://msdn.microsoft.com/en-us/library/cc189037(v=vs.95).aspx

3-D Effects (Perspective Transforms)

http://msdn.microsoft.com/en-us/library/dd470131(v=vs.95).aspx

http://www.silverlightshow.net/items/Image-slider-control-in-Silverlight-1.1.aspx
http://weblogs.asp.net/psheriff/archive/2010/10/07/horizontal-list-boxes-in-silverlight.aspx
http://weblogs.asp.net/psheriff/archive/2009/10/29/create-a-login-screen-in-silverlight.aspx
http://blogs.lessthandot.com/index.php/WebDev/WebDesignGraphicsStyling/silverlight-spinner
https://timdams.wordpress.com/2010/10/19/tutorial-on-silverlight-4-databinding-in-code-behind-custom-user-controls-etc/
http://www.silverlight.net/learn/data-networking/binding/silverlight-data-binding
http://www.silverlight.net/learn/data-networking/binding/data-binding-to-controls-(silverlight-quickstart)

http://timheuer.com/blog/articles/silverlight-get-started-part-3-accessing-data.aspx

Interaction between Silverlight and the Browser

Model-View-ViewModel In Silverlight 2 

Display Live Data In Silverlight Using ObservableCollection and INotifyPropertyChanged

DataGrid and row details in Silverlight

Authentication denied: Boot identity not valid

Weblogic error when starting the server:


<Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.>


Follow the following steps:
1: remove the file boot.properties from directory servers/yourserver/security/.
2: remove the directory servers/yourserver/data/ldap .
start weblogic by command line, and it will prompt for username and password to boot.

create new file boot.properties in directory servers/yourserver/security, and put the following value and restart.
password=weblogic
username=weblogic

Out of the box, users are stored in WebLogic’s embedded LDAP. This means all “normal” users as well as the WebLogic administrative user typically named “weblogic” or “admin” are stored there. Additionally, groups are also stored in embedded LDAP. Users and groups are stored there because the embedded LDAP serves as the DefaultAuthenticator’s data store.


There’s one more critical piece about authenticators and that’s the Control Flag. Each authenticator has a Control Flag that can be set to REQUIRED, REQUISITE, SUFFICIENT, or OPTIONAL. Each flag indicates how the authenticator will be treated by the security framework and whether or not that authenticator has to be able to successfully authenticate the user or not. You can find an explanation of these flags here.
reference: common-problems-with-authentication-provider-configuration

java string encoding when reading from database

If the data you stored in the database is ISO-8859-1, then when you read the data from database you'd better use:  
String str = new String(rs.getBytes("message_fr"),"ISO-8859-1"); to avoid the encoding issue.

If the application is started in UTF-8 encoding, then the following statement will read the data as UTF-8 encoding:
String str =rs.getString("message_fr")