Enterprise Client Community

Hi,

tools that I know, which are used inside the community:

1. CaptainCasa Hot Deployment ;-)
2. JRebel

What I read from Hotswap (http://hotswapagent.org/) sounds good and very interesting... Would be great if maybe someone already has taken a look + shares experience!

Kind regards, Björn

...is available in the download area.

Details about changes: http://www.captaincasa.com/docu/eclnt_changelog

...sorry, missed this one:

I cannot reproduce this: in my examples the editor content shows the right language. Btw.: the editor does not influence the language but just renders the content as is. So the language is coming from the application.

Maybe your application sets the language explicity somewhere?

Pleas check for:

Code:

 1. HttpSessopmAccess.setCurrentLocale(...) - modern version
 2. FacesContext().getCurrentInstance().getViewRoot().setLocale(...)

Kind regards! Björn

...is available in the download area.

Details about changes: http://www.captaincasa.com/docu/eclnt_changelog

Hi Frauke,

the style which is defined in "sessiondefault.xml" is the one that is used in the layout editor by default (and which is also the base for showing the available style variants).

You either can directly edit (eclntjsfserver/config/sessiondefauts.xml) or use the "Project configuration..." button in the tools, then select "Session Defaults" at the bottom of the following dialog.

Kind regards! Björn

...is available in the download area.

Details about changes: http://www.captaincasa.com/docu/eclnt_changelog

There was a very interesting mail conversation today which I want to share. - It is/may be relevant for applications which were developped > 10 years ago and did not use PageBean-class (because it was not available this point of time). Beans had to be picked from the dispatcher.

So all users from 2011 on can skip this info...

First Question was: how can you run a page bean within an existing non-page bean as ROWPAGEBEANINCLUDE? - The answer is simple: you can just do it! The new page bean must implement IPageBean best by extending PageBean-class.

Now the problem: the bean can't be easily turned into a page bean by extending PageBean-class because there is already an inheritance tree on top of the bean that cannot be changed to page bean.

So how can you add a minimal IPageBean implementation to a non-page-bean to make it useable by ROWPAGEBEANINCLUDE?

The following is the response:

Code:

 public class M20_innerUI
     implements IPageBean, Serializable
 {
     String m_actualRootExpression;
     long m_stamp = UniqueIdCreator.createCounter();
     
     public M20_innerUI()
     {
     }
 
     public String getPageName() { return "/ztest/m20_inner.xml"; }
     public String getRootExpressionUsedInPage() { return "#{d.M20_innerUI}"; }
 
     // implementation of IPageBean - reduce to minimum, no popups
     
     @Override
     public void setActualRootExpression(String rootExpression) { m_actualRootExpression = rootExpression; }
     @Override
     public String getActualRootExpression()
     {
         if (m_actualRootExpression != null)
             return m_actualRootExpression;
         else
             return getRootExpressionUsedInPage();
     }
     @Override
     public long getStamp() { return m_stamp; }
     @Override
     public void onBeforeRendering() { /* add any code */ }
     
     // no popup management!
 
     @Override
     public ModalPopup openModalPopup(IPageBean pageBean, String title, int width, int height, IModalPopupListener popupListener) { throw new Error("Not implemented"); }
     @Override
     public ModelessPopup openModelessPopup(IPageBean pageBean, String title, int width, int height, IModelessPopupListener popupListener) { throw new Error("Not implemented"); }
     @Override
     public void closePopup(IPageBean pageBean) { throw new Error("Not implemented"); }
     @Override
     public IPageModifier getPageModifier() { return null; }
 }

Please see this snippet as bridge to overcome this situation - but do not see this as great general strategy!

Kind regards! Björn

Hi Frauke,

thanks for your message - which is correct... The preview URL may contain a double slash.

Today's/This week's version was still open, so we immediately added the fix. It will be available with 20230508, somewhere this evening.

Kind regards! - Björn

Hi,

hmm, just tried:

Code:

 /cctempfileaccess/fa524adf-e2d0-41e7-b51a-28c1be0b09a6/Käsespätzle.txt;jsessionid=FD4532F03976794F1775B2A47B4BBCBC;filename=/Käsespätzle.txt

generated by

Code:

         m_url = TempFileManager.saveTempFile("Käsespätzle.txt","application/octet-stream",content.getBytes());

Sure that the new version is applied?

Kind regards! Björn

PS: otherwise use "Kasspatzen"!

...is available in the download area.

Details about changes: http://www.captaincasa.com/docu/eclnt_changelog

Hi,

the information comes through the UploadContent implementation.

Code:

     public class MyUploadContent extends DefaultUploadContent
     {
         public void beginPassing()
         {
             m_content = "Upload started.\n";
         }
         public void passClientFile(String fileName, byte[] bytes)
         {
             m_content += "File was passed: client name " + fileName + ", length " + bytes.length +"\n";
         }
         public void endPassing()
         {
             m_content += "Upload ended.";
         }
     }

Demo in Demo Workplace: Components => File up/download => Asynchronous Upload

Kind regards! Björn

Hi Klas,

me again ;-)

Yes the BaseActionEventUpload contains a property getClientFileName() - and you can then interpret the extension of the file name.

Kind regards! Björn

PS: please not: FILEUPLOADBUTTON only should be used for "small" files. "Small" meaning < 1MB. Otherwise use the FILEUPLOADBUTTONASYNCHRONOUS component, which does not embed the upload the file into the normal CC-roundtrip data exchange but which opens up a parallel connection to transfer the file - and significantly reduces the amount of memory during upload processing. Please check: https://www.captaincasa.com/docu/eclnt_risc_developersguide/all.html#fileupload

Hi Klas,

of course you can set the BROWSER component (this is the iframe-opener) into a SCALEPANE and then zoom it.

Buit auto-zoom is not possible because the iframe does not tell about the actual sized of its content.

Kind regards! Björn

Hi Markus,

yes you are right - the document type was not considered anymore when using "strange" file names and the names were "even stranger" in the file name proposed for download...

We did a fix.

If you want to have the fix immediately: 20230426_INT was just uploaded (Maven repository)... Otherwise: it is part of next update.

Thanks + Regards! Björn

Dear community,

please find details about this year's community meeting here.

https://captaincasa.com/pdf/eclnt_CommunityMeeting_XVII.pdf

Kind regards! Björn